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

 Munisekhar Katta (MunisekharK17224664)
First Citizens Bank

First Citizens Bank
US
MunisekharK17224664 Member since 2024 14 posts
First Citizens Bank
Posted: Mar 4, 2018
Last activity: Mar 21, 2018
Posted: 4 Mar 2018 22:37 EST
Last activity: 21 Mar 2018 18:04 EDT
Closed
Solved

New Server added to the existing environment

We have added 2 new servers to the existing environment.One server is up and running fine and we were able to access the application without any issues.

The other server is generating error's in stdout logs and Pega logs but we were able to access the application on this node as well,besides this the log file size is growing high.I observed when I restarted the 2nd new server the old server log file is also growing and lot of log files (PegaHAZELCAST-xxxx-xxx-xx.log.2)are being created.when I look at the Pega logs I was able to see the below error's repeatedly. Could anyone please suggest an approach to resolve the issue?

Show More

We have added 2 new servers to the existing environment.One server is up and running fine and we were able to access the application without any issues.

The other server is generating error's in stdout logs and Pega logs but we were able to access the application on this node as well,besides this the log file size is growing high.I observed when I restarted the 2nd new server the old server log file is also growing and lot of log files (PegaHAZELCAST-xxxx-xxx-xx.log.2)are being created.when I look at the Pega logs I was able to see the below error's repeatedly. Could anyone please suggest an approach to resolve the issue?

2018-xx-xx 20:53:26,294 [c-operation.thread-1] [ STANDARD] [ ] [ ] (ition.InternalPartitionService) WARN - [172.xx.xx.xxx]:5701 [226593ec118b69xxxxxxxxxxxxxx] [3.4.1] Following unknown addresses are found in partition table sent from master[Address[172.xx.xx.xxx]:5701]. (Probably they have recently joined or left the cluster.) {
Address[172.xx.xx.xxx]:5702
Address[172.xx.xx.xxx]:5701
}
2018-03-04 20:53:26,310 [c-operation.thread-0] [ STANDARD] [ ] [ ] (ition.InternalPartitionService) WARN - [172.xx.xx.xxx]:5701 [226593xxxxxxxxxxxxxxxxxxx] [3.4.1] Following unknown addresses are found in partition table sent from master[Address[172.xx.xx.xxx]:5701]. (Probably they have recently joined or left the cluster.) {
Address[172.xx.xx.xxx]:5702
Address[172.xx.xx.xxx]:5701

Show Less
To see attachments, please log in.
System Administration

Accepted Solution

Posted: 6 years ago
Posted: 5 Mar 2018 1:06 EST
vamsi krishna (vamsik6185)
ANZ Asia Pacific Division

ANZ Asia Pacific Division
IN

Hi Muni, 

Can you pelase check below articles

https://community.pega.com/support/support-articles/pega718-hazelcast-preventing-startup

And also check in alerts log file there is PEGA0092 and PEGA0088 , if there please check below articles 

https://pdn.pega.com/pega0092-number-servers-cluster-falls-below-recommended-settings

https://pdn.pega.com/pega0088-client-node-unexpectedly-disconnected-cluster

 

 

 

To see attachments, please log in.
Posted: 6 years ago
Posted: 5 Mar 2018 0:38 EST
Ujjwal Kumar Shukla (UjjwalShukla_GCS)
PEGA
Senior Manager, Technical Support
Pegasystems Inc.
IN

Hi There,

Could you please check if pr_sys_statusnodes table has all the node added.
Follow below steps:-
Stop the servers
Truncate pr_sys_statusnodes
And start of all the servers one by one should fix this log message.

Thanks,
Ujjwal
Ujjwal

To see attachments, please log in.

Accepted Solution

Posted: 6 years ago
Posted: 5 Mar 2018 1:06 EST
vamsi krishna (vamsik6185)
ANZ Asia Pacific Division

ANZ Asia Pacific Division
IN

Hi Muni, 

Can you pelase check below articles

https://community.pega.com/support/support-articles/pega718-hazelcast-preventing-startup

And also check in alerts log file there is PEGA0092 and PEGA0088 , if there please check below articles 

https://pdn.pega.com/pega0092-number-servers-cluster-falls-below-recommended-settings

https://pdn.pega.com/pega0088-client-node-unexpectedly-disconnected-cluster

 

 

 

To see attachments, please log in.
Posted: 6 years ago
Posted: 6 Mar 2018 0:07 EST
Munisekhar Katta (MunisekharK17224664)
First Citizens Bank

First Citizens Bank
US

Vamsi,

I added some lines in Prconfig.xml according to the above article and it has fixed the log issues but I am not able to see the newly added nodes under cluster management tab in designer studio and it has only showing existing nodes.

 

 

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