There is a jira ticket describing your situation
https://issues.apache.org/jira/plugins/servlet/mobile#issue/CASSANDRA-14793
I may be wrong but is seems that system directories are pinned to first
data directory in cassandra.yaml by default. When you removed first item
from the list system data re
If the table has zero rows you could truncate it
On Mon, Oct 25, 2021 at 6:29 PM Joe Obernberger <
joseph.obernber...@gmail.com> wrote:
> Update - after 10 days, I'm able to use the table again; prior to that all
> selects timed out.
> Are deletes basically forbidden with Cassandra? If you have
Hi,
You could try to run full repair over short subrange containing data
missing from one replica. It should take just couple of minutes and will
prove if your repair failed to finish
Dmitrii Saprykin
On Tue, Oct 12, 2021 at 7:54 AM Bowen Song wrote:
> I see. In that case, I suspect the repair
I had the same warning for nodetool upgradesstables. Nodetool just checks
wrong location. CASSANDRA-16104
On Fri, Aug 6, 2021 at 9:28 PM Erick Ramirez
wrote:
> I'd say that your `data_file_directories` is pointing at
> /var/lib/cassandra/data and is mounted on the root volume instead of
> /srv/
che/cassandra/commit/d60c78358b6f599a83f3c112bfd6ce72c1129c9f#diff-62875acfa21fb24c7167a0a2d761780e>
:
129
// md (3.0.18, 3.11.4): corrected sstable min/max clustering
Dmitry Saprykin
On Thu, Apr 4, 2019 at 11:23 AM Léo FERLIN SUTTON
wrote:
> Hello !
>
> I have noticed something sinc
See more here
https://issues.apache.org/jira/plugins/servlet/mobile#issue/CASSANDRA-13004
On Sat, Dec 1, 2018 at 1:02 PM Dmitry Saprykin
wrote:
> Even more, 3.0.9 is a terrible target choice by itself. It has a nasty bug
> corrupting sstables on alter.
>
> On Sat, Dec 1, 2018 at 1
Even more, 3.0.9 is a terrible target choice by itself. It has a nasty bug
corrupting sstables on alter.
On Sat, Dec 1, 2018 at 11:55 AM Marc Selwan
wrote:
> Hi Shravan,
>
> Did you upgrade Apache Cassandra 2.1.9 to the latest patch release before
> doing the major upgrade? It's generally favora
You need to move you files into directory named 'cass_testapp/table3/'.
sstable loader uses 2 last path components as keyspace and table names.
On Fri, Nov 30, 2018 at 11:54 AM Oliver Herrmann
wrote:
> When using nodetool refresh I must have write access to the data folder
> and I have to do it
Be sure you have an snapshot of the table source and ignore step 4 of
> course
>
>
> Saludos
>
> Jean Carlo
>
> "The best way to predict the future is to invent it" Alan Kay
>
> On Sun, Apr 8, 2018 at 6:33 PM, Dmitry Saprykin > wrote:
>
>> You can copy
You can copy hardlinks to ALL SSTables from old to new table and then
delete part of data you do not need in a new one.
On Sun, Apr 8, 2018 at 10:20 AM, Nitan Kainth wrote:
> If it for testing and you don’t need any specific data, just copy a set of
> sstables with all files of that sequence and
Hi,
I successfully used 3.0.14 more than a year in production. And moreover
3.0.10 is definitely not stable and you need to upgrade ASAP. 3.0.10
contains known bug which corrupts data during schema changes
Regards,
Dmitrii
On Fri, Mar 23, 2018 at 5:01 PM Nitan Kainth wrote:
> Hi All,
>
> Our r
plain your results.
Also you can think using LOCAL_ONE consistency for your full scans. You may
lose some consistency but will gain a log of performance improvements.
Kind regards,
Dmitry Saprykin
On Thu, Aug 17, 2017 at 12:36 PM, Alex Kotelnikov <
alex.kotelni...@diginetica.com> wrote:
> Do
12 matches
Mail list logo
