On Tue, Sep 18, 2018 at 10:38 AM Steinmaurer, Thomas <
thomas.steinmau...@dynatrace.com> wrote:
>
> any indications in Cassandra log about insufficient disk space during
> compactions?
>
Bingo! The following was logged around the time compaction was started
(and I only looked around when it was
Alex,
any indications in Cassandra log about insufficient disk space during
compactions?
Thomas
From: Oleksandr Shulgin
Sent: Dienstag, 18. September 2018 10:01
To: User
Subject: Major compaction ignoring one SSTable? (was Re: Fresh SSTable files
(due to repair?) in a static table (was Re:
On Mon, Sep 17, 2018 at 4:29 PM Oleksandr Shulgin <
oleksandr.shul...@zalando.de> wrote:
>
> Thanks for your reply! Indeed it could be coming from single-SSTable
> compaction, this I didn't think about. By any chance looking into
> compaction_history table could be useful to trace it down?
>
On Mon, Sep 17, 2018 at 4:41 PM Jeff Jirsa wrote:
> Marcus’ idea of row lifting seems more likely, since you’re using STCS -
> it’s an optimization to “lift” expensive reads into a single sstable for
> future reads (if a read touches more than - I think - 4? sstables, we copy
> it back into the
> On Sep 17, 2018, at 7:29 AM, Oleksandr Shulgin
> wrote:
>
> On Mon, Sep 17, 2018 at 4:04 PM Jeff Jirsa wrote:
>>> Again, given that the tables are not updated anymore from the application
>>> and we have repaired them successfully multiple times already, how can it
>>> be that any
On Mon, Sep 17, 2018 at 4:04 PM Jeff Jirsa wrote:
> Again, given that the tables are not updated anymore from the application
> and we have repaired them successfully multiple times already, how can it
> be that any inconsistency would be found by read-repair or normal repair?
>
> We have seen
It could also be https://issues.apache.org/jira/browse/CASSANDRA-2503
On Mon, Sep 17, 2018 at 4:04 PM Jeff Jirsa wrote:
>
>
> On Sep 17, 2018, at 2:34 AM, Oleksandr Shulgin <
> oleksandr.shul...@zalando.de> wrote:
>
> On Tue, Sep 11, 2018 at 8:10 PM Oleksandr Shulgin <
>
> On Sep 17, 2018, at 2:34 AM, Oleksandr Shulgin
> wrote:
>
>> On Tue, Sep 11, 2018 at 8:10 PM Oleksandr Shulgin
>> wrote:
>>> On Tue, 11 Sep 2018, 19:26 Jeff Jirsa, wrote:
>>> Repair or read-repair
>>
>>
>> Could you be more specific please?
>>
>> Why any data would be streamed in if
On Tue, Sep 11, 2018 at 8:10 PM Oleksandr Shulgin <
oleksandr.shul...@zalando.de> wrote:
> On Tue, 11 Sep 2018, 19:26 Jeff Jirsa, wrote:
>
>> Repair or read-repair
>>
>
> Could you be more specific please?
>
> Why any data would be streamed in if there is no (as far as I can see)
> possibilities
On Tue, 11 Sep 2018, 19:26 Jeff Jirsa, wrote:
> Repair or read-repair
>
Jeff,
Could you be more specific please?
Why any data would be streamed in if there is no (as far as I can see)
possibilities for the nodes to have inconsistency?
--
Alex
On Tue, Sep 11, 2018 at 12:58 AM Oleksandr
Repair or read-repair
On Tue, Sep 11, 2018 at 12:58 AM Oleksandr Shulgin <
oleksandr.shul...@zalando.de> wrote:
> On Tue, Sep 11, 2018 at 9:47 AM Oleksandr Shulgin <
> oleksandr.shul...@zalando.de> wrote:
>
>> On Tue, Sep 11, 2018 at 9:31 AM Steinmaurer, Thomas <
>>
On Tue, Sep 11, 2018 at 9:47 AM Oleksandr Shulgin <
oleksandr.shul...@zalando.de> wrote:
> On Tue, Sep 11, 2018 at 9:31 AM Steinmaurer, Thomas <
> thomas.steinmau...@dynatrace.com> wrote:
>
>> As far as I remember, in newer Cassandra versions, with STCS, nodetool
>> compact offers a ‘-s’
12 matches
Mail list logo
