Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[discovery] No Warning or Info message given when DiscoveryStrategy SPI not on classpath #10993

Closed
lazerion opened this issue Jul 27, 2017 · 0 comments

Comments

@lazerion
Copy link
Contributor

@lazerion lazerion commented Jul 27, 2017

There was a typo on discovery-strategy config, and it may hard to find w/out proper log message when hazelcast starts.

<discovery-strategies>
                <discovery-strategy class="com.hazelcast.eurekast.one.EurekastOneDiscoveryStrategy" enabled="true">
                </discovery-strategy>
</discovery-strategies>

It should be EurekaOneDiscoveryStrategy

Below you can find log output.

docker@vm2:~$ docker logs 3a5ac5e866c0
########################################
# RUN_JAVA=
# JAVA_OPTS=
# starting now....
########################################
Jul 27, 2017 10:25:40 AM com.hazelcast.config.XmlConfigLocator
INFO: Loading 'hazelcast.xml' from working directory.
Jul 27, 2017 10:25:41 AM com.hazelcast.instance.DefaultAddressPicker
INFO: [LOCAL] [dev] [3.8.2] Prefer IPv4 stack is true.
Jul 27, 2017 10:25:41 AM com.hazelcast.instance.DefaultAddressPicker
INFO: [LOCAL] [dev] [3.8.2] Picked [172.18.0.4]:5701, using socket ServerSocket[addr=/0.0.0.0,localport=5701], bind any local is true
Jul 27, 2017 10:25:41 AM com.hazelcast.system
INFO: [172.18.0.4]:5701 [dev] [3.8.2] Hazelcast 3.8.2 (20170518 - a60f944) starting at [172.18.0.4]:5701
Jul 27, 2017 10:25:41 AM com.hazelcast.system
INFO: [172.18.0.4]:5701 [dev] [3.8.2] Copyright (c) 2008-2016, Hazelcast, Inc. All Rights Reserved.
Jul 27, 2017 10:25:41 AM com.hazelcast.system
INFO: [172.18.0.4]:5701 [dev] [3.8.2] Configured Hazelcast Serialization version : 1
Jul 27, 2017 10:25:42 AM com.hazelcast.spi.impl.operationservice.impl.BackpressureRegulator
INFO: [172.18.0.4]:5701 [dev] [3.8.2] Backpressure is disabled
Jul 27, 2017 10:25:43 AM com.hazelcast.instance.Node
INFO: [172.18.0.4]:5701 [dev] [3.8.2] Activating Discovery SPI Joiner
Jul 27, 2017 10:25:43 AM com.hazelcast.spi.impl.operationexecutor.impl.OperationExecutorImpl
INFO: [172.18.0.4]:5701 [dev] [3.8.2] Starting 2 partition threads
Jul 27, 2017 10:25:43 AM com.hazelcast.spi.impl.operationexecutor.impl.OperationExecutorImpl
INFO: [172.18.0.4]:5701 [dev] [3.8.2] Starting 3 generic threads (1 dedicated for priority tasks)
Jul 27, 2017 10:25:44 AM com.hazelcast.core.LifecycleService
INFO: [172.18.0.4]:5701 [dev] [3.8.2] [172.18.0.4]:5701 is STARTING
Jul 27, 2017 10:25:44 AM com.hazelcast.system
INFO: [172.18.0.4]:5701 [dev] [3.8.2] Cluster version set to 3.8
Jul 27, 2017 10:25:44 AM com.hazelcast.internal.cluster.impl.DiscoveryJoiner
INFO: [172.18.0.4]:5701 [dev] [3.8.2]


Members [1] {
	Member [172.18.0.4]:5701 - 361531c1-c5b8-4df3-9b91-ad1e2b2940b3 this
}

Jul 27, 2017 10:25:44 AM com.hazelcast.core.LifecycleService
INFO: [172.18.0.4]:5701 [dev] [3.8.2] [172.18.0.4]:5701 is STARTED
@jerrinot jerrinot changed the title No Warning or Info message given when DiscoveryStrategy SPI not on classpath [SPI] No Warning or Info message given when DiscoveryStrategy SPI not on classpath Jul 28, 2017
@jerrinot jerrinot added this to the 3.9 milestone Jul 28, 2017
@jerrinot jerrinot self-assigned this Aug 16, 2017
jerrinot added a commit to jerrinot/hazelcast that referenced this issue Aug 16, 2017
@mmedenjak mmedenjak changed the title [SPI] No Warning or Info message given when DiscoveryStrategy SPI not on classpath [discovery] No Warning or Info message given when DiscoveryStrategy SPI not on classpath Aug 21, 2017
jerrinot added a commit to jerrinot/hazelcast that referenced this issue Sep 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

3 participants
You can’t perform that action at this time.