[jira] [Commented] (PHOENIX-5612) Upsert Select exceed limits on last execution step of joining threads final mutationState

[Hadoop QA (Jira)]

    [ 
https://issues.apache.org/jira/browse/PHOENIX-5612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16996542#comment-16996542
 ] 

Hadoop QA commented on PHOENIX-5612:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12988863/PHOENIX-5612.4.x-HBase-1.4.v1.patch
  against 4.x-HBase-1.4 branch at commit 
d73765a22ab0a0c9cf558cc6fa8dcef3c0c4b386.
  ATTACHMENT ID: 12988863

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {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.tx.TransactionIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.ImmutableIndexIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.MutableIndexFailureIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.MutableIndexFailureWithNamespaceIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.txn.MutableRollbackIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.tx.TxCheckpointIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.GlobalMutableTxIndexIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.MutableIndexIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.index.GlobalImmutableTxIndexIT
./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.execute.PartialCommitIT

Test results: 
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3194//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-PHOENIX-Build/3194//console

This message is automatically generated.

> Upsert Select exceed limits on last execution step of joining threads final 
> mutationState
> -----------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-5612
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5612
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.14.2, 4.14.3
>            Reporter: Alex Batyrshin
>            Priority: Major
>         Attachments: PHOENIX-5612.4.x-HBase-1.4.v1.patch, 
> commit_last_chunk.patch
>
>
> Upsert Select running via Parallel Iteration Factory does not commit last 
> chunk of data in iteration threads. Instead last chunk (MutationState) 
> returned to main thread. Next this final MutationState from all threads is 
> joining to connection.getMutatioState. This could result that 
> connection.getMutatioState grow up and exceed limits (maxSize or 
> maxSizeBytes).



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