[infinispan-dev] NBST design

[Galder Zamarreño]

First of all, code apart, the document that Adrian has written is very well written, clear, concise and with loads of important information. So kudos to Adrian for the write up!

Now, onto the contents. I'm not yet finished reading the doc, the following comes up:

"The hash of the address of a node no longer participates in the computation of the CH…"

Hmmm, sounds like this is gonna break the Hot Rod protocol:
https://docs.jboss.org/author/display/ISPN/Hot+Rod+Protocol+-+Version+1.1#HotRodProtocol-Version1.1-Servernodehashcodecalculation

The hash code of each node was sent back to the clients as part of the topologies so that they could locate which node has the keys.

Seems like we're now gonna have to send that routing table back to Hot Rod clients? Hmmmmmmm... 

Cheers,

On Aug 15, 2012, at 11:24 AM, Adrian Nistor wrote:

> Hi,
> 
> I managed to rewrite the old NBST design document and created a v2 [1] 
> that should cover the interesting aspects. I'm not sure I managed to 
> make it intelligible and sound enough, but this is the best I could do 
> after several attempts at rewriting :)
> 
> Please read it. Your feedback is welcome!
> 
> The old document is still there [2] for now but should not be relied 
> upon. I kept it because some parts of it might still be relevant and 
> could be moved to v2 doc, but I don't think they are essential in 
> understading the code of our pull request. Dan, could you have a look if 
> there are any bits that we need to move to v2?
> 
> Thanks,
> Adrian
> 
> [1] https://community.jboss.org/wiki/Non-BlockingStateTransferV2
> 
> [2] https://community.jboss.org/wiki/Non-blockingStateTransfer
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache