[
https://issues.apache.org/jira/browse/CASSANDRA-13678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703376#comment-17703376
]
Stefan Miklosovic commented on CASSANDRA-13678:
-----------------------------------------------
maybe related to CASSANDRA-17773
> Misconfiguration in cassandra-env.sh does not report any errors.
> ----------------------------------------------------------------
>
> Key: CASSANDRA-13678
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13678
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Config
> Environment: Cassandra 3.11 at Ubuntu 15.04.
> Reporter: Lucas Benevides Dias
> Priority: Low
> Labels: error-feedback, usability
> Attachments: cassandra-env.sh
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Once I have misconfigured the file /etc/cassandra/cassandra-env.sh. I changed
> the MAX_HEAP_SIZE="1500M" and did not change the HEAP_NEWSIZE="350M", letting
> it commented. Now I know that if you change one, you MUST change the other,
> but even knowing that it is written in the file in comments, I think some
> error message should appear to the user.
> When it occured to me, I looked in the files /var/log/cassandra/system.log
> and debug.log and there wasn't any line telling about the error. The command
> {{ #service cassandra start }} is just responseless.
> There should be some warning in the logs and maybe in the stdout, warning
> that the interpretation of the cassandra-env.sh parameters was wrong.
> I attached the file in which the error happens.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
