[
https://issues.apache.org/jira/browse/CASSANDRA-16104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17210330#comment-17210330
]
Dmitrii Saprykin edited comment on CASSANDRA-16104 at 10/8/20, 4:56 PM:
------------------------------------------------------------------------
After some digging I found a source for this warning:
* src/java/org/apache/cassandra/tools/NodeProbe.java method *upgradeSSTables*
calls *checkJobs* to validate *--jobs* parameter ;
* which calls *DatabaseDescriptor.toolInitialization(false)* ;
* *DatabaseDescriptor* calls *applySimpleConfig* which validates
*data_files_directories* and produces warning ;
So data directory space gets checked in the wrong location (if CASSANDRA_CONF
env is not default) and on the wrong host (it is checked on nodetool
upgradesstables request source).
Moreover I do not think checkJobs has any sense at all as it validates *--jobs*
against local configuration which has nothing to do with
*concurrent_compactors* value for host which actually executes upgrade sstables
operation.
was (Author: saprykin):
After some digging I found a source for this warning:
* src/java/org/apache/cassandra/tools/NodeProbe.java method *upgradeSSTables*
calls *checkJobs* to validate *--jobs* parameter ;
* which calls *DatabaseDescriptor.toolInitialization(false)* ;
* *DatabaseDescriptor* calls *applySimpleConfig* which validates
*data_files_directories* and produces warning ;
So data directory space gets checked in the wrong location (if CASSANDRA_CONF
env is not default) and on the wrong host (it is checked on nodetool
upgradesstables request source).
> Wrong warning about data volumes capacity
> -----------------------------------------
>
> Key: CASSANDRA-16104
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16104
> Project: Cassandra
> Issue Type: Bug
> Reporter: Dmitrii Saprykin
> Priority: Normal
>
> I see the following warning trying to run *nodetool upgradesstables*
> {noformat}
> WARN 16:09:24 Only 34988 MB free across all data volumes. Consider adding
> more capacity to your cluster or removing obsolete snapshots
> {noformat}
> This warning is wrong because the wrong storage device capacity gets tested.
> All my cassandra data paths are subdirectories of */data* mount point which
> has enough of space:
> {noformat}
> $ df -h /data
> Filesystem Size Used Avail Mounted on
> ................. 1.2T 200G 1T /data
> {noformat}
> However what Warning reports is a OS mount which has nothing to do with
> Cassandra configuration:
> {noformat}
> df -h /
> Filesystem Size Used Avail Use% Mounted on
> ............ 40G 5.7G 35G 15% /
> {noformat}
> I see this error running Cassandra 3.0.22
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
