> Hello Carlos,
> Looking at your configuration, I see that W (1) + R (1) = 2, which is
> not > R (2).
> So you could write on one node, and read on another one a different
> version, without detecting any inconsistency.
> Consistent handoff looks for slop store walking down the ring and has
> maybe a problem with this configuration. any-handoff (default) picks a
> random node and that's it.
> On Jun 18, 1:49 pm, ctasada <ctas...@gmail.com> wrote:
> > Hi everyone,
> > Doing my test to migrate to a zones aware cluster, I created an small
> test
> > cluster like this:
> > <cluster>
> > <name>cluster-zone-test</name>
> > <zone>
> > <zone-id>1</zone-id>
> > <proximity-list>2</proximity-list>
> > </zone>
> > <zone>
> > <zone-id>2</zone-id>
> > <proximity-list>1</proximity-list>
> > </zone>
> > <server>
> > <id>0</id>
> > <host>10.162.2.145</host>
> > <http-port>38188</http-port>
> > <socket-port>6688</socket-port>
> > <partitions>0,2,4</partitions>
> > <zone-id>1</zone-id>
> > </server>
> > <server>
> > <id>1</id>
> > <host>10.162.2.145</host>
> > <http-port>38288</http-port>
> > <socket-port>6788</socket-port>
> > <partitions>1,3,5</partitions>
> > <zone-id>2</zone-id>
> > </server>
> > </cluster>
> > And defined an store like this
> > <stores>
> > <store>
> > <name>test</name>
> > <persistence>bdb</persistence>
> > <routing>server</routing>
> > <routing-strategy>zone-routing</routing-strategy>
> > <!-- global replication factor -->
> > <replication-factor>2</replication-factor>
> > <!-- zone specific replication factors -->
> > <zone-replication-factor>
> > <replication-factor zone-id="1">1</replication-factor>
> > <replication-factor zone-id="2">1</replication-factor>
> > </zone-replication-factor>
> > <zone-count-reads>0</zone-count-reads>
> > <zone-count-writes>0</zone-count-writes>
> > <required-reads>1</required-reads>
> > <preferred-reads>1</preferred-reads>
> > <required-writes>1</required-writes>
> > <preferred-writes>1</preferred-writes>
> > <key-serializer>
> > <type>string</type>
> > </key-serializer>
> > <value-serializer>
> > <type>string</type>
> > </value-serializer>
> > <hinted-handoff-strategy>consistent-handoff</hinted-handoff-strategy>
> > </store>
> > </stores>
> > Once started any of the nodes I see that the server doesn't startup, its
> > waiting for something. After doing some debug I discovered that the
> server
> > is looping in the ConsistentHandoffStrategy constructor.
> > If I remove the <hinted-handoff-strategy> from the stores.xml everything
> > runs properly. Am I configuring something wrong?
> > I'll keep looking for a fix to this problem, but if someone can confirm
> if
> > it's a bug or something else, would be great :)
> > Regards,
> > Carlos
> --
> You received this message because you are subscribed to the Google Groups
> "project-voldemort" group.
> To post to this group, send email to project-voldemort@googlegroups.com.
> To unsubscribe from this group, send email to
> project-voldemort+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/project-voldemort?hl=en.
