Hi All,
I was wondering if there is going to be a C* summit this year? If so, when
can we expect?
Thanks!
We upgraded from 2.2.5 to 3.0.11 and it works fine. I will suggest not to go
with 3.013, we are seeing some issues with schema mismatch due to which we had
to rollback to 3.0.11.
Thanks,
Varun
> On May 19, 2017, at 7:43 AM, Stefano Ortolani wrote:
>
> Here
Yes the bugs need to be fixed, but as a work around on dev environment, you can
enable cassandra.yaml option to override any corrupted commit log file.
Thanks,
Varun
> On May 19, 2017, at 11:31 AM, Jeff Jirsa wrote:
>
>
>
>> On 2017-05-19 08:13 (-0700), Haris Altaf
50% free is unnecessary. The only reason to keep that much free is if you
wanted to regularly run major compactions, which you shouldn't.
I'd aim for 75%. Bootstrap new nodes in when you get close to that
number. Ensure you don't have any sstables larger than your available
space and you'll be
On 2017-05-19 08:13 (-0700), Haris Altaf wrote:
> Hi All,
> I am using Cassandra 3.10 for my project and whenever my local windows
> system, which is my development environment, crashes then cassandra server
> is unable to start. I have to delete commitlog directory after
Asad,
Ideally you should keep 50% free disk space. Yes, right now you have good
option to scale horizontally or add more disk space if you can. Adding more
nodes will give you more scalability for reads/writes and disk space will just
give you more capacity for current load.
Sent from my
500 nodes, 20tb of ACTIVE DATA per node in hdfs, no brainer, no problem.
But remember the cross DC traffic will get substantial.
“All men dream, but not equally. Those who dream by night in the dusty
recesses of their minds wake up in the day to find it was vanity, but the
dreamers of the day are
Hello Folks -
I'm using open source apache Cassandra 2.2 .My cluster is spread over 14 nodes
in cluster in two data centers.
My DC1 data center nodes are reaching 2TB of consumed volume. we don't have
much space left on disk.
I am wondering if there is guideline available that can point me to
I have seen this happen as well. Deleting commit logs helps to Cassandra start
but of course if you are very unlucky you might lose some data.
Hannu
> On 19 May 2017, at 18.13, Haris Altaf wrote:
>
> Hi All,
> I am using Cassandra 3.10 for my project and whenever my
Hi All,
I am using Cassandra 3.10 for my project and whenever my local windows
system, which is my development environment, crashes then cassandra server
is unable to start. I have to delete commitlog directory after every system
crash. This is actually annoying and what's the purpose of commitlog
Here (https://github.com/apache/cassandra/blob/cassandra-3.0/NEWS.txt) is
stated that the minimum supported version for the 2.2.X branch is 2.2.2.
On Fri, May 19, 2017 at 2:16 PM, Nicolas Guyomar
wrote:
> Hi Xihui,
>
> I was looking for this documentation also, but I
Hi Xihui,
I was looking for this documentation also, but I believe datastax removed
it, and it is not available yet on the apache website
As far as I remember, intermediate version was needed if C* Version <
2.1.7.
You should be safe starting from 2.2.6, but testing the upgrade on a
dedicated
Hi All,
We are planning to upgrade our production cluster to 3.x, but I can't find
the upgrade guide anymore.
Can I upgrade to 3.0.13 from 2.2.6 directly? Is a interim version necessary?
Thanks,
Xihui
Hi Team,
Just as Information, When Data modeling Document will be published on
official link.
Waiting for its so long time.
Please update the document. Currently no any documents present. And please
put document, which can be understood by the absolute beginner as well as
others also.
Thanks in
14 matches
Mail list logo