[
https://issues.apache.org/jira/browse/CASSANDRA-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16175718#comment-16175718
]
Chris Lohfink commented on CASSANDRA-7723:
------------------------------------------
sstableloader, sstabledump and sstablemetadata do not have this problem. The
other sstable tools still do. Not running as same user as the C* service is
currently dangerous for most of the offline tools.
> sstable2json (and possibly other command-line tools) hang if no write
> permission to the commitlogs
> --------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-7723
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7723
> Project: Cassandra
> Issue Type: Bug
> Reporter: J.B. Langston
> Priority: Minor
>
> sstable2json (and potentially other command-line tools that call
> DatabaseDescriptor.loadSchemas) will hang if the user running them doesn't
> have write permission on the commit logs. loadSchemas calls
> Schema.updateVersion, which causes a mutation to the system tables, then it
> just spins forever trying to acquire a commit log segment. See this thread
> dump: https://gist.github.com/markcurtis1970/837e770d1cad5200943c. The tools
> should recognize this and present an understandable error message.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
