HZ_CLUSTERNAME, incompatible Hazelcast version

Description

When mod-remote-storage-1.7.1 (=Nolana) runs with default Hazelcast configuration and mod-remote-storage-2.0.2 (= Orchid) is started with default Hazelcast configuration that latter stops with this error:

How to reproduce:
In first shell run

Wait 10 seconds.

In second shell run

mod-remote-storage-1.7.1 (= Nolana) runs Hazelcast 5.1.4.

mod-remote-storage-2.0.2 (= Orchid) runs Hazelcast 5.2.1.

They use incompatible minor versions of Hazelcast (5.1 and 5.2).

This can be fixed by setting distinct clusternames. The default clustername is dev.

Example:

Example for the reproducer posted above:

Task:

Explain this requirement in the Orchid release notes. Done.

Explain this requirement in the README.

Other considerations:

The method in
https://github.com/folio-org/mod-erm-usage-harvester/blob/v4.3.0/mod-erm-usage-harvester-bundle/src/main/resources/hazelcast.xml#L34
avoids manual Hazelcast configuration.

Additional information:

VZG internal issue: https://jira.gbv.de/browse/FOLIO-343

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Details

Assignee

Reporter

Priority

Development Team

Volaris

Affected Institution

GBV

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created June 9, 2023 at 10:26 AM
Updated June 9, 2023 at 10:54 AM
TestRail: Cases
TestRail: Runs