Matt. Thanks for the reply.

Would it be possible to do that with the elasticsearch plugin too? 
milliseconds seem expensive to me but I think my biggest problem is that 
with my current approach, I'm often running into "timed out waiting for 
value" exceptions (even when I set the timeout to like 1 minute). I 
recently updated to 2.5.0 and I'm still getting the exception. There is no 
way to give couchbase a hint on where i'd like it to handle a specifc key? 
Do you have any ideas for how to help with the exception? I also receive a 
"failure on node ..." exception quite frequently too. 



On Friday, March 7, 2014 9:44:05 PM UTC-5, Corey Nolet wrote:
>
> Hello,
>
> I've got a unique use-case where I want to use memcached as a backing 
> cache behind Twitter Storm so that I can place keys and values and have 
> Couchbase index them in views as well as ElasticSearch so that users can 
> query on the data that's being populated from Storm.
>
> Storm has a unique feature that will allow me to guarantee that the same 
> item i'm processing will always be sent to the same node/processor. For 
> instance, if i have documents with keys "A, B, and C" and I have 3 nodes 
> running the same storm topology, I can guarantee that A gets put on the 
> same node, B gets put on the same node, and C gets put on the same node. 
> From what I've read, If I use the MemcachedClient in the couchbase java 
> client API instead of the couchbase client and have each of my storm nodes 
> only talk to their localhost memcached clien, I should be able to guarantee 
> that the keys/values stay on that local node, correct? It's important for 
> me as well because I'm manipulating these keys and values quite frequently. 
> Are there any gotchas I should be aware of when considering this approach?
>
> Moxy will not automatically balance out these keys and put them on foreign 
> nodes as long as my topology doesn't change, correct? If nodes are ever 
> added, both Couchbase and Storm will also be added.
>
> Thanks!
>

-- 
You received this message because you are subscribed to the Google Groups 
"Couchbase" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to