[jira] [Commented] (AMBARI-22422) Ambari Metrics does not work with DateTieredStoreEngine
[
https://issues.apache.org/jira/browse/AMBARI-22422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251308#comment-16251308
]
Zhanwei Wang commented on AMBARI-22422:
---
Any comments on this issue?
> Ambari Metrics does not work with DateTieredStoreEngine
> ---
>
> Key: AMBARI-22422
> URL: https://issues.apache.org/jira/browse/AMBARI-22422
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.6.0
> Environment: centos7
>Reporter: Zhanwei Wang
> Attachments: ambari-metrics-collector-etc.tar.gz,
> ambari-metrics-collector-log.tar.gz
>
>
> I build Ambari from source code with tag release-2.6.0 and setup a three node
> centos7 cluster for test.
> With all default configurations, Ambari Metrics did not work and I found the
> following from HBase logs.
> {noformat}
> 2017-11-11 15:07:56,478 INFO
> [B.defaultRpcServer.handler=24,queue=0,port=40128] zookeeper.ZooKeeper:
> Initiating client connection, connectString=test3:61181 sessionTimeout=12
> watcher=hconnection-0x23f7d8350x0, quorum=test3:61181,
> baseZNode=/ams-hbase-unsecure
> @
>@
> at
> org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:129)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:128)
> 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)
> Caused by: java.io.IOException: Unable to load configured store engine
> 'org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine'
> at
> org.apache.hadoop.hbase.regionserver.StoreEngine.create(StoreEngine.java:128)
> at org.apache.hadoop.hbase.regionserver.HStore.(HStore.java:271)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:4958)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:905)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:902)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> ... 3 more
> Caused by: java.lang.UnsupportedOperationException: Unable to find
> org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine
> at
> org.apache.hadoop.hbase.util.ReflectionUtils.instantiateWithCustomCtor(ReflectionUtils.java:36)
> at
> org.apache.hadoop.hbase.regionserver.StoreEngine.create(StoreEngine.java:123)
> ... 10 more
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.hadoop.hbase.util.ReflectionUtils.instantiateWithCustomCtor(ReflectionUtils.java:32)
> ... 11 more
> {noformat}
> After adding the following to ams-site.xml. Ambari Metrics work normally. And
> no more Exception found in both collector and hbase logs.
> {noformat}
>
>
> timeline.metrics.hbase.aggregate.table.compaction.policy.class
> org.apache.hadoop.hbase.regionserver.DefaultStoreEngine
>
> {noformat}
> From HBASE-19223, Date Tiered Compaction is only available starting in the
> 1.3 release.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22423) Ambari Metrics does not work after restart service
[
https://issues.apache.org/jira/browse/AMBARI-22423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251306#comment-16251306
]
Zhanwei Wang commented on AMBARI-22423:
---
Does anyone has any idea to fix this issue?
> Ambari Metrics does not work after restart service
> --
>
> Key: AMBARI-22423
> URL: https://issues.apache.org/jira/browse/AMBARI-22423
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.6.0
> Environment: centos7
>Reporter: Zhanwei Wang
>
> I build Ambari from source code with tag release-2.6.0 and setup a three node
> centos7 cluster for test.
> With all default configurations I manager to make Ambari Metrics work
> normally. But after restart Ambari Metrics service, HBase died with following
> exception.
> {noformat}
> 2017-11-11 16:03:36,800 INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:61181]
> server.NIOServerCnxn: Closed socket connection for client
> /192.168.110.7:41352 which had sessionid 0x15faa1aa2a90005
> 2017-11-11 16:03:48,253 INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:61181]
> server.NIOServerCnxnFactory: Accepted socket connection from
> /192.168.110.7:41390
> 2017-11-11 16:03:48,258 INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:61181]
> server.ZooKeeperServer: Client attempting to establish new session at
> /192.168.110.7:41390
> 2017-11-11 16:03:48,262 INFO [SyncThread:0] server.ZooKeeperServer:
> Established session 0x15faa1aa2a90006 with negotiated timeout 12 for
> client /192.168.110.7:41390
> 2017-11-11 16:03:51,437 ERROR [main] master.HMasterCommandLine: Master exiting
> java.lang.RuntimeException: Master not active after 30 seconds
> at
> org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:194)
> at
> org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:227)
> at
> org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:139)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
> at
> org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126)
> at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2452)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22423) Ambari Metrics does not work after restart service
Zhanwei Wang created AMBARI-22423:
-
Summary: Ambari Metrics does not work after restart service
Key: AMBARI-22423
URL: https://issues.apache.org/jira/browse/AMBARI-22423
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: 2.6.0
Environment: centos7
Reporter: Zhanwei Wang
I build Ambari from source code with tag release-2.6.0 and setup a three node
centos7 cluster for test.
With all default configurations I manager to make Ambari Metrics work normally.
But after restart Ambari Metrics service, HBase died with following exception.
{noformat}
2017-11-11 16:03:36,800 INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:61181]
server.NIOServerCnxn: Closed socket connection for client /192.168.110.7:41352
which had sessionid 0x15faa1aa2a90005
2017-11-11 16:03:48,253 INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:61181]
server.NIOServerCnxnFactory: Accepted socket connection from
/192.168.110.7:41390
2017-11-11 16:03:48,258 INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:61181]
server.ZooKeeperServer: Client attempting to establish new session at
/192.168.110.7:41390
2017-11-11 16:03:48,262 INFO [SyncThread:0] server.ZooKeeperServer:
Established session 0x15faa1aa2a90006 with negotiated timeout 12 for client
/192.168.110.7:41390
2017-11-11 16:03:51,437 ERROR [main] master.HMasterCommandLine: Master exiting
java.lang.RuntimeException: Master not active after 30 seconds
at
org.apache.hadoop.hbase.util.JVMClusterUtil.startup(JVMClusterUtil.java:194)
at
org.apache.hadoop.hbase.LocalHBaseCluster.startup(LocalHBaseCluster.java:445)
at
org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:227)
at
org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:139)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
at
org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126)
at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2452)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22422) Ambari Metrics does not work with DateTieredStoreEngine
[
https://issues.apache.org/jira/browse/AMBARI-22422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhanwei Wang updated AMBARI-22422:
--
Attachment: ambari-metrics-collector-log.tar.gz
attach all collector logs
> Ambari Metrics does not work with DateTieredStoreEngine
> ---
>
> Key: AMBARI-22422
> URL: https://issues.apache.org/jira/browse/AMBARI-22422
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.6.0
> Environment: centos7
>Reporter: Zhanwei Wang
> Attachments: ambari-metrics-collector-etc.tar.gz,
> ambari-metrics-collector-log.tar.gz
>
>
> I build Ambari from source code with tag release-2.6.0 and setup a three node
> centos7 cluster for test.
> With all default configurations, Ambari Metrics did not work and I found the
> following from HBase logs.
> {noformat}
> 2017-11-11 15:07:56,478 INFO
> [B.defaultRpcServer.handler=24,queue=0,port=40128] zookeeper.ZooKeeper:
> Initiating client connection, connectString=test3:61181 sessionTimeout=12
> watcher=hconnection-0x23f7d8350x0, quorum=test3:61181,
> baseZNode=/ams-hbase-unsecure
> @
>@
> at
> org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:129)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:128)
> 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)
> Caused by: java.io.IOException: Unable to load configured store engine
> 'org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine'
> at
> org.apache.hadoop.hbase.regionserver.StoreEngine.create(StoreEngine.java:128)
> at org.apache.hadoop.hbase.regionserver.HStore.(HStore.java:271)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:4958)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:905)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:902)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> ... 3 more
> Caused by: java.lang.UnsupportedOperationException: Unable to find
> org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine
> at
> org.apache.hadoop.hbase.util.ReflectionUtils.instantiateWithCustomCtor(ReflectionUtils.java:36)
> at
> org.apache.hadoop.hbase.regionserver.StoreEngine.create(StoreEngine.java:123)
> ... 10 more
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.hadoop.hbase.util.ReflectionUtils.instantiateWithCustomCtor(ReflectionUtils.java:32)
> ... 11 more
> {noformat}
> After adding the following to ams-site.xml. Ambari Metrics work normally. And
> no more Exception found in both collector and hbase logs.
> {noformat}
>
>
> timeline.metrics.hbase.aggregate.table.compaction.policy.class
> org.apache.hadoop.hbase.regionserver.DefaultStoreEngine
>
> {noformat}
> From HBASE-19223, Date Tiered Compaction is only available starting in the
> 1.3 release.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22422) Ambari Metrics does not work with DateTieredStoreEngine
[
https://issues.apache.org/jira/browse/AMBARI-22422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhanwei Wang updated AMBARI-22422:
--
Attachment: ambari-metrics-collector-etc.tar.gz
attach collector configuration
> Ambari Metrics does not work with DateTieredStoreEngine
> ---
>
> Key: AMBARI-22422
> URL: https://issues.apache.org/jira/browse/AMBARI-22422
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.6.0
> Environment: centos7
>Reporter: Zhanwei Wang
> Attachments: ambari-metrics-collector-etc.tar.gz
>
>
> I build Ambari from source code with tag release-2.6.0 and setup a three node
> centos7 cluster for test.
> With all default configurations, Ambari Metrics did not work and I found the
> following from HBase logs.
> {noformat}
> 2017-11-11 15:07:56,478 INFO
> [B.defaultRpcServer.handler=24,queue=0,port=40128] zookeeper.ZooKeeper:
> Initiating client connection, connectString=test3:61181 sessionTimeout=12
> watcher=hconnection-0x23f7d8350x0, quorum=test3:61181,
> baseZNode=/ams-hbase-unsecure
> @
>@
> at
> org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:129)
> at
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:128)
> 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)
> Caused by: java.io.IOException: Unable to load configured store engine
> 'org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine'
> at
> org.apache.hadoop.hbase.regionserver.StoreEngine.create(StoreEngine.java:128)
> at org.apache.hadoop.hbase.regionserver.HStore.(HStore.java:271)
> at
> org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:4958)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:905)
> at
> org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:902)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> ... 3 more
> Caused by: java.lang.UnsupportedOperationException: Unable to find
> org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine
> at
> org.apache.hadoop.hbase.util.ReflectionUtils.instantiateWithCustomCtor(ReflectionUtils.java:36)
> at
> org.apache.hadoop.hbase.regionserver.StoreEngine.create(StoreEngine.java:123)
> ... 10 more
> Caused by: java.lang.ClassNotFoundException:
> org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.hadoop.hbase.util.ReflectionUtils.instantiateWithCustomCtor(ReflectionUtils.java:32)
> ... 11 more
> {noformat}
> After adding the following to ams-site.xml. Ambari Metrics work normally. And
> no more Exception found in both collector and hbase logs.
> {noformat}
>
>
> timeline.metrics.hbase.aggregate.table.compaction.policy.class
> org.apache.hadoop.hbase.regionserver.DefaultStoreEngine
>
> {noformat}
> From HBASE-19223, Date Tiered Compaction is only available starting in the
> 1.3 release.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22422) Ambari Metrics does not work with DateTieredStoreEngine
Zhanwei Wang created AMBARI-22422:
-
Summary: Ambari Metrics does not work with DateTieredStoreEngine
Key: AMBARI-22422
URL: https://issues.apache.org/jira/browse/AMBARI-22422
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: 2.6.0
Environment: centos7
Reporter: Zhanwei Wang
I build Ambari from source code with tag release-2.6.0 and setup a three node
centos7 cluster for test.
With all default configurations, Ambari Metrics did not work and I found the
following from HBase logs.
{noformat}
2017-11-11 15:07:56,478 INFO
[B.defaultRpcServer.handler=24,queue=0,port=40128] zookeeper.ZooKeeper:
Initiating client connection, connectString=test3:61181 sessionTimeout=12
watcher=hconnection-0x23f7d8350x0, quorum=test3:61181,
baseZNode=/ams-hbase-unsecure
@
@at
org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:129)
at
org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:128)
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)
Caused by: java.io.IOException: Unable to load configured store engine
'org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine'
at
org.apache.hadoop.hbase.regionserver.StoreEngine.create(StoreEngine.java:128)
at org.apache.hadoop.hbase.regionserver.HStore.(HStore.java:271)
at
org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:4958)
at org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:905)
at org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:902)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
... 3 more
Caused by: java.lang.UnsupportedOperationException: Unable to find
org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine
at
org.apache.hadoop.hbase.util.ReflectionUtils.instantiateWithCustomCtor(ReflectionUtils.java:36)
at
org.apache.hadoop.hbase.regionserver.StoreEngine.create(StoreEngine.java:123)
... 10 more
Caused by: java.lang.ClassNotFoundException:
org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at
org.apache.hadoop.hbase.util.ReflectionUtils.instantiateWithCustomCtor(ReflectionUtils.java:32)
... 11 more
{noformat}
After adding the following to ams-site.xml. Ambari Metrics work normally. And
no more Exception found in both collector and hbase logs.
{noformat}
timeline.metrics.hbase.aggregate.table.compaction.policy.class
org.apache.hadoop.hbase.regionserver.DefaultStoreEngine
{noformat}
>From HBASE-19223, Date Tiered Compaction is only available starting in the 1.3
>release.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
