Project

General

Profile

Bug #5321

Multiple Hazelcast Client connections to same storage instance

Added by Robert Waltz over 8 years ago. Updated about 6 years ago.

Status:
New
Priority:
Normal
Assignee:
Robert Waltz
Category:
d1_process_daemon
Target version:
Start date:
2014-09-25
Due date:
2014-09-25
% Done:

0%

Milestone:
None
Product Version:
*
Story Points:
Sprint:

Description

D1 Processing appears to attempt to open up multiple hazelcast client connections to the metacat storage hazelcast instance on port 5701

The first client that opens a connection wins the connection to the metacat storage hz instance.

The other hz clients fail, and then continue to attempt to reconnect ad infinatum. Each reconnect attempts at a different port number, increasing the port number incrementally. These attempted reconnects will eat up all available HZ reconnection ports until there are none available.

If the hazelcast client that was successfully connected ever dies and has to reconnect, there will be no ports left that the hazelcast client can use to connect through.

History

#1 Updated by Robert Waltz about 8 years ago

  • Milestone changed from CCI-1.3 to CCI-1.4

#2 Updated by Dave Vieglais about 8 years ago

  • Due date set to 2014-09-25
  • Target version set to Release Backlog
  • Start date set to 2014-09-25

#3 Updated by Robert Waltz about 6 years ago

  • Milestone changed from CCI-1.4 to None

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)