[jira] [Resolved] (PHOENIX-6546) BackwardCompatibilityIT#testSystemTaskCreationWithIndexAsyncRebuild is flakey

2021-09-15 Thread Istvan Toth (Jira)


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

Istvan Toth resolved PHOENIX-6546.
--
Fix Version/s: 5.1.3
   4.16.2
   5.2.0
   4.17.0
   Resolution: Fixed

Committed to all active branches.
Thanks for the review [~vjasani]

> BackwardCompatibilityIT#testSystemTaskCreationWithIndexAsyncRebuild is flakey
> -
>
> Key: PHOENIX-6546
> URL: https://issues.apache.org/jira/browse/PHOENIX-6546
> Project: Phoenix
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.2.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
> Fix For: 4.17.0, 5.2.0, 4.16.2, 5.1.3
>
>
> The problem seems to be that we are testing for the succesful finishing of 
> the index rebuild task, which does not always happen in 50 seconds.
> However, we are really only interested in whether the task has been added, 
> we're not testing the rebuild task itself here.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (PHOENIX-6547) BasePermissionsIT is still a bit flakey

2021-09-15 Thread Istvan Toth (Jira)


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

Istvan Toth resolved PHOENIX-6547.
--
Fix Version/s: 5.1.3
   5.2.0
   Resolution: Fixed

Committed to master and 5.1
Thanks for the review [~vjasani]

> BasePermissionsIT is still a bit flakey
> ---
>
> Key: PHOENIX-6547
> URL: https://issues.apache.org/jira/browse/PHOENIX-6547
> Project: Phoenix
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.2.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
> Fix For: 5.2.0, 5.1.3
>
>
> We had a flakey execution (for two different profiles) at 
> {noformat}
> at 
> org.apache.phoenix.end2end.BasePermissionsIT.testAutomaticGrantWithIndexAndView(BasePermissionsIT.java:1394)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (PHOENIX-6544) Adding metadata inconsistency metric

2021-09-15 Thread Xinyi Yan (Jira)


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

Xinyi Yan resolved PHOENIX-6544.

Fix Version/s: 5.1.0
   4.16.1
   Resolution: Fixed

> Adding metadata inconsistency metric
> 
>
> Key: PHOENIX-6544
> URL: https://issues.apache.org/jira/browse/PHOENIX-6544
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: Xinyi Yan
>Assignee: Xinyi Yan
>Priority: Minor
> Fix For: 4.16.1, 5.1.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (PHOENIX-6548) Race condition when triggering index rebuilds as regionserver closes

2021-09-15 Thread Geoffrey Jacoby (Jira)
Geoffrey Jacoby created PHOENIX-6548:


 Summary: Race condition when triggering index rebuilds as 
regionserver closes
 Key: PHOENIX-6548
 URL: https://issues.apache.org/jira/browse/PHOENIX-6548
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 4.16.1, 4.14.3
Reporter: Geoffrey Jacoby


On each regionserver our coprocs keep a cache of HConnections with custom 
settings (such as short timeouts) for talking to other regionservers. They're 
used when coprocs need to make RPCs, such as during index rebuilds. 

When a regionserver is closed, these HConnections are closed as well. However, 
we've seen in our test pipelines a race condition where we may have just given 
out one of the HConnections to a coprocessor, only to have the connection 
closed just before it's used. 

This will produce an IllegalArgumentException from the HBase Table object, 
which (if the index rebuild was caused by a client Scan) will be thrown back to 
the client as a DoNotRetryIOException.

In this case we want the client exception to be a normal retriable IOException, 
because if they try again after the region comes up again somewhere else, the 
Scan will likely succeed. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (PHOENIX-6547) BasePermissionsIT is still a bit flakey

2021-09-15 Thread Istvan Toth (Jira)
Istvan Toth created PHOENIX-6547:


 Summary: BasePermissionsIT is still a bit flakey
 Key: PHOENIX-6547
 URL: https://issues.apache.org/jira/browse/PHOENIX-6547
 Project: Phoenix
  Issue Type: Bug
  Components: core
Affects Versions: 5.2.0
Reporter: Istvan Toth
Assignee: Istvan Toth


We had a flakey execution (for two different profiles) at 
{noformat}
at 
org.apache.phoenix.end2end.BasePermissionsIT.testAutomaticGrantWithIndexAndView(BasePermissionsIT.java:1394)
{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (PHOENIX-6546) BackwardCompatibilityIT#testSystemTaskCreationWithIndexAsyncRebuild is flakey

2021-09-15 Thread Istvan Toth (Jira)
Istvan Toth created PHOENIX-6546:


 Summary: 
BackwardCompatibilityIT#testSystemTaskCreationWithIndexAsyncRebuild is flakey
 Key: PHOENIX-6546
 URL: https://issues.apache.org/jira/browse/PHOENIX-6546
 Project: Phoenix
  Issue Type: Bug
  Components: core
Affects Versions: 5.2.0
Reporter: Istvan Toth
Assignee: Istvan Toth


The problem seems to be that we are testing for the succesful finishing of the 
index rebuild task, which does not always happen in 50 seconds.
However, we are really only interested in whether the task has been added, 
we're not testing the rebuild task itself here.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (PHOENIX-6545) IndexToolForNonTxGlobalIndexIT.testIndexToolFailedMapperNotRecordToResultTable() fails with HBase 2.1

2021-09-15 Thread Istvan Toth (Jira)


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

Istvan Toth updated PHOENIX-6545:
-
Labels: test  (was: )

> IndexToolForNonTxGlobalIndexIT.testIndexToolFailedMapperNotRecordToResultTable()
>  fails with HBase 2.1
> -
>
> Key: PHOENIX-6545
> URL: https://issues.apache.org/jira/browse/PHOENIX-6545
> Project: Phoenix
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.2.0
>Reporter: Istvan Toth
>Assignee: Istvan Toth
>Priority: Major
>  Labels: test
>
> IndexTool exists with 
> {noformat}
> Can't do incremental index verification on this version of HBase because raw 
> skip scan filters are not supported.
> {noformat}
> so we just need to skip this test for the Hbase 2.1 profile



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (PHOENIX-6545) IndexToolForNonTxGlobalIndexIT.testIndexToolFailedMapperNotRecordToResultTable() fails with HBase 2.1

2021-09-15 Thread Istvan Toth (Jira)
Istvan Toth created PHOENIX-6545:


 Summary: 
IndexToolForNonTxGlobalIndexIT.testIndexToolFailedMapperNotRecordToResultTable()
 fails with HBase 2.1
 Key: PHOENIX-6545
 URL: https://issues.apache.org/jira/browse/PHOENIX-6545
 Project: Phoenix
  Issue Type: Bug
  Components: core
Affects Versions: 5.2.0
Reporter: Istvan Toth
Assignee: Istvan Toth


IndexTool exists with 

{noformat}
Can't do incremental index verification on this version of HBase because raw 
skip scan filters are not supported.
{noformat}

so we just need to skip this test for the Hbase 2.1 profile



--
This message was sent by Atlassian Jira
(v8.3.4#803005)