[
https://issues.apache.org/jira/browse/CASSANDRA-8024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler resolved CASSANDRA-8024.
---------------------------------------
Resolution: Not a Problem
It appears that you are starting manually with {{./bin/cassandra}} which sends
a small amount of stdout and detaches, logging normally. You can foreground
your startup, if you wish: {{./bin/cassandra -f}}
> No boot finished or ready message anymore upon startup completion to CLI
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-8024
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8024
> Project: Cassandra
> Issue Type: Bug
> Environment: Cassandra 2.0.10
> Reporter: Karl Mueller
> Priority: Trivial
>
> This is trivial, but cassandra logs the following to its log:
> ...
> INFO [main] 2014-09-29 23:10:35,793 CassandraDaemon.java (line 575) No
> gossip backlog; proceeding
> INFO [main] 2014-09-29 23:10:35,979 Server.java (line 156) Starting
> listening for CQL clients on
> kaos-cass00.sv.walmartlabs.com/10.93.12.10:9042...
> INFO [main] 2014-09-29 23:10:36,048 ThriftServer.java (line 99) Using
> TFramedTransport with a max frame size of 15728640 bytes.
> However, on the command line I only see:
> INFO 23:10:30,005 Compacted 4 sstables to
> [/data2/data-cassandra/system/compactions_in_progress/system-compactions_in_progress-jb-67,].
> 1,333 bytes to 962 (~72% of original) in 32ms = 0.028670MB/s. 15 total
> partitions merged to 12. Partition merge counts were {1:11, 2:2, }
> INFO 23:10:35,793 No gossip backlog; proceeding
> I would be nice if the "Starting listening for.." or some other "startup
> complete" message went to the command line STDOUT. There used to be one, I
> think, but there isn't anymore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
