[
https://issues.apache.org/jira/browse/HBASE-18122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030898#comment-16030898
]
Hudson commented on HBASE-18122:
--------------------------------
SUCCESS: Integrated in Jenkins build HBase-1.4 #753 (See
[https://builds.apache.org/job/HBase-1.4/753/])
HBASE-18122 Scanner id should include ServerName of region server (yangzhe1991:
rev e670be690f143a3fbfa97fdecd110baa5f7c3fa7)
* (add)
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ScannerIdGenerator.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java
> 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)
