[ https://issues.apache.org/jira/browse/GEODE-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Barbara Pruijn resolved GEODE-1786. ----------------------------------- Resolution: Works for Me Works in 1.4.0. This was probably fixed at some point. > 'describe member' does not show all available Cache Servers when Geode Server > has more than 1 Cache Server defined. > ------------------------------------------------------------------------------------------------------------------- > > Key: GEODE-1786 > URL: https://issues.apache.org/jira/browse/GEODE-1786 > Project: Geode > Issue Type: Bug > Components: gfsh, management > Reporter: John Blum > Priority: Major > Labels: CacheServer, CacheServerInformation, > DescribeMemberCommand, Gfsh, describe_member > > When my Geode Server (data node) has more than 1 {{CacheServer}} defined, > _Gfsh's_ '{{describe member}}' command does not show all the available cache > servers for that member. It only shows the **last** {{CacheServer}} added. > // Geode Server log file output... > {code:java} > [info 2016/08/15 12:03:34.971 PDT <main> tid=0x1] CacheServer Configuration: > port=11235 max-connections=800 max-threads=0 notify-by-subscription=true > socket-buffer-size=32768 maximum-time-between-pings=60000 > maximum-message-count=230000 message-time-to-live=180 eviction-policy=none > capacity=1 overflow directory=. groups=[] loadProbe=ConnectionCountProbe > loadPollInterval=5000 tcpNoDelay=true > [info 2016/08/15 12:03:34.979 PDT <main> tid=0x1] Cache server connection > listener bound to address 0.0.0.0/0.0.0.0:12480 with backlog 1,000. > [info 2016/08/15 12:03:34.980 PDT <main> tid=0x1] CacheServer Configuration: > port=12480 max-connections=800 max-threads=0 notify-by-subscription=true > socket-buffer-size=32768 maximum-time-between-pings=60000 > maximum-message-count=230000 message-time-to-live=180 eviction-policy=none > capacity=1 overflow directory=. groups=[] loadProbe=ConnectionCountProbe > loadPollInterval=5000 tcpNoDelay=true > [info 2016/08/15 12:03:34.981 PDT <main> tid=0x1] Cache server connection > listener bound to address 0.0.0.0/0.0.0.0:42424 with backlog 1,000. > [info 2016/08/15 12:03:34.983 PDT <main> tid=0x1] CacheServer Configuration: > port=42424 max-connections=800 max-threads=0 notify-by-subscription=true > socket-buffer-size=32768 maximum-time-between-pings=60000 > maximum-message-count=230000 message-time-to-live=180 eviction-policy=none > capacity=1 overflow directory=. groups=[] loadProbe=ConnectionCountProbe > loadPollInterval=5000 tcpNoDelay=true > [info 2016/08/15 12:03:34.983 PDT <main> tid=0x1] Cache server connection > listener bound to address 0.0.0.0/0.0.0.0:48484 with backlog 1,000. > [info 2016/08/15 12:03:34.985 PDT <main> tid=0x1] CacheServer Configuration: > port=48484 max-connections=800 max-threads=0 notify-by-subscription=true > socket-buffer-size=32768 maximum-time-between-pings=60000 > maximum-message-count=230000 message-time-to-live=180 eviction-policy=none > capacity=1 overflow directory=. groups=[] loadProbe=ConnectionCountProbe > loadPollInterval=5000 tcpNoDelay=true > {code} > _Gfsh_ output for '{{describe member}}' > {code:java} > gfsh>list members > Name | Id > -------------------------- | > ---------------------------------------------------------- > DataGeodeServerApplication | > 10.99.199.9(DataGeodeServerApplication:45269)<ec><v0>:1024 > gfsh> > gfsh>describe member --name=DataGeodeServerApplication > Name : DataGeodeServerApplication > Id : 10.99.199.9(DataGeodeServerApplication:45269)<ec><v0>:1024 > Host : 10.99.199.9 > Regions : Echo > PID : 45269 > Groups : > Used Heap : 47M > Max Heap : 3641M > Working Dir : > /Users/jblum/pivdev/springonePlatform-2016/configuration-example/target > Log file : > /Users/jblum/pivdev/springonePlatform-2016/configuration-example/target > Locators : localhost[10334] > Cache Server Information > Server Bind : > Server Port : 48484 > Running : true > Client Connections : 0 > {code} > It seems _Gfsh_ assumes there is only 1 {{CacheServer}} when in fact a Geode > Server may have defined/added multiple {{CacheServer}} endpoints, in which > case, it would be helpful to the user if all endpoints were shown in > '{{describe member}}' since the would all have different ports, possible bind > addresses and perhaps varying number of client connections at any given point > in time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)