[
https://issues.apache.org/jira/browse/PHOENIX-7506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-7506:
---------------------------------
Description:
Crash in UngroupedAggregateRegionObserver.waitForScansToFinish causes crashes
on region stop.
# I am not sure about using a client property for coprocessor functionality
like this.
# Even ignoring that, if a scan takes longer that timeout, a crash will still
happen.
I am not sure if there is an easy fix for for this, but forcing a crash in this
case is not a good solution.
Does the coporcessor accept new calls after preClose is called ?
was:
Crash in UngroupedAggregateRegionObserver.waitForScansToFinish causes crashes
on region stop.
# I am not sure about using a client property for coprocessor functionality
like this.
# Even ignoring that, if a scan takes longer that timeout, a crash will still
happen.
I am not sure if there is an easy for for this, but forcing a crash in this
case is not a good solution.
Does the coporcessor accept new calls after preClose is called ?
> Crash in UngroupedAggregateRegionObserver.waitForScansToFinish on region move
> -----------------------------------------------------------------------------
>
> Key: PHOENIX-7506
> URL: https://issues.apache.org/jira/browse/PHOENIX-7506
> Project: Phoenix
> Issue Type: Bug
> Components: core
> Reporter: Istvan Toth
> Priority: Major
>
> Crash in UngroupedAggregateRegionObserver.waitForScansToFinish causes
> crashes on region stop.
> # I am not sure about using a client property for coprocessor functionality
> like this.
> # Even ignoring that, if a scan takes longer that timeout, a crash will
> still happen.
> I am not sure if there is an easy fix for for this, but forcing a crash in
> this case is not a good solution.
> Does the coporcessor accept new calls after preClose is called ?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
