Why brick ports changed after configuring I/O and management encryption in Red Hat Gluster Storage 3.1 ?

Solution Verified - Updated -

Issue

  • Why brick ports changed after configuring I/O and management encryption in Red Hat Gluster Storage 3.1 ?

~snippet from glusterd logs,

var/log/glusterfs/etc-glusterfs-glusterd.vol.log:[2016-01-26 10:43:00.906060] I [MSGID: 106144] [glusterd-pmap.c:274:pmap_registry_remove] 0-pmap: removing brick /bricks/brick_pv01-test/brick_pv01-test-_lv01 on port 49170

~snippet from mount logs,

media-pv01-test.log:[2016-01-26 16:18:41.150149] I [rpc-clnt.c:1851:rpc_clnt_reconfig] 0-pv01-test-client-1: changing port to 49170 (from 0)
media-pv01-test.log:[2016-01-26 16:18:42.176595] I [rpc-clnt.c:1851:rpc_clnt_reconfig] 0-pv01-test-client-0: changing port to 49170 (from 0)
media-pv01-test.log:[2016-01-26 16:18:45.404244] I [rpc-clnt.c:1851:rpc_clnt_reconfig] 0-pv01-test-client-1: changing port to 49170 (from 0)

Environment

  • Red Hat Gluster Storage 3.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content