cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lohfink (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7723) sstable2json (and possibly other command-line tools) hang if no write permission to the commitlogs
Date Tue, 28 Oct 2014 12:59:33 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14186778#comment-14186778
] 

Chris Lohfink commented on CASSANDRA-7723:
------------------------------------------

A solution that some people have tried is to use sudo while calling it, which would work but
may cause problems later.  sstable2json would then build any missing components with the root
user that creates a ton of permission problems down the road.

> 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
>            Assignee: Joshua McKenzie
>            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.3.4#6332)

Mime
View raw message