Eugene Retunsky
Eugene Retunsky

Reputation: 13139

Issue on start-up with Hazelcast (CONCURRENT_MAP_PUT)

I have three nodes on different servers. It works fine, but sometimes on node restart it falls into an infinite cycle like this:

    INFO  03-04 19:51:32,851 (LoggerInstance.java:log:185)  -/10.0.0.107:61000 [dev] ======= -1: CONCURRENT_MAP_PUT ======== 
            thisAddress= Address[10.0.0.107:61000], target= Address[10.0.0.9:61000]
            targetMember= null, targetConn=Connection [/10.0.0.9:39345 -> Address[10.0.0.9:61000]] live=true, client=false, type=MEMBER, targetBlock=Block [129] owner=Address[10.0.0.9:61000] migrationAddress=null
            ProxyKey {name='t:campaignsClicks', key=null} Re-doing [20] times! c:__hz_Proxies : null
    INFO  03-04 19:51:37,862 (LoggerInstance.java:log:185)  -/10.0.0.107:61000 [dev] ======= -1: CONCURRENT_MAP_PUT ======== 
            thisAddress= Address[10.0.0.107:61000], target= Address[10.0.0.9:61000]
            targetMember= null, targetConn=Connection [/10.0.0.9:39345 -> Address[10.0.0.9:61000]] live=true, client=false, type=MEMBER, targetBlock=Block [129] owner=Address[10.0.0.9:61000] migrationAddress=null
            ProxyKey {name='t:campaignsClicks', key=null} Re-doing [30] times! c:__hz_Proxies : null
    INFO  03-04 19:51:42,870 (LoggerInstance.java:log:185)  -/10.0.0.107:61000 [dev] ======= -1: CONCURRENT_MAP_PUT ======== 
            thisAddress= Address[10.0.0.107:61000], target= Address[10.0.0.9:61000]
            targetMember= null, targetConn=Connection [/10.0.0.9:39345 -> Address[10.0.0.9:61000]] live=true, client=false, type=MEMBER, targetBlock=Block [129] owner=Address[10.0.0.9:61000] migrationAddress=null
... and so on infinetely

Restart doesn't help. Only disabling network in hazelcast.xml and restarting all three nodes. Does anybody know what is wrong?

The config file:

<hazelcast>
    <network>
        <port auto-increment="true">60000</port>
        <join>
            <tcp-ip enabled="true">
                <interface>10.0.0.107</interface>
                <hostname>10.0.0.3</hostname>
                <hostname>10.0.0.9</hostname>
            </tcp-ip>
        </join>
    </network>
</hazelcast>

Upvotes: 0

Views: 619

Answers (1)

Eugene Retunsky
Eugene Retunsky

Reputation: 13139

Solved - upgrade to Hazelcast 2.0.0 seemed to solve the problem (it has not been appearing for about 30 days).

Upvotes: 1

Related Questions