[
https://issues.apache.org/jira/browse/CASSANDRA-15154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861732#comment-16861732
]
Michael Shuler commented on CASSANDRA-15154:
--------------------------------------------
Close - not a bug?
Generally, one or two lines before the ones you listed is the line you're
looking for. The "listening for CQL clients" line is the equivalent of "I've
started and I'm ready for connections":
{noformat}
INFO [main] 2019-06-11 22:42:46,373 Server.java:156 - Starting listening for
CQL clients on localhost/127.0.0.1:9042 (unencrypted)...
{noformat}
Longer sample on fresh start including lines you listed:
{noformat}
...
INFO [MigrationStage:1] 2019-06-11 22:42:45,977 ColumnFamilyStore.java:430 -
Initializing system_auth.resource_role_permissons_index
INFO [MigrationStage:1] 2019-06-11 22:42:45,984 ColumnFamilyStore.java:430 -
Initializing system_auth.role_members
INFO [MigrationStage:1] 2019-06-11 22:42:45,993 ColumnFamilyStore.java:430 -
Initializing system_auth.role_permissions
INFO [MigrationStage:1] 2019-06-11 22:42:46,000 ColumnFamilyStore.java:430 -
Initializing system_auth.roles
INFO [main] 2019-06-11 22:42:46,297 NativeTransportService.java:70 - Netty
using native Epoll event loop
INFO [main] 2019-06-11 22:42:46,373 Server.java:155 - Using Netty Version:
[netty-buffer=netty-buffer-4.0.44.Final.452812a, netty-codec=net
ty-codec-4.0.44.Final.452812a,
netty-codec-haproxy=netty-codec-haproxy-4.0.44.Final.452812a,
netty-codec-http=netty-codec-http-4.0.44.Final.
452812a, netty-codec-socks=netty-codec-socks-4.0.44.Final.452812a,
netty-common=netty-common-4.0.44.Final.452812a, netty-handler=netty-handl
er-4.0.44.Final.452812a, netty-tcnative=netty-tcnative-1.1.33.Fork26.142ecbb,
netty-transport=netty-transport-4.0.44.Final.452812a, netty-tr
ansport-native-epoll=netty-transport-native-epoll-4.0.44.Final.452812a,
netty-transport-rxtx=netty-transport-rxtx-4.0.44.Final.452812a, nett
y-transport-sctp=netty-transport-sctp-4.0.44.Final.452812a,
netty-transport-udt=netty-transport-udt-4.0.44.Final.452812a]
INFO [main] 2019-06-11 22:42:46,373 Server.java:156 - Starting listening for
CQL clients on localhost/127.0.0.1:9042 (unencrypted)...
INFO [main] 2019-06-11 22:42:46,429 CassandraDaemon.java:556 - Not starting
RPC server as requested. Use JMX (StorageService->startRPCServe
r()) or nodetool (enablethrift) to start it
INFO [OptionalTasks:1] 2019-06-11 22:42:56,162 CassandraRoleManager.java:356 -
Created default superuser role 'cassandra'
...
{noformat}
> Add console log to indicate the node is ready to accept requests
> ----------------------------------------------------------------
>
> Key: CASSANDRA-15154
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15154
> Project: Cassandra
> Issue Type: Improvement
> Components: Cluster/Membership, Local/Startup and Shutdown,
> Observability/Logging
> Reporter: Abhijit Sarkar
> Priority: Normal
>
> Depending on whether a cluster is initialized the first time, or a node is
> restarted, the last message on the console varies. In either case, there's no
> indication that the cluster/node is ready to accept requests.
> For example, when I create a new Cassandra Docker container locally:
> {code}
> $ docker run --name cas -p 9042:9042 -p 9091:9091 -e CASSANDRA_DC=dev
> cassandra
> ...
> INFO [OptionalTasks:1] 2019-06-11 23:31:35,527 CassandraRoleManager.java:356
> - Created default superuser role 'cassandra'
> {code}
> After shutting it down (CTRL + C), and restarting:
> {code}
> $ docker start cas
> ...
> INFO [main] 2019-06-11 23:32:57,980 CassandraDaemon.java:556 - Not starting
> RPC server as requested. Use JMX (StorageService->startRPCServer()) or
> nodetool (enablethrift) to start it
> {code}
> In either of the above cases, how is a regular user, whose full time job is
> not working with Cassandra, expected to know whether the server is ready? We
> have a new member in the team who previously was an iOS developer. He left
> the server running overnight, assuming the node hadn't finished
> initialization; the next morning, the last message was still "Created default
> superuser role 'cassandra'".
> Please add a simple log statement with basic information like node IPs in the
> cluster indicating the node is ready. For example, this is what Spring Boot
> does:
> {code}
> 2019-06-11 16:37:28.295 INFO [my-app,,,] 17392 --- [ main]
> o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 11900
> (http) with context path ''
> 2019-06-11 16:37:28.299 INFO [my-app,,,] 17392 --- [ main]
> mypackage.MyApp : Started MyApp in 5.279 seconds (JVM running for 5.916)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
