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

Posted to issues@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2017/10/17 21:29:04 UTC

[jira] [Commented] (BOOKKEEPER-842) Tests related to changing bookie id would fail if DNS resolution can't return hostname

    [ https://issues.apache.org/jira/browse/BOOKKEEPER-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208402#comment-16208402 ] 

Ivan Kelly commented on BOOKKEEPER-842:
---------------------------------------

Migrated to github https://github.com/apache/bookkeeper/issues/607

> Tests related to changing bookie id would fail if DNS resolution can't return hostname
> --------------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-842
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-842
>             Project: Bookkeeper
>          Issue Type: Improvement
>          Components: bookkeeper-server
>            Reporter: Sijie Guo
>              Labels: ghmigrated, iktriage1, test
>
> failed tests: UpdateCookieCmdTest, UpdateLedgerOpTest, CookieTest.
> Some are easier to get around. but some aren't. in general, we shouldn't tight changing bookie id to be just hostname and ip, we should be allowed to configure what bookie id to be used.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)