You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2026/05/18 23:29:00 UTC

[jira] [Updated] (PHOENIX-7831) PhoenixQueryTimeoutIT wait for DelayedRegionObserver to load

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

Viraj Jasani updated PHOENIX-7831:
----------------------------------
    Fix Version/s: 5.3.2
                       (was: 5.3.1)

> PhoenixQueryTimeoutIT wait for DelayedRegionObserver to load
> ------------------------------------------------------------
>
>                 Key: PHOENIX-7831
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-7831
>             Project: Phoenix
>          Issue Type: Sub-task
>          Components: test
>            Reporter: Andrew Kyle Purtell
>            Assignee: Andrew Kyle Purtell
>            Priority: Minor
>             Fix For: 5.4.0, 5.3.2
>
>
> {{testScanningResultIteratorQueryTimeoutForPagingWithVeryLowTimeout}} attaches a {{DelayedRegionObserver}} to its data table so the test query reliably times out, but {{addCoprocessor}} only invokes {{{}admin.modifyTable{}}}, which returns as soon as the master {{TableDescriptor}} is updated and does not wait for region servers to reopen the affected regions with the new coprocessor. The query then runs immediately against the old observer chain, completes too quickly, and the timeout assertion fails. The fix polls {{region.getCoprocessorHost().findCoprocessor()}} on every region of the test table after {{addCoprocessor}} until the coprocessor is loaded.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)