Re: Maximum and recommended storage per node

There are many different recommendations floating around, typically the limit depends on how well you know Cassandra and your workload. If your workload is CPU bound, you should go for more, less dense nodes. If not, you can sustain higher data density per node. Typically I'd say the usable range

Re: java.lang.UnsatisfiedLinkError on CentOS 6.5 VM

Hi Piet,I have also encountered this situation, when I installed Cassandra 3.11.0 on RHEL .  It seems complain of low GLIBC version. Then I use an older version of Cassandra 3.9.0.  It works. Thanks.RyanOn 07/28/2017 22:31，piet molenaar wrote： Hi, I've installed Cassandra on a Ce

Cassandra + Stratio’s Cassandra Lucene Index for online quering

Considering that Stratio’s Cassandra Lucene Index, "..is a plugin for Apache Cassandra that extends its index functionality to provide near real time search such as ElasticSearch or Solr..". Can I use Stratio’s Cassandra Lucene Index to build a online reporting functionality within my applicat

java.lang.UnsatisfiedLinkError on CentOS 6.5 VM

Hi, I've installed Cassandra on a CentOS cluster of VM's When starting up Cassandra gives OK but when actually checking the nodetool status this gives a connection error, and when checking Cassandra is in fact not running at all. The log shows problems: ERROR [main] 2017-07-28 14:03:56,958 Native

Re: Maximum and recommended storage per node

Hi Kiran, Is this raw storage size per node or allowed data per node? Can you provide links or articles about those recommendations? On 28 July 2017 at 12:45, Kiran mk wrote: > Recommended is 4TB per node > > Best regards, > Koran.M.K > > On 28-Jul-2017 1:57 PM, "CPC" wrote: > >> Hi all, >> >>

Re: Unable to connect to C* nodes except one node (same configuration)

figured out the problems, node 1 has configuration error due to a problem in ansible script, which set rpc_address to localhost. On node 3, after clearing the logs and restarting I saw this in log file INFO [main] 2017-07-26 09:26:36,938 Server.java:160 - Starting listening for CQL clients on /10

Re: Maximum and recommended storage per node

Recommended is 4TB per node Best regards, Koran.M.K On 28-Jul-2017 1:57 PM, "CPC" wrote: > Hi all, > > Is there any recommended and maximum storage per node? In old articles > 1tb per node was maximum but is it still apply. Or is it just depends on > our latency requirements? Can you share you

Maximum and recommended storage per node

Hi all, Is there any recommended and maximum storage per node? In old articles 1tb per node was maximum but is it still apply. Or is it just depends on our latency requirements? Can you share your production experiences? Thank you...