Enyim client elects the wrong bucket?
I have the following configuration for Enyim client in web.config of my web app:
<membase>
<servers bucket="session_state" userName="session_state" password="xyz">
<add uri="http://ginseng:8091/pools/default" />
<add uri="http://lecithin:8091/pools/default" />
</servers>
The membase server has two buckets:
- default -> type: memcached
- session_state -> type: membase
I've activated logging for enyim client library and I received the following messages and I see no activity in admin console on the 'session_state' bucket. It seems that Enyim library is using the Memcached pool (named: default) instead of session_state pool which is of type Membase.
2011-05-12 10:38:39,623 [32] DEBUG Membase.MessageStreamListener - Started working.
2011-05-12 10:38:39,623 [1] DEBUG Membase.MessageStreamListener - Starting the listener. Queue=True
2011-05-12 10:38:39,669 [32] DEBUG Membase.MessageStreamListener - Looking for the first working node.
2011-05-12 10:38:39,716 [32] DEBUG Membase.ConfigHelper - Found config for bucket default.
2011-05-12 10:38:39,716 [32] DEBUG Membase.MessageStreamListener - Resolved pool url http://ginseng:8091/pools/default to http://ginseng:8091/pools/default/bucketsStreaming/default
2011-05-12 10:38:39,716 [32] DEBUG Membase.MessageStreamListener - Start receiving messages.
2011-05-12 10:38:39,747 [32] INFO Membase.MembasePool - Received new configuration.
2011-05-12 10:38:39,763 [32] INFO Membase.MembasePool - No vbucket. Server count: 1
2011-05-12 10:38:39,779 [32] DEBUG Membase.MessageStreamListener - Processing message: {"name":"default","bucketType":"memcached","authType":"sasl","saslPassword":"","proxyPort":0,"uri":"/pools/default/buckets/default","streamingUri":"/pools/default/bucketsStreaming/default","flushCacheUri":"/pools/default/buckets/default/controller/doFlush","nodes":[{"replication":1.0,"clusterMembership":"active","status":"healthy","hostname":"172.16.69.30:8091","clusterCompatibility":1,"version":"1.6.5","os":"x86_64-unknown-linux-gnu","ports":{"proxy":11211,"direct":11210}}],"stats":{"uri":"/pools/default/buckets/default/stats"},"nodeLocator":"ketama"}
2011-05-12 10:38:39,794 [41] INFO Membase.MembasePool - Received new configuration.
2011-05-12 10:38:39,794 [41] INFO Membase.MembasePool - No vbucket. Server count: 1
Can you take a look please and tell me what's wrong with this setup? I am using the latest Enyim client released version 2.11
Regards,
Robert
This is a known issue in the latest 2.11 release of the Enyim client. We have fixed it, but have not gotten the fix into a release yet. The latest code can be downloaded from github here:
https://github.com/enyim/EnyimMemcached