Question
Intel
IN
Last activity: 12 Sep 2017 21:41 EDT
Not able to add New node in production
Hi Team,
We have 3 nodes in our production environment and we have to add one more as a backup node. When we are adding the 4th Node we are facing issues:
First of all it is taking backup NIC IP address ( Our physical server has 2 NIC's and Haselcast is taking the backup nic IP instead of physical server.
Secondly, even if the tomcat service successfully running on Node4 after that also it is not appearing in SMA , it's throwing MBean error (com.pega.jmx.ui.util.JMXClientException: No MBeans)
Thirdly, if we enable the service of new node, Node4, then the other production node drive is filling with logs, i have attached the error that is coming and filling the drive logs
Please Assist
Thanks & Regards,
Narhar Dev Sharma
***Updated by moderator: Lochan to add Categories***
Pegasystems Inc.
IN
Hi,
1. Destination of migration could not be found!------ This is just a warning which does not seem to cause the issue. Also I can see hazelcaste exception please correct it if required and do a node by node restart with clear cache of temp folder.
2. For second issue If the auto-discovery is enabled then you have to truncate these table pegadata.pr_sys_statusnodes,
pegadata.pr_sys_queue_ftsindexer;
if auto-discovery is not enabled then add host IP manually in jmx configuration
example:
http://public-ip:9080/prweb/DiagnosticData
service:jmx:rmi:///jndi/rmi:// Proprietary information hidden:9004/jmxrmi
Replace public IP with your instance IP respective JMX port
3.The third issue is due to the exception that is there because of hazelcast exception and it is filling up the logs.
Thank You
Intel
IN
Hi Shubham,
Thanks for your reply, below is my answers to your questions:
1. Yes we do node by node restart only and which temp cache you are talking about? Please share the name, as there are many folders in temp.
2. Yes we add node the way you mentioned like this "service:jmx:rmi:///jndi/rmi:// Proprietary information hidden:9004/jmxrmi"
3. How to resolve that haselcast exception??
Pegasystems Inc.
IN
Hi Narhar,
Clear the entire temp folder and delete the extract marker file.
Also truncate these table pegadata.pr_sys_statusnodes, pegadata.pr_sys_queue_ftsindexer;
For hazelcast exception try disabling firewall and try checking the reachability.
Thank You.
JPMorgan Chase & Company
US
Hi Narhar
Regarding TargetNotMemberException error, the port is blocked by firewall, as telnet < Proprietary information hidden> <port(5701)> fails. Please disable firewall or allow connections to TCP/IP network port.