hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chia-Ping Tsai (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-18415) The "retry" may cause TableExistsException even if the table doesn't exist
Date Mon, 24 Jul 2017 14:56:00 GMT

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

Chia-Ping Tsai updated HBASE-18415:
-----------------------------------
    Description: After a timeout occurs on first request, client will retry the request with
distinct group/nonce. The second request may bring the TableXXXException back if the first
request have changed the table state.  (was: After a timeout occurs on first request, client
will retry the request with distinct group/nonce. The second request may bring the TableExistsException
back if the first request is done.)

> The "retry" may cause TableExistsException even if the table doesn't exist
> --------------------------------------------------------------------------
>
>                 Key: HBASE-18415
>                 URL: https://issues.apache.org/jira/browse/HBASE-18415
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>             Fix For: 3.0.0, 1.5.0, 2.0.0-alpha-2
>
>         Attachments: HBASE-18415.branch-1.ut.patch, HBASE-18415.branch-1.v0.patch, HBASE-18415.branch-1.v1.patch
>
>
> After a timeout occurs on first request, client will retry the request with distinct
group/nonce. The second request may bring the TableXXXException back if the first request
have changed the table state.



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

Mime
View raw message