[
https://issues.apache.org/jira/browse/CASSANDRA-13678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lucas Benevides Dias updated CASSANDRA-13678:
---------------------------------------------
Attachment: cassandra-env.sh
Environment: Cassandra 3.10 at Ubuntu 15.04.
Reproduced In: 3.10
Labels: error-feedback usability (was: )
Priority: Trivial (was: Major)
Description:
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.
Component/s: Configuration
Issue Type: Wish (was: Bug)
> 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: Wish
> Components: Configuration
> Environment: Cassandra 3.10 at Ubuntu 15.04.
> Reporter: Lucas Benevides Dias
> Priority: Trivial
> Labels: error-feedback, usability
> Attachments: cassandra-env.sh
>
>
> 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.
--
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
