You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Alexey Zotov (JIRA)" <ji...@apache.org> on 2012/12/06 14:00:59 UTC
[jira] [Comment Edited] (CASSANDRA-4483) Restarting service
[ https://issues.apache.org/jira/browse/CASSANDRA-4483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511283#comment-13511283 ]
Alexey Zotov edited comment on CASSANDRA-4483 at 12/6/12 12:59 PM:
-------------------------------------------------------------------
CASSANDRA-2967 was resolved as "won't fix". Do you have any thoughts how this issue can be fixed?
There is a bad way how it can be fixed: to add 5 seconds sleep :) I understand that it's an ugly trick, but it should work properly.
was (Author: azotcsit):
CASSANDRA-2967 was resolved as "won't fix". Do you have any thoughts how it can be fixed?
There is a bad way how it can be fixed: to add 5 seconds sleep :) I understand that it's an ugly trick, but it should work properly.
> Restarting service
> ------------------
>
> Key: CASSANDRA-4483
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4483
> Project: Cassandra
> Issue Type: Improvement
> Components: Core, Tools
> Environment: CentOS release 6.2 (Final)
> Reporter: Vladimir Barinov
> Priority: Trivial
> Labels: lhf
>
> Cassandra can't restart too quickly.
> # /etc/init.d/cassandra status
> cassandra (pid 6843) is running...
> # /etc/init.d/cassandra restart
> Shutdown Cassandra: OK
> Starting Cassandra: OK
> # /etc/init.d/cassandra status
> cassandra is stopped
> cassandra log:
> xss = -ea -javaagent:/usr/share/cassandra//lib/jamm-0.2.5.jar -XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms1024M -Xmx1024M -Xmn200M -XX:+HeapDumpOnOutOfMemoryError -Xss128k
> Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 7199; nested exception is:
> java.net.BindException: Address already in use
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira