Hi,
This issue is related to
https://issues.apache.org/jira/browse/CASSANDRA-9630
Thanks and Regards
A.SathishKumar
On Sun, Dec 24, 2017 at 2:59 AM, sat wrote:
> Hi,
>
> We have 3 node cluster, before we reboot one of the VMWare VM/node (RHEL
> 7.2) all 3 nodes formed
Hi,
We have 3 node cluster, before we reboot one of the VMWare VM/node (RHEL
7.2) all 3 nodes formed the cluster without any issues. However after
reboot, we noticed rebooted node (7 out of 10 times) takes more time to
join approximately 10 - 15min.
Cassandra - 3.9 version
While investigating
Hi Jeff,
Thanks for your prompt response. Please find logs. Does Gossip has
dependency with NTP, because we find the node we reboot takes time to sync
with NTP.
When will FailureDetector message kick in, we have this issue only when we
see Gossiper and Failure Detector log message.
TRACE
Not received is ambiguous.
Can you paste the logs somewhere like pastebin? Sanitize/anonymize as needed.
--
Jeff Jirsa
> On Dec 21, 2017, at 9:15 PM, sat wrote:
>
> Hi,
>
> We observe gossip is not received by other nodes and we see "Convicted"
> message in
Hi,
We observe gossip is not received by other nodes and we see "Convicted"
message in debug.log even though cassandra process is running in all 3
nodes.
Thanks and Regards
A.SathisKumar
On Thu, Dec 21, 2017 at 9:12 PM, Jeff Jirsa wrote:
> What’s it logging?
>
> --
> Jeff
What’s it logging?
--
Jeff Jirsa
> On Dec 21, 2017, at 8:56 PM, sat wrote:
>
> We have configured 3 node cassandra cluster in RHEL 7.2 version and we are
> doing cluster testing. When we start cassandra in all 3 nodes they form a
> cluster and they work fine.
>
>
We have configured 3 node cassandra cluster in RHEL 7.2 version and we are
doing cluster testing. When we start cassandra in all 3 nodes they form a
cluster and they work fine.
But when we bring one node down using "init 6" or "reboot" command, the
rebooted node takes more time to join the