We started seeing this behavior before we even discovered that it was possible to run manual compactions or cancel compactions by ID.
On Fri, Oct 13, 2017 at 5:58 PM, Jeff Jirsa <jji...@gmail.com> wrote: > Is it possible someone/something is running 'nodetool compact' explicitly? > That would cause the behavior you're seeing. > > > > On Fri, Oct 13, 2017 at 4:24 PM, Bruce Tietjen < > bruce.tiet...@imatsolutions.com> wrote: > >> >> We are new to Cassandra and have built a test cluster and loaded some >> data into the cluster. >> >> We are seeing compaction behavior that seems to violate what we read >> about it's behavior. >> >> Our cluster is configured with JBOD with 3 3.6T disks. Those disks >> currently respectively have the following used/available space: >> Disk Used Available >> sdb1 1.8T 1.7T >> sdc1 1.8T 1.6T >> sdd1 1.5T 2.0T >> >> nodetool compactionstats -H reports that the compaction system is >> attempting to do a compaction that has a total of 6.83T >> >> The system hasn't had that much free space since sometime after we >> started loading data and there has never been that much free space on a >> single disk, so why would it ever attempt such a compaction? >> >> What have we done wrong, or am I reading this wrong? >> >> We have seen the same behavior on most of our 8 nodes. >> >> Can anyone tell us what is happening or what we have done wrong? >> >> Thanks >> > >
