Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Radhakrishna Gongala (RadhakrishnaG1339)
JPMorgan Chase & Company

JPMorgan Chase & Company
IN
RadhakrishnaG1339 Member since 2017 2 posts
JPMorgan Chase & Company
Posted: Jul 7, 2022
Last activity: Jul 8, 2022
Posted: 7 Jul 2022 4:06 EDT
Last activity: 8 Jul 2022 2:46 EDT
Closed

Hazelcast cluster sockettimeoutexception

Hi team,

We are usign Pega 8.6.1 with Hazelcast 4.1.1.

While trying to bring up more webuser or background pods then they are not connecting to the existing master.

getting Socket timeout exception as mentioned below:

2022-07-07 03:29:12,576 [ates.cached.thread-3] [                    ] [                    ] ( server.tcp.TcpServerConnector) INFO     - [ Proprietary information hidden]:5701 [a777ff8b0dc21625f37f6239916fc65f] [4.1.1] Connecting to / Proprietary information hidden:5701, timeout: 10000, bind-any: true

2022-07-07 03:29:22,584 [ates.cached.thread-3] [                    ] [                    ] ( server.tcp.TcpServerConnector) INFO     - [ Proprietary information hidden]:5701 [a777ff8b0dc21625f37f6239916fc65f] [4.1.1] Could not connect to: / Proprietary information hidden:5701. Reason: SocketTimeoutException[null]

Show More

Hi team,

We are usign Pega 8.6.1 with Hazelcast 4.1.1.

While trying to bring up more webuser or background pods then they are not connecting to the existing master.

getting Socket timeout exception as mentioned below:

2022-07-07 03:29:12,576 [ates.cached.thread-3] [                    ] [                    ] ( server.tcp.TcpServerConnector) INFO     - [ Proprietary information hidden]:5701 [a777ff8b0dc21625f37f6239916fc65f] [4.1.1] Connecting to / Proprietary information hidden:5701, timeout: 10000, bind-any: true

2022-07-07 03:29:22,584 [ates.cached.thread-3] [                    ] [                    ] ( server.tcp.TcpServerConnector) INFO     - [ Proprietary information hidden]:5701 [a777ff8b0dc21625f37f6239916fc65f] [4.1.1] Could not connect to: / Proprietary information hidden:5701. Reason: SocketTimeoutException[null]

2022-07-07 03:29:22,584 [ates.cached.thread-3] [                    ] [                    ] (      cluster.impl.TcpIpJoiner) INFO     - [ Proprietary information hidden]:5701 [a777ff8b0dc21625f37f6239916fc65f] [4.1.1] [ Proprietary information hidden]:5701 is added to the blacklist.

2022-07-07 03:29:12,576 [ates.cached.thread-3] [                    ] [                    ] ( server.tcp.TcpServerConnector) INFO     - [ Proprietary information hidden]:5701 [a777ff8b0dc21625f37f6239916fc65f] [4.1.1] Connecting to / Proprietary information hidden:5701, timeout: 10000, bind-any: true

2022-07-07 03:29:22,584 [ates.cached.thread-3] [                    ] [                    ] ( server.tcp.TcpServerConnector) INFO     - [ Proprietary information hidden]:5701 [a777ff8b0dc21625f37f6239916fc65f] [4.1.1] Could not connect to: / Proprietary information hidden:5701. Reason: SocketTimeoutException[null]

2022-07-07 03:29:22,584 [ates.cached.thread-3] [                    ] [                    ] (      cluster.impl.TcpIpJoiner) INFO     - [ Proprietary information hidden]:5701 [a777ff8b0dc21625f37f6239916fc65f] [4.1.1] [ Proprietary information hidden]:5701 is added to the blacklist.

 

Show Less
***Edited by Moderator: Pooja Gadige to add capability tag***
To see attachments, please log in.
Pega Platform 8.6.1
Client-managed Cloud
System Administration

  • VenkataRojaratnam Kothuri
Posted: 2 years ago
Updated: 2 years ago
Posted: 7 Jul 2022 11:08 EDT
Updated: 7 Jul 2022 22:40 EDT
Sriharsha Anika (Sriharsha A)
JPMorgan Chase
Sriharsha Anika
JPMorgan Chase
IN

@RadhakrishnaG1339

Embedded Hazelcast deployments have cluster stability issues, especially when the number of nodes are high Embedded deployment is not a recommended by Hazelcast  

Starting 8.6 recommendation to clients is to follow a new architecture with respect to hazelcast

HZ server deployed as a single tenant backing service for each Infinity environment in the same k8s namespace. 

Reduced interdependency between the  Client ( Infinity) and the server ( Hazelcast cluster). Client and server can upgrade independently.  

Refer to below docs and deploying 

https://docs.pega.com/configuring-client-server-mode-hazelcast-pega-platform 

https://docs.pega.com/deploying-hazelcast-management-center 

https://github.com/pegasystems/pega-helm-charts/tree/master/charts/pega/charts/hazelcast 

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice