You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2012/10/15 12:24:03 UTC

[jira] [Created] (BOOKKEEPER-434) [Hedwig CPP Client] Delay resolving default host until necessary.

Sijie Guo created BOOKKEEPER-434:
------------------------------------

             Summary: [Hedwig CPP Client] Delay resolving default host until necessary.
                 Key: BOOKKEEPER-434
                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-434
             Project: Bookkeeper
          Issue Type: Bug
          Components: hedwig-client
            Reporter: Sijie Guo
            Assignee: Sijie Guo
             Fix For: 4.2.0


1) default host might a VIP like name, we could delay resolving default host until necessary. so we could leverage the round-robin mechanism behind default server.

2) we should not fail the process (throwing exception) when the default server isn't reachable temporary. we could fail the request at that time.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (BOOKKEEPER-434) [Hedwig CPP Client] Delay resolving default host until necessary.

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

Sijie Guo updated BOOKKEEPER-434:
---------------------------------

    Attachment: BOOKKEEPER-434.diff

Attach a patch generated with --no-prefix.
                
> [Hedwig CPP Client] Delay resolving default host until necessary.
> -----------------------------------------------------------------
>
>                 Key: BOOKKEEPER-434
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-434
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: hedwig-client
>            Reporter: Sijie Guo
>            Assignee: Sijie Guo
>             Fix For: 4.2.0
>
>         Attachments: BOOKKEEPER-434.diff, BOOKKEEPER-434.diff
>
>
> 1) default host might a VIP like name, we could delay resolving default host until necessary. so we could leverage the round-robin mechanism behind default server.
> 2) we should not fail the process (throwing exception) when the default server isn't reachable temporary. we could fail the request at that time.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (BOOKKEEPER-434) [Hedwig CPP Client] Delay resolving default host until necessary.

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BOOKKEEPER-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488299#comment-13488299 ] 

Hudson commented on BOOKKEEPER-434:
-----------------------------------

Integrated in bookkeeper-trunk #783 (See [https://builds.apache.org/job/bookkeeper-trunk/783/])
    BOOKKEEPER-434: [Hedwig CPP Client] Delay resolving default host until necessary. (sijie via ivank) (Revision 1404255)

     Result = UNSTABLE
ivank : 
Files : 
* /zookeeper/bookkeeper/trunk/CHANGES.txt
* /zookeeper/bookkeeper/trunk/hedwig-client/src/main/cpp/lib/clientimpl.cpp
* /zookeeper/bookkeeper/trunk/hedwig-client/src/main/cpp/lib/clientimpl.h
* /zookeeper/bookkeeper/trunk/hedwig-client/src/main/cpp/test/publishtest.cpp
* /zookeeper/bookkeeper/trunk/hedwig-client/src/main/cpp/test/util.h

                
> [Hedwig CPP Client] Delay resolving default host until necessary.
> -----------------------------------------------------------------
>
>                 Key: BOOKKEEPER-434
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-434
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: hedwig-client
>            Reporter: Sijie Guo
>            Assignee: Sijie Guo
>             Fix For: 4.2.0
>
>         Attachments: BOOKKEEPER-434.diff, BOOKKEEPER-434.diff
>
>
> 1) default host might a VIP like name, we could delay resolving default host until necessary. so we could leverage the round-robin mechanism behind default server.
> 2) we should not fail the process (throwing exception) when the default server isn't reachable temporary. we could fail the request at that time.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (BOOKKEEPER-434) [Hedwig CPP Client] Delay resolving default host until necessary.

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

Sijie Guo updated BOOKKEEPER-434:
---------------------------------

    Attachment: BOOKKEEPER-434.diff

Attach a patch to delay resolving default host and a test case for it. The patch is generated based on BOOKKEEPER-369.
                
> [Hedwig CPP Client] Delay resolving default host until necessary.
> -----------------------------------------------------------------
>
>                 Key: BOOKKEEPER-434
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-434
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: hedwig-client
>            Reporter: Sijie Guo
>            Assignee: Sijie Guo
>             Fix For: 4.2.0
>
>         Attachments: BOOKKEEPER-434.diff
>
>
> 1) default host might a VIP like name, we could delay resolving default host until necessary. so we could leverage the round-robin mechanism behind default server.
> 2) we should not fail the process (throwing exception) when the default server isn't reachable temporary. we could fail the request at that time.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira