It's fine and intended behaviour. Upgradesstables also has the same effect. Basically cleanup operates on all SSTables on a node (for each table) and will cancel any in-progress compactions and instead run cleanup across them, as you can't have two different compactions including the same file. The compactions will be retriggered if necessary after cleanup has completed.
On 22 January 2018 at 13:05, Steinmaurer, Thomas < thomas.steinmau...@dynatrace.com> wrote: > Hello, > > > > when triggering a „nodetool cleanup“ with Cassandra 3.11, the nodetool > call almost returns instantly and I see the following INFO log. > > > > INFO [CompactionExecutor:54] 2018-01-22 12:59:53,903 > CompactionManager.java:1777 - Compaction interrupted: > Compaction@fc9b0073-1008-3a07-aeb9-baf6f3cd0b1c(ruxitdb, Ts2Final05Min, > 98624438/107305082)bytes > > INFO [CompactionExecutor:69] 2018-01-22 12:59:54,135 > CompactionManager.java:1777 - Compaction interrupted: > Compaction@ea0742f8-f3be-365d-a689-26ab346fdfb0(ruxitdb, Ts2Final01Min, > 49238516/72948781)bytes > > > > > > No error etc. Does the “compaction interrupted” sound ok? > > > > Thanks, > > Thomas > > > The contents of this e-mail are intended for the named addressee only. It > contains information that may be confidential. Unless you are the named > addressee or an authorized designee, you may not copy or use it, or > disclose it to anyone else. If you received it in error please notify us > immediately and then destroy it. Dynatrace Austria GmbH (registration > number FN 91482h) is a company registered in Linz whose registered office > is at 4040 Linz, Austria, Freist > <https://maps.google.com/?q=4040+Linz,+Austria,+Freist%C3%A4dterstra%C3%9Fe+313&entry=gmail&source=g> > ädterstra > <https://maps.google.com/?q=4040+Linz,+Austria,+Freist%C3%A4dterstra%C3%9Fe+313&entry=gmail&source=g> > ße 313 > <https://maps.google.com/?q=4040+Linz,+Austria,+Freist%C3%A4dterstra%C3%9Fe+313&entry=gmail&source=g> >
