hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18122) Scanner id should include ServerName of region server
Date Wed, 31 May 2017 07:39:04 GMT

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

Hadoop QA commented on HBASE-18122:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s {color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 8s {color} | {color:red}
HBASE-18122 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/0.3.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12870531/addendum.patch
|
| JIRA Issue | HBASE-18122 |
| Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/7020/console |
| Powered by | Apache Yetus 0.3.0   http://yetus.apache.org |


This message was automatically generated.



> Scanner id should include ServerName of region server
> -----------------------------------------------------
>
>                 Key: HBASE-18122
>                 URL: https://issues.apache.org/jira/browse/HBASE-18122
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.0.0, 1.4.0, 1.3.1, 1.1.10, 1.2.6
>            Reporter: Phil Yang
>            Assignee: Phil Yang
>             Fix For: 2.0.0, 1.4.0, 1.3.2, 1.1.11, 1.2.7
>
>         Attachments: addendum.patch, HBASE-18122.v01.patch, HBASE-18122.v02.patch, HBASE-18122.v03.patch,
HBASE-18122.v04.patch
>
>
> Now the scanner id is a long number from 1 to max in a region server. Each new scanner
will have a scanner id.
> If a client has a scanner whose id is x, when the RS restart and the scanner id is also
incremented to x or a little larger, there will be a scanner id collision.
> So the scanner id should now be same during each time the RS restart. We can add the
start timestamp as the highest several bits in scanner id uint64.
> And because HBASE-18121 is not easy to fix and there are many clients with old version.
We can also encode server host:port into the scanner id.
> So we can use ServerName.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message