Hello Kurt,
We are using V 3.11.0 and I think this might a part of a bigger problem. I can
see that nodes are failing in my cluster unexpectedly and also repair commands
are failing.
Repair command failure error:
INFO [Native-Transport-Requests-2] 2017-12-19 17:06:02,332 Message.java:619
Hi,
I'm getting below error for all sstable tools.
sstabledump mc-173-big-Data.db
Exception in thread "main" java.lang.ExceptionInInitializerError
Caused by: org.apache.cassandra.exceptions.ConfigurationException:
Expecting URI in variable: [cassandra.config]. Found[cassandra.yaml].
Please
Can you send through the full stack trace as reported in the Cassandra
logs? Also, what version are you running?
On 19 Dec. 2017 9:23 pm, "Dipan Shah" wrote:
> Hello,
>
>
> I am getting an error message when I'm running a select query from 1
> particular node. The error
Hello all,
We have a small cluster (3.11.1) with JBOD and with disk_failure_policy =
best_effort.
- How do I check if a drive has become blacklisted by Cassandra due to
failure?
- Would you recommend to switch back to the default disk_failure_policy =
stop which would be easier to check for
Hi,
Sure! I attached the jstack dumps on the ticket.
Hannu
On 19 December 2017 at 14:38:45, Jeff Jirsa (jji...@gmail.com) wrote:
Can you grab a thread dump with jstack as well?
--
Jeff Jirsa
On Dec 19, 2017, at 3:32 AM, Hannu Kröger wrote:
Hi,
I opened a ticket about
Can you grab a thread dump with jstack as well?
--
Jeff Jirsa
> On Dec 19, 2017, at 3:32 AM, Hannu Kröger wrote:
>
> Hi,
>
> I opened a ticket about nodetool compactionstats hanging:
> https://issues.apache.org/jira/browse/CASSANDRA-14130
>
> The root cause seems to be
Hi,
I opened a ticket about nodetool compactionstats hanging:
https://issues.apache.org/jira/browse/CASSANDRA-14130
The root cause seems to be JMX metric fetching hanging. I was able to
replicate it on this problematic like this:
Welcome to JMX terminal. Type "help" for available commands.
Hello,
I am getting an error message when I'm running a select query from 1 particular
node. The error is "ServerError: java.lang.IllegalStateException: Unable to
compute ceiling for max when histogram overflowed".
Has anyone faced this error earlier? I tried to search for this but did not
Any specific reason why It doesn't work across major version ? a
On Fri, Dec 15, 2017 at 12:05 AM, Jon Haddad wrote:
> Heh, hit send accidentally.
>
> You generally can’t run rebuild to upgrade, because it’s a streaming
> operation. Streaming isn’t supported between
12 matches
Mail list logo