[
https://issues.apache.org/jira/browse/PHOENIX-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17195925#comment-17195925
]
Hadoop QA commented on PHOENIX-6072:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/13011530/PHOENIX-6072-4.x-v1.patch
against 4.x branch at commit .
ATTACHMENT ID: 13011530
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:red}-1 core tests{color}. The patch failed these unit tests:
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.InQueryIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.UngroupedIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.ConcurrentMutationsExtendedIT
Test results:
https://ci-hadoop.apache.org/job/PreCommit-PHOENIX-Build/89//testReport/
Code Coverage results:
https://ci-hadoop.apache.org/job/PreCommit-PHOENIX-Build/89//artifact/phoenix-core/target/site/jacoco/index.html
Console output:
https://ci-hadoop.apache.org/job/PreCommit-PHOENIX-Build/89//console
This message is automatically generated.
> SYSTEM.MUTEX not created with a TTL on a fresh cluster connected to by a
> 4.15+ client
> -------------------------------------------------------------------------------------
>
> Key: PHOENIX-6072
> URL: https://issues.apache.org/jira/browse/PHOENIX-6072
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 4.15.0
> Reporter: Chinmay Kulkarni
> Assignee: Chinmay Kulkarni
> Priority: Blocker
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-6072-4.x-v1.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> If you have a fresh cluster that is directly connected to via a 4.15+ client,
> then SYSTEM.MUTEX gets created without a TTL (See
> [this|https://github.com/apache/phoenix/blob/a99db61cd82ae2b83add2a1bd74fd80baa5c91c7/phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java#L3335])
> The SYSTEM.MUTEX
> [DDL|https://github.com/apache/phoenix/blob/a99db61cd82ae2b83add2a1bd74fd80baa5c91c7/phoenix-core/src/main/java/org/apache/phoenix/query/QueryConstants.java#L367-L379]
> does not specify a TTL.
> This will obviously be a problem when a client does any operation that
> requires writing a cell to SYSTEM.MUTEX via checkAndPut (like add/drop
> column, create view, etc.) and dies/gets disconnected before being able to
> delete the mutex cell.
> After that point, since the cell will stay written and never be TTL’ed, any
> operation which requires a checkAndPut on that cell will always fail with a
> ConcurrentTableMutationException, deeming any further add/drop cols or create
> view for the same name impossible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
