This article is about "Naming GemFireXD members for easier identification in JMX"

Products

• Pivotal GemFire XD

Issue/Introduction

With the defualt setup members get a name including the PID like the following:

GemFire:type=Member,member=localhost(36523)<v0>-18574

Environment

Cause

In this case the JMX object name is: localhost(36523)<v0>-18574

The PID which will obviously change every time the process is restarted which makes it harder to manage the members.

Resolution

Add the -name parameter to the start scripts:

gfxd locator start -peer-discovery-address=localhost -dir=locator -name=myLocator

JMX object name is then: GemFireXD:group=DEFAULT,type=Member,member=myLocator

gfxd server start -locators=localhost[10334] -bind-address=localhost -client-port=1528 -dir=server -name=myServer

JMX object name will then be: GemFireXD:group=DEFAULT,type=Member,member=myServer