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 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
> nodes
> found in ring until they detect failure or slow down of a particular node.
> Then clients fail over to the next node in ring automatically. Failed node
> is
> placed by clients to failed nodes list and will not ever be used by clients
> operator's command. This command is not to cassandra servers, but to
> clients
> saying to exclude node from failed nodes list.
>
> And there is procedure, that operator should inspect, did failed node
> finished
> hinted handoff prior issuing this command to clients.
>
> If we'd have possibility to inspect this condition automatically, we'd
> eliminated this manual inspection from our workflow.
>
>
>
>
--
Best Regards,
Chen Xinli
