[
https://issues.apache.org/jira/browse/PHOENIX-4215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16181395#comment-16181395
]
James Taylor commented on PHOENIX-4215:
---------------------------------------
bq. 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.
For the record, [~rajeshbabu], your test did not uncover PHOENIX-4220. Without
this fix, every batch would have written everything from the start of the batch
until LATEST_TIMESTAMP (which obviously completely defeats the idea of time
batching and would have performed horribly). We need to be more diligent in our
testing, IMHO.
> 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, PHOENIX-4215_wip2.patch,
> PHOENIX-4215_wip.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)
