You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2018/08/01 06:23:15 UTC

[jira] [Issue Comment Deleted] (HBASE-18122) Scanner id should include ServerName of region server

     [ https://issues.apache.org/jira/browse/HBASE-18122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gavin updated HBASE-18122:
--------------------------
    Comment: was deleted

(was: A comment with security level 'jira-users' was removed.)

> 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: 1.4.0, 1.3.1, 1.1.10, 1.2.6, 2.0.0
>            Reporter: Phil Yang
>            Assignee: Phil Yang
>            Priority: Major
>             Fix For: 1.4.0, 1.3.2, 1.1.11, 1.2.7, 2.0.0
>
>         Attachments: HBASE-18122.v01.patch, HBASE-18122.v02.patch, HBASE-18122.v03.patch, HBASE-18122.v04.patch, addendum.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
(v7.6.3#76005)