Re: Cassandra is not running

Thankyou everyone On 13 Feb 2018 8:50 p.m., "Michael Shuler" wrote: > On 02/13/2018 09:45 AM, Jürgen Albersdorfer wrote: > > 1.8.0_161 is not yet supported - try 1.8.0_151 > > > >> Am 13.02.2018 um 16:44 schrieb Irtiza Ali >> >: > >>

Re: Cassandra is not running

On 02/13/2018 09:45 AM, Jürgen Albersdorfer wrote: > 1.8.0_161 is not yet supported - try 1.8.0_151 > >> Am 13.02.2018 um 16:44 schrieb Irtiza Ali > >: >> >> 1.8.0_161 > Or install the 3.11.2 tentative release, which should work fine on 1.8.0_161.

RE: Cassandra is not running

Adding known issue reference and fix versions: CASSANDRA-14173<https://issues.apache.org/jira/browse/CASSANDRA-14173> Fix Version/s: 3.11.2/4.0 From: Jürgen Albersdorfer [mailto:jalbersdor...@gmail.com] Sent: Tuesday, February 13, 2018 9:45 AM To: user@cassandra.apache.org Subject: Re: Cas

Re: Cassandra is not running

Downgrade your Java version please On Feb 13, 2018 11:46 PM, "Irtiza Ali" wrote: > Thank you > > On 13 Feb 2018 20:45, "Jürgen Albersdorfer" > wrote: > >> 1.8.0_161 is not yet supported - try 1.8.0_151 >> >> Am 13.02.2018 um 16:44 schrieb Irtiza Ali

Re: Cassandra is not running

Thank you On 13 Feb 2018 20:45, "Jürgen Albersdorfer" wrote: > 1.8.0_161 is not yet supported - try 1.8.0_151 > > Am 13.02.2018 um 16:44 schrieb Irtiza Ali : > > 1.8.0_161 > > >

Re: Cassandra is not running

1.8.0_161 is not yet supported - try 1.8.0_151 > Am 13.02.2018 um 16:44 schrieb Irtiza Ali : > > 1.8.0_161

Re: Cassandra is not running

t;>>>Loaded: loaded (/etc/init.d/cassandra; bad; vendor preset: enabled) >>>>>Active: active (exited) since 2018-02-13 19:57:51 PKT; 31s ago >>>>> Docs: man:systemd-sysv-generator(8) >>>>> Process: 28844 ExecStop=/etc/init.d/cassandra stop (code=exited, >>>>> status=0/SUCCESS) >>>>> Process: 28929 ExecStart=/etc/init.d/cassandra start (code=exited, >>>>> status=0/SUCCESS) >>>>> >>>>> Anyone knows why cassandra is not running properly? >>>>> >>>>> With Regards >>>>> Irtiza Ali >>>>> >>>> >>>>

Re: Cassandra is not running

.d/cassandra; bad; vendor preset: enabled) >>>>Active: active (exited) since 2018-02-13 19:57:51 PKT; 31s ago >>>> Docs: man:systemd-sysv-generator(8) >>>> Process: 28844 ExecStop=/etc/init.d/cassandra stop (code=exited, >>>> status=0/SUCCESS) >>>> Process: 28929 ExecStart=/etc/init.d/cassandra start (code=exited, >>>> status=0/SUCCESS) >>>> >>>> Anyone knows why cassandra is not running properly? >>>> >>>> With Regards >>>> Irtiza Ali >>>> >>> >>>

Re: Cassandra is not running

t.d/cassandra; bad; vendor preset: enabled) >>>Active: active (exited) since 2018-02-13 19:57:51 PKT; 31s ago >>> Docs: man:systemd-sysv-generator(8) >>> Process: 28844 ExecStop=/etc/init.d/cassandra stop (code=exited, >>> status=0/SUCCESS) >>> Process: 28929 ExecStart=/etc/init.d/cassandra start (code=exited, >>> status=0/SUCCESS) >>> >>> Anyone knows why cassandra is not running properly? >>> >>> With Regards >>> Irtiza Ali >>> >> >>

Re: Cassandra is not running

ss: 28844 ExecStop=/etc/init.d/cassandra stop (code=exited, >> status=0/SUCCESS) >> Process: 28929 ExecStart=/etc/init.d/cassandra start (code=exited, >> status=0/SUCCESS) >> >> Anyone knows why cassandra is not running properly? >> >> With Regards >> Irtiza Ali >> > >

Re: Cassandra is not running

2018-02-13 19:57:51 PKT; 31s ago > Docs: man:systemd-sysv-generator(8) > Process: 28844 ExecStop=/etc/init.d/cassandra stop (code=exited, > status=0/SUCCESS) > Process: 28929 ExecStart=/etc/init.d/cassandra start (code=exited, > status=0/SUCCESS) > > Anyone knows w

Cassandra is not running

) since 2018-02-13 19:57:51 PKT; 31s ago Docs: man:systemd-sysv-generator(8) Process: 28844 ExecStop=/etc/init.d/cassandra stop (code=exited, status=0/SUCCESS) Process: 28929 ExecStart=/etc/init.d/cassandra start (code=exited, status=0/SUCCESS) Anyone knows why cassandra is not running

Re: Cassandra 2.1: replace running node without streaming

On Sat, Feb 3, 2018 at 11:23 AM, Kyrylo Lebediev wrote: > Just tested on 3.11.1 and it worked for me (you may see the logs below). > > Just comprehended that there is one important prerequisite this method to > work: new node MUST be located in the same rack (in terms

Re: Cassandra 2.1: replace running node without streaming

/2016/01/26/cassandra-instantaneous-in-place-node-replacement > > Thank you for your readiness to help! > > Kind Regards, > Kyrill > From: Kyrylo Lebediev <kyrylo_lebed...@epam.com> > Sent: Saturday, February 3, 2018 12:23:15 PM > To: User > Subject: Re: Cassandra 2.1:

Re: Cassandra 2.1: replace running node without streaming

From: Kyrylo Lebediev <kyrylo_lebed...@epam.com> Sent: Saturday, February 3, 2018 12:23:15 PM To: User Subject: Re: Cassandra 2.1: replace running node without streaming Thank you Oleksandr, Just tested on 3.11.1 and it worked for me (you may see the logs

Re: Cassandra 2.1: replace running node without streaming

<oleksandr.shul...@zalando.de> Sent: Saturday, February 3, 2018 10:44:26 AM To: User Subject: Re: Cassandra 2.1: replace running node without streaming On 3 Feb 2018 08:49, "Jürgen Albersdorfer" <jalbersdor...@gmail.com<mailto:jalbersdor...@gmail.com>> wrote: Co

Re: Cassandra 2.1: replace running node without streaming

e affected node addresses. Be careful though, to make sure that you put the data directory exactly where the new node expects to find it: otherwise it might just join as a brand new one, allocating new tokens. As a precaution it helps to ensure that the system user running the Cassandra proc

Re: Cassandra 2.1: replace running node without streaming

d log something like "ignoring IP address > change" for the affected node addresses. > > Be careful though, to make sure that you put the data directory exactly where > the new node expects to find it: otherwise it might just join as a brand new > one, allocating new toke

Re: Cassandra 2.1: replace running node without streaming

ing like "ignoring IP address change" for the affected node addresses. Be careful though, to make sure that you put the data directory exactly where the new node expects to find it: otherwise it might just join as a brand new one, allocating new tokens. As a precaution it helps to ensure that the

Re: Cassandra 2.1: replace running node without streaming

? Regards, Kyrill From: Oleksandr Shulgin <oleksandr.shul...@zalando.de> Sent: Friday, February 2, 2018 4:26:30 PM To: User Subject: Re: Cassandra 2.1: replace running node without streaming On Fri, Feb 2, 2018 at 3:15 PM, Kyrylo Lebediev <kyrylo_lebed...

Re: Cassandra 2.1: replace running node without streaming

On Fri, Feb 2, 2018 at 3:15 PM, Kyrylo Lebediev wrote: > Hello All! > > I've got a pretty standard task - to replace a running C* node [version > 2.1.15, vnodes=256, Ec2Snitch] (IP address will change after replacement, > have no control over it). > > There are 2 ways

Cassandra 2.1: replace running node without streaming

Hello All! I've got a pretty standard task - to replace a running C* node [version 2.1.15, vnodes=256, Ec2Snitch] (IP address will change after replacement, have no control over it). There are 2 ways stated in C* documentation how this can be done: 1) Add a new node, than 'nodetool

Ran into an issue where Cassandra Crashed when running out of heap space

 INFO [HINTED-HANDOFF-POOL:1] 2010-07-20 15:10:43,721 HintedHandOffManager.java (line 210) Finished hinted handoff of 0 rows to endpoint /10.129.28.23 ERROR [pool-1-thread-37895] 2010-07-20 15:10:51,622 CassandraDaemon.java (line 83) Uncaught exception in thread Thread[pool-1-thread-37895,5,main]

Re: Ran into an issue where Cassandra Crashed when running out of heap space

CassandraDaemon.java (line 83) Uncaught exception in thread Thread[pool-1-thread-37895,5,main] java.lang.OutOfMemoryError: Java heap space     at org.apache.thrift.protocol.TBinaryProtocol.readStringBody(TBinaryProtocol.java:296)     at

Re: Ran into an issue where Cassandra Crashed when running out of heap space

The storage structure is rather simple. For every 1 key there is 1 column and a timestamp for that column. ColumnFamily Name=Standard2 CompareWith=UTF8Type / We don't enable pulling a huge amount of data and all other nodes are up servicing the same request. I suspect there may be another

Re: Ran into an issue where Cassandra Crashed when running out of heap space

Attaching Jconsole shows that there is a growth of memory and weird spikes. Unfortunately I did not take a screen shot of the growth of the spike over time. I'll do that when it occurs again. Note that expected behavior for CMS is to have lots of small ups and downs as a result of young

Re: Ran into an issue where Cassandra Crashed when running out of heap space

On Tue, Jul 20, 2010 at 1:28 PM, Peter Schuller peter.schul...@infidyne.com wrote: Attaching Jconsole shows that there is a growth of memory and weird spikes. Unfortunately I did not take a screen shot of the growth of the spike over time. I'll do that when it occurs again. Note that expected

Cassandra tuning for running test on a desktop

Hello, For my first message I will first thanks Cassandra contributors for their great works. I have a parameter issue with Cassandra (I hope it's just a parameter issue). I'm using Cassandra 6.0.1 with Hector client on my desktop. It's a simple dual core with 4GB of RAM on WinXP. I have keep

Re: Cassandra tuning for running test on a desktop

I have try 1400M, and Cassandra OOM too. Is there another solution ? My data isn't very big. It seems that is the merge of the db On Wed, Apr 21, 2010 at 2:14 PM, Mark Greene green...@gmail.com wrote: Trying increasing Xmx. 1G is probably not enough for the amount of inserts you are doing.

Re: Cassandra tuning for running test on a desktop

Jones mjo...@imagehawk.com wrote: On my 4GB machine I’m giving it 3GB and having no trouble with 60+ million 500 byte columns *From:* Nicolas Labrot [mailto:nith...@gmail.com] *Sent:* Wednesday, April 21, 2010 7:47 AM *To:* user@cassandra.apache.org *Subject:* Re: Cassandra tuning

Re: Cassandra tuning for running test on a desktop

Hit send to early That being said a lot of people running Cassandra in production are using 4-6GB max heaps on 8GB machines, don't know if that helps but hopefully gives you some perspective. On Wed, Apr 21, 2010 at 10:39 AM, Mark Greene green...@gmail.com wrote: RAM doesn't necessarily

Re: Cassandra tuning for running test on a desktop

Thanks Mark. Cassandra is maybe too much for my need ;) On Wed, Apr 21, 2010 at 4:45 PM, Mark Greene green...@gmail.com wrote: Hit send to early That being said a lot of people running Cassandra in production are using 4-6GB max heaps on 8GB machines, don't know if that helps

Re: Cassandra tuning for running test on a desktop

;) On Wed, Apr 21, 2010 at 4:45 PM, Mark Greene green...@gmail.com wrote: Hit send to early That being said a lot of people running Cassandra in production are using 4-6GB max heaps on 8GB machines, don't know if that helps but hopefully gives you some perspective. On Wed, Apr 21, 2010

Re: Cassandra tuning for running test on a desktop

That being said a lot of people running Cassandra in production are using 4-6GB max heaps on 8GB machines, don't know if that helps but hopefully gives you some perspective. On Wed, Apr 21, 2010 at 10:39 AM, Mark Greene green...@gmail.comwrote: RAM doesn't necessarily need to be proportional