You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Chia-Ping Tsai (JIRA)" <ji...@apache.org> on 2017/09/13 21:31:00 UTC
[jira] [Updated] (HBASE-18415) The "retry" may cause
TableExistsException even if the table did not exist before
[ https://issues.apache.org/jira/browse/HBASE-18415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chia-Ping Tsai updated HBASE-18415:
-----------------------------------
Summary: The "retry" may cause TableExistsException even if the table did not exist before (was: The "retry" may cause TableExistsException even if the table doesn't exist)
> The "retry" may cause TableExistsException even if the table did not exist before
> ---------------------------------------------------------------------------------
>
> 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: 2.0.0
>
> 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)