You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Benjamin Reed (JIRA)" <ji...@apache.org> on 2008/11/24 22:31:44 UTC

[jira] Created: (ZOOKEEPER-238) HostAuthenicationProvider should be removed

HostAuthenicationProvider should be removed
-------------------------------------------

                 Key: ZOOKEEPER-238
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-238
             Project: Zookeeper
          Issue Type: Bug
            Reporter: Benjamin Reed


I think the way the HostAuthenticationProvider is implemented could cause serious performance problems if DNS is slow or broken. The problem is that we need to do a reverse hostname resolution during connection establishment. I suggest it be removed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (ZOOKEEPER-238) HostAuthenicationProvider should be removed

Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ZOOKEEPER-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mahadev konar updated ZOOKEEPER-238:
------------------------------------

    Fix Version/s: 3.2.0
                   3.2.1
         Assignee: Benjamin Reed

We fixed this in ZOOKEEPER-446.

> HostAuthenicationProvider should be removed
> -------------------------------------------
>
>                 Key: ZOOKEEPER-238
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-238
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: server
>            Reporter: Benjamin Reed
>            Assignee: Benjamin Reed
>             Fix For: 3.2.0, 3.2.1
>
>
> I think the way the HostAuthenticationProvider is implemented could cause serious performance problems if DNS is slow or broken. The problem is that we need to do a reverse hostname resolution during connection establishment. I suggest it be removed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (ZOOKEEPER-238) HostAuthenicationProvider should be removed

Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ZOOKEEPER-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mahadev konar resolved ZOOKEEPER-238.
-------------------------------------

    Resolution: Fixed

> HostAuthenicationProvider should be removed
> -------------------------------------------
>
>                 Key: ZOOKEEPER-238
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-238
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: server
>            Reporter: Benjamin Reed
>            Assignee: Benjamin Reed
>             Fix For: 3.2.1, 3.2.0
>
>
> I think the way the HostAuthenticationProvider is implemented could cause serious performance problems if DNS is slow or broken. The problem is that we need to do a reverse hostname resolution during connection establishment. I suggest it be removed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (ZOOKEEPER-238) HostAuthenicationProvider should be removed

Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ZOOKEEPER-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Hunt updated ZOOKEEPER-238:
-----------------------------------

    Component/s: server

> HostAuthenicationProvider should be removed
> -------------------------------------------
>
>                 Key: ZOOKEEPER-238
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-238
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: server
>            Reporter: Benjamin Reed
>
> I think the way the HostAuthenticationProvider is implemented could cause serious performance problems if DNS is slow or broken. The problem is that we need to do a reverse hostname resolution during connection establishment. I suggest it be removed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.