You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@phoenix.apache.org by "jinzhuan@wacai.com" <ji...@wacai.com> on 2016/08/26 14:22:22 UTC
error after upgrade to 4.8-hbase-1.1
after upgraded , a lot of WARN logs in hbase-regionserver.log:
2016-08-26 22:12:39,682 WARN [pool-287-thread-1] coprocessor.MetaDataRegionObserver: ScheduledBuildIndexTask failed!
java.lang.IllegalArgumentException
at org.apache.phoenix.index.IndexMaintainer.create(IndexMaintainer.java:121)
at org.apache.phoenix.schema.PTableImpl.getIndexMaintainer(PTableImpl.java:957)
at org.apache.phoenix.coprocessor.MetaDataRegionObserver$BuildIndexScheduleTask.run(MetaDataRegionObserver.java:318)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
jinzhuan@wacai.com
Re: error after upgrade to 4.8-hbase-1.1
Posted by Ankit Singhal <an...@gmail.com>.
probably , you are hitting the following bug(I just reported today).
https://issues.apache.org/jira/browse/PHOENIX-3237
Because of above bug, data table is trying to get the index maintainers of
disabled index of another table.
You can check it with below query:-
select
TABLE_NAME,DATA_TABLE_NAME,INDEX_TYPE,INDEX_STATE,INDEX_DISABLE_TIMESTAMP
from system.catalog where INDEX_TYPE is not null;
INDEX_DISABLE_TIMESTAMP>0 for more than one data table.
As a workaround , I think for now , if possible, we need to rebuild indexes
of one data table manually by using (Alter INDEX .. REBUILD) command.
Regards,
Ankit Singhal
On Fri, Aug 26, 2016 at 7:52 PM, jinzhuan@wacai.com <ji...@wacai.com>
wrote:
> after upgraded , a lot of WARN logs in hbase-regionserver.log:
>
>
> 2016-08-26 22:12:39,682 WARN [pool-287-thread-1] coprocessor.
> MetaDataRegionObserver: ScheduledBuildIndexTask failed!
> java.lang.IllegalArgumentException
> at org.apache.phoenix.index.IndexMaintainer.create(
> IndexMaintainer.java:121)
> at org.apache.phoenix.schema.PTableImpl.getIndexMaintainer(
> PTableImpl.java:957)
> at org.apache.phoenix.coprocessor.MetaDataRegionObserver$
> BuildIndexScheduleTask.run(MetaDataRegionObserver.java:318)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> at java.util.concurrent.ScheduledThreadPoolExecutor$
> ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
> at java.util.concurrent.ScheduledThreadPoolExecutor$
> ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
>
> ------------------------------
> jinzhuan@wacai.com
>