hi;
would unsafeassasinating a dead node maintain the replication factor
like decommission process or removenode process?
thanks
hi;
we were trying to add in a new node to the cluster. It fails during the
bootstrap process unable to gossip with seed nodes. We have not faced this
earlier.
2015-10-31 12:30:15,779 [HANDSHAKE-/X.X.X.X] INFO OutboundTcpConnection
Handshaking version with /X.X.X.X
2015-10-31 12:30:15,810 [HAN
You have to do few things before unsafe as sanitation . First run the nodetool
decommission if the node is up and wait till streaming happens . You can check
is the streaming is completed by nodetool netstats . If streaming is completed
you can do unsafe assanitation .
To answer your question
Please send both the yaml file I.e. Seed and new node.
Sent from my iPhone
> On Oct 31, 2015, at 5:55 AM, sai krishnam raju potturi
> wrote:
>
> hi;
>we were trying to add in a new node to the cluster. It fails during the
> bootstrap process unable to gossip with seed nodes. We have n
Thanks Surabhi. Decommission nor removenode did not work. We did not
capture the tokens of the dead node. Any way we could make sure the
replication of 3 is maintained?
On Sat, Oct 31, 2015, 11:14 Surbhi Gupta wrote:
> You have to do few things before unsafe as sanitation . First run the
> nodet
Whether the node is down or up which you want to decommission?
Sent from my iPhone
> On Oct 31, 2015, at 8:24 AM, sai krishnam raju potturi
> wrote:
>
> Thanks Surabhi. Decommission nor removenode did not work. We did not capture
> the tokens of the dead node. Any way we could make sure the r
it's dead; and we had to do unsafeassassinate as other 2 methods did not
work
On Sat, Oct 31, 2015 at 11:30 AM, Surbhi Gupta
wrote:
> Whether the node is down or up which you want to decommission?
>
> Sent from my iPhone
>
> On Oct 31, 2015, at 8:24 AM, sai krishnam raju potturi <
> pskraj...@gm
So have you already done unsafe assassination ?
On 31 October 2015 at 08:37, sai krishnam raju potturi
wrote:
> it's dead; and we had to do unsafeassassinate as other 2 methods did not
> work
>
> On Sat, Oct 31, 2015 at 11:30 AM, Surbhi Gupta
> wrote:
>
>> Whether the node is down or up which y
yes Surbhi.
On Sat, Oct 31, 2015 at 12:10 PM, Surbhi Gupta
wrote:
> So have you already done unsafe assassination ?
>
> On 31 October 2015 at 08:37, sai krishnam raju potturi <
> pskraj...@gmail.com> wrote:
>
>> it's dead; and we had to do unsafeassassinate as other 2 methods did not
>> work
>>
Is the cluster using vnodes?
Sent from my iPhone
> On Oct 31, 2015, at 9:16 AM, sai krishnam raju potturi
> wrote:
>
> yes Surbhi.
>
>> On Sat, Oct 31, 2015 at 12:10 PM, Surbhi Gupta
>> wrote:
>> So have you already done unsafe assassination ?
>>
>>> On 31 October 2015 at 08:37, sai krishn
Hi guys,
Could you help me with this error?
cassandra.Unavailable: code=1000 [Unavailable exception] message="Cannot
achieve consistency level LOCAL_QUORUM" info={'required_replicas': 2,
'alive_replicas': 1, 'consistency': 'LOCAL_QUORUM’}
I am using cassandra standalone
Thanks
One or more of your nodes, depending on your replication factor, is not
answering in time. Either they are down or have too much load that they are
not able to answer every request before the timeout expires.
On 31 Oct 2015 20:35, "Eduardo Alfaia" wrote:
> Hi guys,
>
> Could you help me with this
yes Surbhi.
On Sat, Oct 31, 2015 at 1:13 PM, Surbhi Gupta
wrote:
> Is the cluster using vnodes?
>
> Sent from my iPhone
>
> On Oct 31, 2015, at 9:16 AM, sai krishnam raju potturi <
> pskraj...@gmail.com> wrote:
>
> yes Surbhi.
>
> On Sat, Oct 31, 2015 at 12:10 PM, Surbhi Gupta
> wrote:
>
>> So
If it is using vnodes then just run nodetool repair . It should fix the issue
related to data if any.
And then run nodetool cleanup
Sent from my iPhone
> On Oct 31, 2015, at 3:12 PM, sai krishnam raju potturi
> wrote:
>
> yes Surbhi.
>
>> On Sat, Oct 31, 2015 at 1:13 PM, Surbhi Gupta
>>
14 matches
Mail list logo
