Thanks Alexander.
1. No reads and writes were enabled during repair on keyspace.
2. All repairs were started sequentially on all nodes one by one (new
repair started after repair completeon on previous node)
I'll dig deeper into the logs, maybe there are some records about reason
why some sstables
There are 2 main reasons I see for still having unrepaired sstables after
running nodetool repair -pr :
1- new data is still flowing in your database after the repair sessions
were launched, and thus hasn't been repaired
2- some repair sessions failed and left unrepaired data on your nodes.
Increm
Thanks for confirmation Paulo. Then my understanding of proccess was
correct.
I'm curious why I still see unrepaired sstables after performing repair -pr
on all nodes in all datacenters...
пт, 26 Авг 2016 г., 3:25 Paulo Motta :
> 1. Migration procedure is no longer necessary after CASSANDRA-8004
1. Migration procedure is no longer necessary after CASSANDRA-8004, and
since you never ran repair before this would not make any difference
anyway, so just run repair and by default (CASSANDRA-7250) this will
already be incremental.
2. Incremental repair is not supported with -pr, -local or -st/-e
I’m new in Cassandra and trying to figure out how to _start_ using
incremental repairs. I have seen article about “Migrating to incremental
repairs” but since I didn’t use repairs before at all and I use Cassandra
version v3.0.8, then maybe not all steps are needed which are mentioned in
Datastax a
This looks like you've run out of disk. What are your hardware specs?
Patrick
On Thursday, August 25, 2016, Benedict Elliott Smith
wrote:
> You should update from 2.0 to avoid this behaviour, is the simple answer.
> You are correct that when the commit log gets full the memtables are
> flushed
Nop, still don't get stale values. (I just ran your script 3 times)
On Thu, Aug 25, 2016 at 12:36 PM, Yuji Ito wrote:
> Thank you for testing, Christian
>
> What did you set commitlog_sync in cassandra.yaml?
> I set commitlog_sync batch (window 2ms) as below.
>
> commitlog_sync: batch
> commitlo
Hello to everyone, I'm pretty new to Cassandra and I'm working on PHP based
projects.
For interface PHP with Cassandra I use the DataStax PHP driver, which lately
has been updated to the version 1.2.2 and now I've a trouble while using LIST
data type: when I try to use a prepared statement and I
Thank you for testing, Christian
What did you set commitlog_sync in cassandra.yaml?
I set commitlog_sync batch (window 2ms) as below.
commitlog_sync: batch
commitlog_sync_batch_window_in_ms: 2
The problem didn't occur by setting commitlog_sync periodic(default).
regards,
yuji
On Thu, Aug 25,
You should update from 2.0 to avoid this behaviour, is the simple answer.
You are correct that when the commit log gets full the memtables are
flushed to make room. 2.0 has several interrelated problems here though:
There is a maximum flush queue length property (I cannot recall its name),
and on
Listen address is the network address the node will listen into.
Seeds is the contact points a node will use when bootstrapping to find a
cluster.
To make those four into a single cluster just start the first one with
himself as a seed and then sequentially bootstrap the others with the first
one
(running C* 2.2.7)
On Thu, Aug 25, 2016 at 11:10 AM, horschi wrote:
> Hi Yuji,
>
> I tried your script a couple of times. I did not experience any stale
> values. (On my Linux laptop)
>
> regards,
> Ch
>
> On Mon, Aug 15, 2016 at 7:29 AM, Yuji Ito wrote:
>
>> Hi,
>>
>> I can reproduce the probl
Hi Yuji,
I tried your script a couple of times. I did not experience any stale
values. (On my Linux laptop)
regards,
Ch
On Mon, Aug 15, 2016 at 7:29 AM, Yuji Ito wrote:
> Hi,
>
> I can reproduce the problem with the following script.
> I got rows which should be truncated.
> If truncating is e
Hello,
I am little bit confusing about cassandra's configuration.
There are 2 parameters which I don't understand:
listen_address
seeds
I have 4 identical nodes:
192.168.0.61 cassandra1
192.168.0.62 cassandra2
192.168.0.63 cassandra3
192.168.0.64 cassandra4
What shell I do to configure those 4 n
14 matches
Mail list logo
