On Sat, Dec 6, 2014 at 8:05 AM, Eric Stevens wrote:
> The official recommendation is 100k:
> http://www.datastax.com/documentation/cassandra/2.0/cassandra/install/installRecommendSettings.html
>
> I wonder if there's an advantage to this over unlimited if you're running
> servers which are dedicat
The official recommendation is 100k:
http://www.datastax.com/documentation/cassandra/2.0/cassandra/install/installRecommendSettings.html
I wonder if there's an advantage to this over unlimited if you're running
servers which are dedicated to your Cassandra cluster (which you should be
for anything
On Wed, Dec 3, 2014 at 6:37 AM, Rafał Furmański
wrote:
> I see “Too many open files” exception in logs, but I’m sure that my limit
> is now 150k.
> Should I increase it? What’s the reasonable limit of open files for
> cassandra?
Why provide any limit? ulimit allows "unlimited"?
=Rob
I see “Too many open files” exception in logs, but I’m sure that my limit is
now 150k.
Should I increase it? What’s the reasonable limit of open files for cassandra?
On 3 gru 2014, at 15:02, Yuki Morishita wrote:
> As the exception indicates, nodetool just lost communication with the
> Cassandr
As the exception indicates, nodetool just lost communication with the
Cassandra node and cannot print progress any further.
Check your system.log on the node, and see if your repair was
completed. If there is no error, then it should be fine.
On Wed, Dec 3, 2014 at 5:08 AM, Rafał Furmański wrote:
Hi All!
We have a 8 nodes cluster in 2 DC (4 per DC, RF=3) running Cassandra 2.1.2 on
Linux Debian Wheezy.
I executed “nodetool repair” on one of the nodes, and this command returned
following error:
Exception occurred during clean-up.
java.lang.reflect.UndeclaredThrowableException
error: JMX
