phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajeshbabu Chintaguntla (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-4446) Sequence table region opening failing because of property setting attempt on read-only configuration
Date Tue, 12 Dec 2017 09:59:00 GMT

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

Rajeshbabu Chintaguntla updated PHOENIX-4446:
---------------------------------------------
    Attachment: PHOENIX-4446_addendum.patch

Here is the addendum fixes the WALReplayWithIndexWritesAndCompressedWALIT. The other failure
is flaky and not related to this issue. In the addendum skipping throwing exception on failures
to check WAL restoration. Otherwise we might go with check for the table existence and all
in PhoenixIndexFailurePolicy on exception which doesn't require for this issue.

> Sequence table region opening failing because of property setting attempt on read-only
configuration
> ----------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-4446
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4446
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Rajeshbabu Chintaguntla
>            Assignee: Rajeshbabu Chintaguntla
>             Fix For: 5.0.0
>
>         Attachments: PHOENIX-4446.patch, PHOENIX-4446_addendum.patch
>
>
> The sequence table region opening failed because we are trying to set a property to read
only configuration while initializing the Indexer coprocessor.
> {noformat}
> 2017-12-08 15:06:56,401 INFO  [RpcServer.default.FPBQ.Fifo.handler=29,queue=2,port=16020]
regionserver.RSRpcServices: Open SYSTEM.SEQUENCE,,1512725815924.f335e39a7727f8c17aa6b572a2c277a8.
> 2017-12-08 15:06:56,419 ERROR [RS_OPEN_PRIORITY_REGION-10.114.94.100:16020-0] coprocessor.CoprocessorHost:
The coprocessor org.apache.phoenix.hbase.index.Indexer threw java.lang.UnsupportedOperationException:
Read-only Configuration
> java.lang.UnsupportedOperationException: Read-only Configuration
>         at org.apache.hadoop.hbase.coprocessor.ReadOnlyConfiguration.setIfUnset(ReadOnlyConfiguration.java:134)
>         at org.apache.phoenix.index.PhoenixIndexBuilder.setup(PhoenixIndexBuilder.java:108)
>         at org.apache.phoenix.hbase.index.builder.IndexBuildManager.getIndexBuilder(IndexBuildManager.java:65)
>         at org.apache.phoenix.hbase.index.builder.IndexBuildManager.<init>(IndexBuildManager.java:56)
>         at org.apache.phoenix.hbase.index.Indexer.start(Indexer.java:215)
>         at org.apache.hadoop.hbase.coprocessor.BaseEnvironment.startup(BaseEnvironment.java:72)
>         at org.apache.hadoop.hbase.coprocessor.CoprocessorHost.checkAndLoadInstance(CoprocessorHost.java:264)
>         at org.apache.hadoop.hbase.coprocessor.CoprocessorHost.load(CoprocessorHost.java:227)
>         at org.apache.hadoop.hbase.coprocessor.CoprocessorHost.load(CoprocessorHost.java:186)
>         at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.loadTableCoprocessors(RegionCoprocessorHost.java:420)
>         at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.<init>(RegionCoprocessorHost.java:276)
>         at org.apache.hadoop.hbase.regionserver.HRegion.<init>(HRegion.java:797)
>         at org.apache.hadoop.hbase.regionserver.HRegion.<init>(HRegion.java:699)
>         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>         at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
>         at org.apache.hadoop.hbase.regionserver.HRegion.newHRegion(HRegion.java:6749)
>         at org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:6949)
>         at org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:6921)
>         at org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:6877)
>         at org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:6828)
>         at org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:285)
>         at org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:110)
>         at org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:104)
>         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)
> 2017-12-08 15:06:56,420 FATAL [RS_OPEN_PRIORITY_REGION-10.114.94.100:16020-0] regionserver.HRegionServer:
***** ABORTING region server 10.114.94.100,16020,1512725637060: The coprocessor org.apache.phoenix.hbase.index.Indexer
threw java.lang.UnsupportedOperationException: Read-only Configuration *****
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message