I found the issue. I was running the nodetool command from another user.
Sorry for the noise.

Thanks.

On Tue, Mar 13, 2018 at 6:45 PM, AI Rumman <rumman...@gmail.com> wrote:

> Hi,
>
> I am trying to upgrade Datastax Cassandra 4.8.14 to 5.0.12, which is
> Cassandra version 2.0.1 to 3.4.0.
>
> The software upgrade operation went fine. But during sstable upgrade, I am
> getting the following error:
>
> nodetool upgradesstables
> error: commitlog directory '/cassandra_dir/commitlog' or, if it does not
> already exist, an existing parent directory of it, is not readable and
> writable for the DSE. Check file system and configuration.
> -- StackTrace --
> org.apache.cassandra.exceptions.ConfigurationException: commitlog
> directory '/cassandra_dir/commitlog' or, if it does not already exist, an
> existing parent directory of it, is not readable and writable for the DSE.
> Check file system and configuration.
>         at org.apache.cassandra.config.DatabaseDescriptor.
> resolveAndCheckDirectory(DatabaseDescriptor.java:801)
>         at org.apache.cassandra.config.DatabaseDescriptor.applyConfig(
> DatabaseDescriptor.java:538)
>         at org.apache.cassandra.config.DatabaseDescriptor.<clinit>(
> DatabaseDescriptor.java:131)
>         at org.apache.cassandra.tools.NodeProbe.checkJobs(NodeProbe.
> java:274)
>         at org.apache.cassandra.tools.NodeProbe.upgradeSSTables(
> NodeProbe.java:328)
>         at org.apache.cassandra.tools.nodetool.UpgradeSSTable.
> execute(UpgradeSSTable.java:54)
>         at org.apache.cassandra.tools.NodeTool$NodeToolCmd.run(
> NodeTool.java:253)
>         at org.apache.cassandra.tools.NodeTool.main(NodeTool.java:167)
>
> Here is my directory structure:
>
> ls -ld /cassandra_dir/*
> drwxr-xr-x  2 cassandra cassandra 4096 Mar 14 01:23
> /cassandra_dir/commitlog
> drwxr-xr-x 11 cassandra cassandra 4096 Mar 14 01:15 /cassandra_dir/data
> drwxr-xr-x  2 cassandra cassandra 4096 Mar 14 01:14 /cassandra_dir/hints
> drwxr-xr-x  2 cassandra cassandra 4096 Mar 14 01:04
> /cassandra_dir/saved_caches
>
> Can anyone please tell me why I am getting the above error?
>
> Thanks.
>
>

Reply via email to