hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18178) [C++] Retrying meta location lookup and zookeeper connection
Date Wed, 14 Jun 2017 20:03:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049598#comment-16049598

Enis Soztutar commented on HBASE-18178:

bq. Is the above going to be done in next patch or new JIRA ?
We cannot do this in this jira. Will be follow up jira. 
bq. Why is the retry number increased ?
Because retry number is 35 in the Java side. It should not have been 31. 
bq. Change the log level. (There're other LOG(INFO)'s in the patch)
Log level is correct. It is intentionally INFO. 
bq. Is the return statement effective ?
No it is not. However, we need it because of the static assertion for the folly::Future template.

> [C++] Retrying meta location lookup and zookeeper connection 
> -------------------------------------------------------------
>                 Key: HBASE-18178
>                 URL: https://issues.apache.org/jira/browse/HBASE-18178
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>         Attachments: hbase-18178-v1.patch
> Currently location-cache can only do a single lookup to meta. If meta location changes
or we have zookeeper connection problems, we never retry. 

This message was sent by Atlassian JIRA

View raw message