Thanks for the update.
I got the idea; it also works in our case.
I read the last post by Rob; this feature has been posted before, and there
seems no such an easy way to figure it out.
Any way, the manual operation can solve our problem. Thanks a lot!
2010/8/20 Oleg Anastasjev
> Chen Xinli gm
Chen Xinli gmail.com> writes:
> would you pls describe the manual operation with more details?
> I have not found any related information.
>
Um, this is code of our in-house implementation of cassandra client libraries.
The main idea is that normally clients query ring and work directly with nod
On 8/19/10 7:18 AM, Chen Xinli wrote:
2010/8/19 Oleg Anastasjev
Chen Xinli gmail.com> writes:
Hi,
Despite our use cases, is't it a good feature to disable reading when a
node
is doing hinted handoff, just like bootstraping?
It will be very useful for READ ONE consitency level.
Or it ca
2010/8/19 Oleg Anastasjev
> Chen Xinli gmail.com> writes:
>
> >
> > Hi,
> >
> > Despite our use cases, is't it a good feature to disable reading when a
> node
> > is doing hinted handoff, just like bootstraping?
> > It will be very useful for READ ONE consitency level.
> >
> > Or it can be an op
Chen Xinli gmail.com> writes:
>
> Hi,
>
> Despite our use cases, is't it a good feature to disable reading when a node
> is doing hinted handoff, just like bootstraping?
> It will be very useful for READ ONE consitency level.
>
> Or it can be an option in storage-conf.xml, and user can set it
Hi,
Despite our use cases, is't it a good feature to disable reading when a node
is doing hinted handoff, just like bootstraping?
It will be very useful for READ ONE consitency level.
Or it can be an option in storage-conf.xml, and user can set it when
necessary.
I'd like to implement this featu
