cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lohfink (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-13683) sstabledump should not use tool initialization
Date Mon, 10 Jul 2017 15:42:00 GMT
Chris Lohfink created CASSANDRA-13683:

             Summary: sstabledump should not use tool initialization
                 Key: CASSANDRA-13683
             Project: Cassandra
          Issue Type: Bug
            Reporter: Chris Lohfink
            Assignee: Chris Lohfink

The tool initialization is not necessary for the sstabledump utility and by using it we possibly
introduce a unnecessary requirement of being on the same C* instance (since we may introduce
changes that require it, UDT changes can lead to dangerous assumptions) that has the schema.
This also does things like introduce possibly devastating issues from having the same commitlog/sstable

A good example is updating the sstable activity table, and having that flushed to commitlogs
as an application outside the running C* service. This may not be on same user (ie root) which
than when a postmemtable flusher after restart attempts to delete it will throw an exception
and potentially kill that thread pool. One that happens commitlogs will cease to get recycled
and will just burn disk space until we run out.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message