You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@sentry.apache.org by "Vamsee Yarlagadda (JIRA)" <ji...@apache.org> on 2017/02/17 17:52:41 UTC

[jira] [Updated] (SENTRY-1635) Limit HMS connections only to the leader of the sentry servers

     [ https://issues.apache.org/jira/browse/SENTRY-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vamsee Yarlagadda updated SENTRY-1635:
--------------------------------------
    Status: Patch Available  (was: Open)

> 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
>
>
> 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)