[jira] [Updated] (CASSANDRA-13683) sstabledump should not use tool initialization

["Jeff Jirsa (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-13683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Jirsa updated CASSANDRA-13683:
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 4.0
           Status: Resolved  (was: Ready to Commit)

Thanks to both of you. Committed as {{9e3483f844d9db6fe2a6210550622fc2cd8aef72}}


> sstabledump should not use tool initialization
> ----------------------------------------------
>
>                 Key: CASSANDRA-13683
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13683
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Chris Lohfink
>            Assignee: Chris Lohfink
>             Fix For: 4.0
>
>
> 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 locations.
> 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
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org