[
https://issues.apache.org/jira/browse/SENTRY-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsee Yarlagadda updated SENTRY-1635:
--------------------------------------
Attachment: SENTRY-1635.02-sentry-ha-redesign.patch
Thanks Sasha for pointing out that the old patch only handles the new
connections. But for the ones that became a follower after the leader, they
will continue to hold dangling connections.
The new patch will clear out the connection if the server has become a follower.
> Limit HMS connections only to the leader of the sentry servers
> ---------------------------------------------------------------
>
> Key: SENTRY-1635
> URL: https://issues.apache.org/jira/browse/SENTRY-1635
> Project: Sentry
> Issue Type: Sub-task
> Components: Hdfs Plugin
> Affects Versions: sentry-ha-redesign
> Reporter: Vamsee Yarlagadda
> Assignee: Vamsee Yarlagadda
> Priority: Minor
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1635.01-sentry-ha-redesign.patch,
> SENTRY-1635.02-sentry-ha-redesign.patch
>
>
> Looking at the code of HMSFollower, we seem to be establishing HMS connection
> for all servers of Sentry servers irrespective of whether they are leader or
> not. Whereas the subsequent operations of HMSFollower are only limited to the
> leader of the Sentry group. To avoid extra connections, we can limit only the
> leader to get a connection to HMS.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
