Re: Public Interface Failure in Multiple DC setup

Hi  Can someone take these questions? ThanksAnuj On Thu, 11 Aug, 2016 at 8:30 PM, Anuj Wadehra wrote: Hi, Setup: Cassandra 2.0.14 with PropertyFileSnitch. 2 Data Centers. Every node has broadcast address= Public IP (bond0) & listen address=Private IP (bond1). As

Corrupt SSTABLE over and over

Hi, I have a 16 Node cluster, Cassandra 2.2.1 on Windows, local installation (NOT on the cloud) and I am getting Error [CompactionExecutor:2] 2016-08-12 06:51:52, 983 Cassandra Daemon.java:183 - Execption in thread Thread[CompactionExecutor:2,1main] org.apache.cassandra.io.FSReaderError:

Re: nodetool repair with -pr and -dc

-D does not do what you think it does. I've quoted the relevant documentation from the README: > > Multiple > Datacenters > > If you have multiple datacenters in your ring, then you MUST specify the > name of the

Re: migrating from 2.1.2 to 3.0.8 log errors

After migrating C* from 2.1.2 to 3.0.8, all queries with the where condition involved ad indexed column return zero rows for the old data, instead news inserted data are returned from the same query, I'm guessing that something was remained incomplete about indexes, should we run rebuild indexes?

Re: Question nodetool status

Hi, thanks a lot for answer :) Gossip is a peer-to-peer communication protocol in which nodes periodically exchange state information about themselves and about other nodes they know about. unreachableNodes = probe.getUnreachableNodes(); ---> i.e if node don't publish heartbeats on x seconds

Public Interface Failure in Multiple DC setup

Hi, Setup: Cassandra 2.0.14 with PropertyFileSnitch. 2 Data Centers. Every node has broadcast address= Public IP (bond0) & listen address=Private IP (bond1). As per DataStax docs, (https://docs.datastax.com/en/cassandra/2.0/cassandra/configuration/configMultiNetworks.html), "For

Re: Question nodetool status

Hi Jean Paul, Yes, the gossiper is used. Example with down nodes:1. The status command retrieve unreachable nodes from a NodeProbe instance:  https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/tools/nodetool/Status.java#L64 2. The NodeProbe list comes from a

Re: nodetool repair with -pr and -dc

> if we want to use -pr option ( which i suppose we should to prevent duplicate checks) in 2.0 then if we run the repair on all nodes in a single DC then it should be sufficient and we should not need to run it on all nodes across DC's? No, because the primary ranges of the nodes in other DCs

Question nodetool status

Hi all, *$nodetool status*Datacenter: datacenter1 === Status=Up/Down |/ State=Normal/Leaving/Joining/Moving -- AddressLoad Tokens Owns (effective) Host ID Rack *UN 127.0.0.1 83.05 KB 256 100.0%

Re: JVM Crash on 3.0.6

Not really related, but know that on 12.04 I had to disable jemalloc, otherwise nodes would randomly die at startup ( https://issues.apache.org/jira/browse/CASSANDRA-11723) Regards, Stefano On Thu, Aug 11, 2016 at 10:28 AM, Riccardo Ferrari wrote: > Hi C* users, > > In

JVM Crash on 3.0.6

Hi C* users, In recent time I had couple of my nodes crashing (on different dates). I don't have core dumps however my JVM crash logs goes like this: === # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at