Hi,
I'm getting the following error on the node when trying to connect to Cassandra
through cqlsh with SSL enabled:
io.netty.handler.codec.DecoderException: javax.net.ssl.SSLHandshakeException:
Client requested protocol TLSv1 not enabled or not supported
I'm running the C* code (based on trun
Hi ,
I am getting the below issue while creating a role in Cassandra.
Single node , Cqlsh is pointing to '127.0.0.1'.
[cid:image001.png@01D358C3.8ABF82B0]
Can anyone help me in this issue?
Thanks,
Bhargav
Unavailable indicates that the number of nodes it needs for the query to
succeed are known to be down
Either it’s a single node that thinks it’s more than one node and others are
down (like you added/removed nodes to that cluster in the past), or your
replication strategy for system_auth is wro
Hello,
We run Cassandra 2.1.13 and since last few days we're seeing below in logs
occasionally. The node then becomes unresponsive to cqlsh.
ERROR [SharedPool-Worker-2] 2017-11-08 17:02:32,362 CommitLogSegment.java:441 -
Attempted to write commit log entry for unrecognized column family:
2854d
It looks like you have a schema disagreement in your cluster which you need
to look into.
And you're right since that column family ID is equivalent to Friday, June
24, 2016 10:14:49 AM PDT.
Have a look at the table IDs in system.schema_columnfamilies for clues.
Cheers!
On Thu, Nov 9, 2017 at 4:
You can continue to perform operations while running a repair but just be
aware that you will get repair failures, e.g. if you drop a table while
that table is getting repaired. In which case, the failure is benign.
Creating new keyspaces or tables will not pose any problems for the repair
session
system.local only contains a single partition with key='local'. There won't
be anything to repair for it since it only contains data about that node,
e.g. saved tokens, cluster name, etc. Cheers!
On Wed, Nov 8, 2017 at 5:03 AM, Riccardo Ferrari wrote:
> Thanks you Adama,
>
> Even though it refer
