[
https://issues.apache.org/jira/browse/PHOENIX-6104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17255299#comment-17255299
]
Viraj Jasani edited comment on PHOENIX-6104 at 12/27/20, 6:31 PM:
------------------------------------------------------------------
{quote}I think that the root cause in a bug in HBase 2.3, and we should
eventually file an HBase bug for it, as the current method works fine up to
HBase 2.2.
{quote}
Sure, I think we can do this, the only thing I feel might happen is they will
reject this idea of disabling table while splitting is happening
asynchronously, but sure good to get 100% confirmation on this.
However, real issue here seems that SYSTEM.CATALOG is not even being split in
reality. Even with HBase 2.1.
I think a check is missing that can confirm whether we have two SYSCAT daughter
regions online. If we have this check, test might be failing all the time. Let
me also compare actual splitting behaviour in Phoenix 4.x tests.
was (Author: vjasani):
{quote}I think that the root cause in a bug in HBase 2.3, and we should
eventually file an HBase bug for it, as the current method works fine up to
HBase 2.2.
{quote}
Sure, I think we can do this, the only thing I feel might happen is they will
reject this idea of disabling table while splitting is happening
asynchronously, but sure good to get 100% confirmation on this.
However, real issue here seems that SYSTEM.CATALOG is not even being split in
reality. Even with HBase 2.1.
> SplitSystemCatalogIT tests very unstable with Hbase 2.3
> -------------------------------------------------------
>
> Key: PHOENIX-6104
> URL: https://issues.apache.org/jira/browse/PHOENIX-6104
> Project: Phoenix
> Issue Type: Bug
> Components: core
> Affects Versions: 5.1.0
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Attachments: 6104-testouput.log
>
>
> The failure is in the test preparation code, where we split the system
> catalog table, and it seems to be a HBase issue, rather than a Phoenix one,
> but we need to track the issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
