Chris Lohfink created CASSANDRA-13683:
-----------------------------------------
Summary: 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
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: [email protected]
For additional commands, e-mail: [email protected]
