Re: Re : will Unsafeassaniate a dead node maintain the replication factor
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 >> wrote: >> 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 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 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 >>> 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 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 unsafe assanitation will not take care of replication factor . It is like forcing a node out from the cluster . Hope this helps. Sent from my iPhone > On Oct 31, 2015, at 5:12 AM, sai krishnam raju potturi > wrote: > > hi; >would unsafeassasinating a dead node maintain the replication > factor like decommission process or removenode process? > > thanks > > >
Re: Re : will Unsafeassaniate a dead node maintain the replication factor
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 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 >>> >>> 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...@gmail.com> 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 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 > 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 unsafe assanitation will not take care of > replication factor . > It is like forcing a node out from the cluster . > > Hope this helps. > > Sent from my iPhone > > > On Oct 31, 2015, at 5:12 AM, sai krishnam raju potturi < > pskraj...@gmail.com> wrote: > > > > hi; > >would unsafeassasinating a dead node maintain the replication > factor like decommission process or removenode process? > > > > thanks > > > > > >>> >> >
Re: Error code=1000
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 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
>
>
Error code=1000
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
Re: Re : will Unsafeassaniate a dead node maintain the replication factor
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 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 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 > 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 >> 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 unsafe assanitation will not take care of >> replication factor . >> It is like forcing a node out from the cluster . >> >> Hope this helps. >> >> Sent from my iPhone >> >> > On Oct 31, 2015, at 5:12 AM, sai krishnam raju potturi >> > wrote: >> > >> > hi; >> >would unsafeassasinating a dead node maintain the replication >> > factor like decommission process or removenode process? >> > >> > thanks >> > >> > >
Re: Re : will Unsafeassaniate a dead node maintain the replication factor
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 >> >> 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...@gmail.com> 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 >>> 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 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 unsafe assanitation will not take care of replication factor . It is like forcing a node out from the cluster . Hope this helps. Sent from my iPhone > On Oct 31, 2015, at 5:12 AM, sai krishnam raju potturi < pskraj...@gmail.com> wrote: > > hi; >would unsafeassasinating a dead node maintain the replication factor like decommission process or removenode process? > > thanks > > >>> >> >
Re: Re : will Unsafeassaniate a dead node maintain the replication factor
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 you want to decommission? >> >> Sent from my iPhone >> >> On Oct 31, 2015, at 8:24 AM, sai krishnam raju potturi < >> pskraj...@gmail.com> 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 >> 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 >>> 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 unsafe assanitation will not take care of >>> replication factor . >>> It is like forcing a node out from the cluster . >>> >>> Hope this helps. >>> >>> Sent from my iPhone >>> >>> > On Oct 31, 2015, at 5:12 AM, sai krishnam raju potturi < >>> pskraj...@gmail.com> wrote: >>> > >>> > hi; >>> >would unsafeassasinating a dead node maintain the replication >>> factor like decommission process or removenode process? >>> > >>> > thanks >>> > >>> > >>> >> >
Re: Re : will Unsafeassaniate a dead node maintain the replication factor
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...@gmail.com> 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 > 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 >> 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 unsafe assanitation will not take care of >> replication factor . >> It is like forcing a node out from the cluster . >> >> Hope this helps. >> >> Sent from my iPhone >> >> > On Oct 31, 2015, at 5:12 AM, sai krishnam raju potturi < >> pskraj...@gmail.com> wrote: >> > >> > hi; >> >would unsafeassasinating a dead node maintain the replication factor >> like decommission process or removenode process? >> > >> > thanks >> > >> > >> >
Re: Re : will Unsafeassaniate a dead node maintain the replication factor
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 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 >> 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 unsafe assanitation will not take care of >> replication factor . >> It is like forcing a node out from the cluster . >> >> Hope this helps. >> >> Sent from my iPhone >> >> > On Oct 31, 2015, at 5:12 AM, sai krishnam raju potturi >> > wrote: >> > >> > hi; >> >would unsafeassasinating a dead node maintain the replication factor >> > like decommission process or removenode process? >> > >> > thanks >> > >> >
Re: Re : will Unsafeassaniate a dead node maintain the replication factor
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 > 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 unsafe assanitation will not take care of > replication factor . > It is like forcing a node out from the cluster . > > Hope this helps. > > Sent from my iPhone > > > On Oct 31, 2015, at 5:12 AM, sai krishnam raju potturi < > pskraj...@gmail.com> wrote: > > > > hi; > >would unsafeassasinating a dead node maintain the replication factor > like decommission process or removenode process? > > > > thanks > > > > >
Re: Re : Unable to bootstrap a new node
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 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 [HANDSHAKE-/Y.Y.Y.Y] INFO OutboundTcpConnection > Handshaking version with /Y.Y.Y.Y > 2015-10-31 12:30:46,743 [main] ERROR CassandraDaemon Exception encountered > during startup > java.lang.RuntimeException: Unable to gossip with any seeds > at org.apache.cassandra.gms.Gossiper.doShadowRound(Gossiper.java:1296) > at > org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:457) > at > org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:671) > at > org.apache.cassandra.service.StorageService.initServer(StorageService.java:623) > at > org.apache.cassandra.service.StorageService.initServer(StorageService.java:515) > at > org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:437) > at com.datastax.bdp.server.DseDaemon.setup(DseDaemon.java:423) > at > org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:567) > at com.datastax.bdp.server.DseDaemon.main(DseDaemon.java:641) > 2015-10-31 12:30:46,748 [Thread-5] INFO DseDaemon DSE shutting down... > 2015-10-31 12:30:46,760 [Thread-5] ERROR CassandraDaemon Exception in thread > Thread[Thread-5,5,main] > java.lang.NullPointerException > at > org.apache.cassandra.gms.Gossiper.addLocalApplicationState(Gossiper.java:1373) > at com.datastax.bdp.gms.DseState.setActiveStatus(DseState.java:171) > at com.datastax.bdp.server.DseDaemon.stop(DseDaemon.java:503) > at com.datastax.bdp.server.DseDaemon$1.run(DseDaemon.java:412) > 2015-10-31 12:30:46,846 [StorageServiceShutdownHook] WARN Gossiper No local > state or state is in silent shutdown, not announcing shutdown > 2015-10-31 12:30:46,846 [StorageServiceShutdownHook] INFO MessagingService > Waiting for messaging service to quiesce > 2015-10-31 12:30:46,847 [ACCEPT-/Z.Z.Z.Z] INFO MessagingService > MessagingService has terminated the accept() thread > > Thanks in advance for the help. >
Re: Re : will Unsafeassaniate a dead node maintain the replication factor
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 unsafe assanitation will not take care of replication factor . It is like forcing a node out from the cluster . Hope this helps. Sent from my iPhone > On Oct 31, 2015, at 5:12 AM, sai krishnam raju potturi > wrote: > > hi; >would unsafeassasinating a dead node maintain the replication factor like > decommission process or removenode process? > > thanks > >
Re : Unable to bootstrap a new node
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 [HANDSHAKE-/Y.Y.Y.Y] INFO OutboundTcpConnection Handshaking version with /Y.Y.Y.Y 2015-10-31 12:30:46,743 [main] ERROR CassandraDaemon Exception encountered during startup java.lang.RuntimeException: Unable to gossip with any seeds at org.apache.cassandra.gms.Gossiper.doShadowRound(Gossiper.java:1296) at org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:457) at org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:671) at org.apache.cassandra.service.StorageService.initServer(StorageService.java:623) at org.apache.cassandra.service.StorageService.initServer(StorageService.java:515) at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:437) at com.datastax.bdp.server.DseDaemon.setup(DseDaemon.java:423) at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:567) at com.datastax.bdp.server.DseDaemon.main(DseDaemon.java:641) 2015-10-31 12:30:46,748 [Thread-5] INFO DseDaemon DSE shutting down... 2015-10-31 12:30:46,760 [Thread-5] ERROR CassandraDaemon Exception in thread Thread[Thread-5,5,main] java.lang.NullPointerException at org.apache.cassandra.gms.Gossiper.addLocalApplicationState(Gossiper.java:1373) at com.datastax.bdp.gms.DseState.setActiveStatus(DseState.java:171) at com.datastax.bdp.server.DseDaemon.stop(DseDaemon.java:503) at com.datastax.bdp.server.DseDaemon$1.run(DseDaemon.java:412) 2015-10-31 12:30:46,846 [StorageServiceShutdownHook] WARN Gossiper No local state or state is in silent shutdown, not announcing shutdown 2015-10-31 12:30:46,846 [StorageServiceShutdownHook] INFO MessagingService Waiting for messaging service to quiesce 2015-10-31 12:30:46,847 [ACCEPT-/Z.Z.Z.Z] INFO MessagingService MessagingService has terminated the accept() thread Thanks in advance for the help.
Re : will Unsafeassaniate a dead node maintain the replication factor
hi; would unsafeassasinating a dead node maintain the replication factor like decommission process or removenode process? thanks
