You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Alex Batyrshin (Jira)" <ji...@apache.org> on 2019/12/11 11:52:00 UTC
[jira] [Updated] (PHOENIX-5612) Upsert Select exceed limits on last
execution step of joining threads final mutationState
[ https://issues.apache.org/jira/browse/PHOENIX-5612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Batyrshin updated PHOENIX-5612:
------------------------------------
Description: Upsert Select running via Parallel Iteration Factory does not commit last chunk of data in 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). (was: Upsert Select running via Parallel Iteration Factory does not commit last chunk of data in threads. Instead last chunk (MutationState) returned to main thread. Next this final MutationState is joining to connection.getMutatioState. This could result that connection.getMutatioState grow up and exceed limits (maxSize or maxSizeBytes).)
> 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
> Reporter: Alex Batyrshin
> Priority: Major
> Attachments: commit_last_chunk.patch
>
>
> Upsert Select running via Parallel Iteration Factory does not commit last chunk of data in 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)