tkhurana opened a new pull request, #2595: URL: https://github.com/apache/phoenix/pull/2595
The same physical RegionServer can be observed under two ServerName spellings that differ only in host -- a declared FQDN (from hbase.unsafe.regionserver.hostname) versus the pod IP the master hands back at reportForDuty when reverse-DNS is enabled. Different coprocessor environments surface different spellings for the same server (prewarm PhoenixRegionServerEndpoint vs write-path IndexRegionObserver), so keying INSTANCES on serverName.getServerName() split one logical group into two independent instances, each with its own Disruptor and sequence counter. Key on (port, startcode) instead, which excludes the host: two distinct live RegionServers can never share a port on the same host at the same time, so mini-cluster ITs running several RS in one JVM stay distinct (each binds its own ephemeral port), while the single-RS case collapses the FQDN/IP spellings to one entry. closeAllForServer() matches on the same canonical identity. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
