Question

Hazlecast required for standalone setup

Client requirement is to setup two standalone environment without cluster or domain.We have done ear deployment on JBOSS 6.4.21 with standalone-full.xml.During start-up of application server, observed PegaRules log file that, it’s scanning the network and trying to build cluster.

  1. Clustering technology is mandatory in v7.x?
  2. Do we really required Hazlecast for standalone setup? If not how to disable it.
  • If it’s disable, what are all the implications.
  1. Is Hazlecast is getting triggered by default to create TcpIpJoiner

PegaRuleLog file

2018-11-30 15:00:10,355 [ ServerName01U] [ STANDARD] [ ] [ ] (ic.toggle.ToggleControllerImpl) INFO - Toggle Controller initialization complete

2018-11-30 15:00:11,308 [ ServerName01U] [ STANDARD] [ ] [ ] ( internal.mgmt.PRNodeImpl) INFO - Created provisional node: "ServerName01U ServerName 2018-11-30 06:59:46.506 GMT", []

2018-11-30 15:00:11,324 [ ServerName01U] [ STANDARD] [ ] [ ] ( internal.mgmt.PRNodeImpl) INFO - Starts joining cluster

2018-11-30 15:00:11,574 [ ServerName01U] [ STANDARD] [ ] [ ] (.instance.DefaultAddressPicker) INFO - [LOCAL] [c13c66c1cbf917091298a5bf8a244f73] [3.4.1] Interfaces is disabled, trying to pick one address from TCP-IP config addresses: [xxx.xx.xxx.xx9]

2018-11-30 15:00:11,574 [ ServerName01U] [ STANDARD] [ ] [ ] (.instance.DefaultAddressPicker) INFO - [LOCAL] [c13c66c1cbf917091298a5bf8a244f73] [3.4.1] Prefer IPv4 stack is true.

2018-11-30 15:00:11,605 [ ServerName01U] [ STANDARD] [ ] [ ] (.instance.DefaultAddressPicker) WARN - [LOCAL] [c13c66c1cbf917091298a5bf8a244f73] [3.4.1] Could not find a matching address to start with! Picking one of non-loopback addresses.

2018-11-30 15:00:11,652 [ ServerName01U] [ STANDARD] [ ] [ ] (.instance.DefaultAddressPicker) INFO - [LOCAL] [c13c66c1cbf917091298a5bf8a244f73] [3.4.1] Picked Address[xxx.xx.xxx.xx8]:5701, using socket ServerSocket[addr=/xxx.xx.xxx.xx8,localport=5701], bind any local is false

2018-11-30 15:00:12,058 [ ServerName01U] [ STANDARD] [ ] [ ] (hazelcast.spi.OperationService) INFO - [xxx.xx.xxx.xx8]:5701 [c13c66c1cbf917091298a5bf8a244f73] [3.4.1] Backpressure is disabled

2018-11-30 15:00:12,074 [ ServerName01U] [ STANDARD] [ ] [ ] (i.impl.BasicOperationScheduler) INFO - [xxx.xx.xxx.xx8]:5701 [c13c66c1cbf917091298a5bf8a244f73] [3.4.1] Starting with 4 generic operation threads and 8 partition operation threads.

2018-11-30 15:00:12,199 [ ServerName01U] [ STANDARD] [ ] [ ] ( com.hazelcast.system) INFO - [xxx.xx.xxx.xx8]:5701 [c13c66c1cbf917091298a5bf8a244f73] [3.4.1] Hazelcast 3.4.1 (20150213 - 780828c) starting at Address[xxx.xx.xxx.xx8]:5701

2018-11-30 15:00:12,199 [ ServerName01U] [ STANDARD] [ ] [ ] ( com.hazelcast.system) INFO - [xxx.xx.xxx.xx8]:5701 [c13c66c1cbf917091298a5bf8a244f73] [3.4.1] Copyright (C) 2008-2014 Hazelcast.com

2018-11-30 15:00:12,199 [ ServerName01U] [ STANDARD] [ ] [ ] ( hazelcast.instance.Node) INFO - [xxx.xx.xxx.xx8]:5701 [c13c66c1cbf917091298a5bf8a244f73] [3.4.1] Creating TcpIpJoiner

2018-11-30 15:00:12,199 [ ServerName01U] [ STANDARD] [ ] [ ] (azelcast.core.LifecycleService) INFO - [xxx.xx.xxx.xx8]:5701 [c13c66c1cbf917091298a5bf8a244f73] [3.4.1] Address[xxx.xx.xxx.xx8]:5701 is STARTING

2018-11-30 15:00:12,339 [4f73.cached.thread-1] [ STANDARD] [ ] [ ] ( nio.tcp.SocketConnector) INFO - [xxx.xx.xxx.xx8]:5701 [c13c66c1cbf917091298a5bf8a244f73] [3.4.1] Connecting to /xxx.xx.xxx.xx9:5701, timeout: 0, bind-any: false

2018-11-30 15:00:12,371 [4f73.cached.thread-1] [ STANDARD] [ ] [ ] (nio.tcp.TcpIpConnectionManager) INFO - [xxx.xx.xxx.xx8]:5701 [c13c66c1cbf917091298a5bf8a244f73] [3.4.1] Established socket connection between /xxx.xx.xxx.xx8:63973 and ServerName02U/xxx.xx.xxx.xx9:5701

2018-11-30 15:00:18,402 [c-operation.thread-3] [ STANDARD] [ ] [ ] (zelcast.cluster.ClusterService) INFO - [xxx.xx.xxx.xx8]:5701 [c13c66c1cbf917091298a5bf8a244f73] [3.4.1]

***Edited by Moderator Marissa to update SR Details***

Group Tags

Comments

Keep up to date on this post and subscribe to comments

December 19, 2018 - 12:51am

Why Hazlecast required for standalone setup?

  1. Clustering technology is mandatory in v7.x?
  2. Do we really required Hazlecast for standalone setup? If not how to disable it.
  • If it’s disable, what are all the implications.

Pega
December 27, 2018 - 12:14pm
  1. Clustering technology is mandatory in v7.x?

>>> Yes. Pega internally uses it for cache synchronization, remote calls, user presence etc. The use of hazelcast varies and is growing in newer versions.

  1. Do we really required Hazlecast for standalone setup? If not how to disable it.

>>> We don't want customers to end up with customizations unless absolutely required. Don't disable it.

  • If it’s disable, what are all the implications. - NA
  1. Is Hazlecast is getting triggered by default to create TcpIpJoiner

Correct!