Hi Christian,
C* 2.2.7 doesn't cause this problem.
I can always reproduce it on some servers and my laptop by using 2.2.6.
I reviewed the source code of 2.2.7.
The above ReplayPosition updating was fixed.
Thank you for your cooperation.
yuji
On Thu, Aug 25, 2016 at 11:40 PM, horschi wrote:
>
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
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,
(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
Hi,
I can reproduce the problem with the following script.
I got rows which should be truncated.
If truncating is executed only once, the problem doesn't occur.
The test for multi nodes (replication_factor:3, kill & restart C* processes
in all nodes) can also reproduce it.
test script:
ip=
Hi Yuji,
ok, perhaps you are seeing a different issue than I do.
Have you tried with durable_writes=False? If the issue is caused by the
commitlog, then it should work if you disable durable_writes.
Cheers,
Christian
On Tue, Aug 9, 2016 at 3:04 PM, Yuji Ito wrote:
> Thanks Christian
>
> can
Thanks Christian
can you reproduce the behaviour with a single node?
I tried my test with a single node. But I can't.
This behaviour is seems to be CQL only, or at least has gotten worse with
> CQL. I did not experience this with Thrift.
I truncate tables with CQL. I've never tried with Thrift.
Hi Yuji,
can you reproduce the behaviour with a single node?
The reason I ask is because I probably have the same issue with my
automated tests (which run truncate between every test), which run on my
local laptop.
Maybe around 5 tests randomly fail out of my 1800. I can see that the
failed test
Hi all,
I have a question about clearing table and commit log replay.
After some tables were truncated consecutively, I got some stale values.
This problem doesn't occur when I clear keyspaces with DROP (and CREATE).
I'm testing the following test with node failure.
Some stale values appear at ch
10 matches
Mail list logo
