[
https://issues.apache.org/jira/browse/PHOENIX-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16172630#comment-16172630
]
Rajeshbabu Chintaguntla commented on PHOENIX-4215:
--------------------------------------------------
[~jamestaylor]
bq. FYI, I have a test and found and fixed a few issues. Will post patch after
I clean it up, Rajeshbabu Chintaguntla.
Super. Thanks.
bq. To write the test, you'd just create your own Clock class and inject it as
the other tests are doing. Just set
QueryServices.INDEX_FAILURE_HANDLING_REBUILD_PERIOD in the setup to a
reasonable value (not large enough to trigger batches in other tests) and
UPSERT some rows with timestamps that will cause batching to occur. You can
copy/paste other tests there.
In the testcase patch uploaded here PHOENIX-4215_testcase.patch setting period
to 1000 milli seconds. With this able to reproduce the issue and meeting all
the requirements what ever you are saying. As you already said you have a test
that's cool.
> Partial index rebuild never complete after PHOENIX-3525 when rebuild period
> is configured
> -----------------------------------------------------------------------------------------
>
> Key: PHOENIX-4215
> URL: https://issues.apache.org/jira/browse/PHOENIX-4215
> Project: Phoenix
> Issue Type: Bug
> Reporter: Rajeshbabu Chintaguntla
> Assignee: Rajeshbabu Chintaguntla
> Fix For: 4.12.0
>
> Attachments: PHOENIX-4215_testcase.patch
>
>
> Currently the default value of phoenix.index.failure.handling.rebuild.period
> is long max. When we configure it some thing like an hour or day then partial
> index rebuild never complete and the index is never usable until recreate it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
