Disable auto-detection in tests that start Hazelcast
See original GitHub issueProgrammatically, it’s something like:
getAutoDetectionConfig().setEnabled(false)
In YAML:
hazelcast:
network:
join:
auto-detection:
enabled: false
And in XML:
<hazelcast>
...
<network>
<join>
<auto-detection enabled="false" />
...
</join>
</network>
...
</hazelcast>
When configured correctly, the node should log the following:
WARNING: [192.168.178.45]:5701 [dev] [4.2.5] No join method is enabled! Starting standalone.
We don’t want to see this:
INFO: [192.168.178.45]:5701 [dev] [4.2.5] Using Multicast discovery
Issue Analytics
- State:
- Created a year ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Discovering Members by Auto Detection
Discovering Members by Auto Detection ... Auto Detection is a good way to start playing with Hazelcast. It tries to automatically detect the...
Read more >Hazelcast: How to disable auto-discovery during tests?
To build the project I use mvn clean package command. In this maven build process, tests are run and Spring context wakes up....
Read more >Faster startup of hazelcast in tests - RManniBucau
The trick to reduce hazelcast startup time is to use an "embedded discovery ... is to disable port auto-increment and disable autodetection, ...
Read more >[Longish] New to hazelcast: Questions about discovery and ...
By default, Hazelcast tries to automatically detect the applicable discovery mechanism based on the runtime environment.
Read more >AutoDetectionConfig (Hazelcast Root 4.1 API)
For example, it will automatically use the hazelcast-aws plugin if run on an AWS instance. ... Enables or disables the auto detection join...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@adrianbob sure, the issue is yours.
https://github.com/spring-projects/spring-boot/commit/a4bafa88bc167eaff7e0cbf7bfe36da742db2b15 should hopefully fix the build