Re: Major compaction ignoring one SSTable? (was Re: Fresh SSTable files (due to repair?) in a static table (was Re: Drop TTLd rows: upgradesstables -a or scrub?))

2018-09-18 Thread Oleksandr Shulgin
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

RE: Major compaction ignoring one SSTable? (was Re: Fresh SSTable files (due to repair?) in a static table (was Re: Drop TTLd rows: upgradesstables -a or scrub?))

2018-09-18 Thread Steinmaurer, Thomas
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:

Major compaction ignoring one SSTable? (was Re: Fresh SSTable files (due to repair?) in a static table (was Re: Drop TTLd rows: upgradesstables -a or scrub?))

2018-09-18 Thread Oleksandr Shulgin
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? >