did you make sure to run the sstable upgrade after you
>>> completed the move from 2.x to 3.x ?
>>>
>>>
>>>
>>> *From:* Evgeny Inberg [mailto:evg...@gmail.com]
>>> *Sent:* Thursday, May 02, 2019 1:31 AM
>>> *To:* user@cassandra.ap
ble upgrade after you
>> completed the move from 2.x to 3.x ?
>>
>>
>>
>> *From:* Evgeny Inberg [mailto:evg...@gmail.com]
>> *Sent:* Thursday, May 02, 2019 1:31 AM
>> *To:* user@cassandra.apache.org
>> *Subject:* Re: Cassandra taking very long to sta
May 02, 2019 1:31 AM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Cassandra taking very long to start and server under heavy
> load
>
>
>
> Using a sigle data disk.
>
> Also, it is performing mostly heavy read operations according to the
> metrics cillected.
>
Just curious but, did you make sure to run the sstable upgrade after you
completed the move from 2.x to 3.x ?
From: Evgeny Inberg [mailto:evg...@gmail.com]
Sent: Thursday, May 02, 2019 1:31 AM
To: user@cassandra.apache.org
Subject: Re: Cassandra taking very long to start and server under heavy
Using a sigle data disk.
Also, it is performing mostly heavy read operations according to the
metrics cillected.
On Wed, 1 May 2019, 20:14 Jeff Jirsa wrote:
> Do you have multiple data disks?
> Cassandra 6696 changed behavior with multiple data disks to make it safer
> in the situation that one
Do you have multiple data disks?
Cassandra 6696 changed behavior with multiple data disks to make it safer in
the situation that one disk fails . It may be copying data to the right places
on startup, can you see if sstables are being moved on disk?
--
Jeff Jirsa
> On May 1, 2019, at 6:04
