[jira] [Commented] (AMBARI-22321) Add Registry StackFeatures to HDP StackFeatures
[
https://issues.apache.org/jira/browse/AMBARI-22321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248772#comment-16248772
]
Yolanda M. Davis commented on AMBARI-22321:
---
[~jluniya] Since these features are aligned with the Stack Version I think they
should be set to 2.6.3.0 instead of 2.6.0, Is that accurate? If so I have a
suggested update below:
{code:java}
{
"name": "registry_remove_rootpath",
"description": "Registry remove root path setting",
"min_version": "2.6.3.0"
},
{
"name": "registry_allowed_resources_support",
"description": "Registry allowed resources",
"min_version": "2.6.3.0"
},
{
"name": "registry_rewriteuri_filter_support",
"description": "Registry RewriteUri servlet filter",
"min_version": "2.6.3.0"
}
{code}
> Add Registry StackFeatures to HDP StackFeatures
> ---
>
> Key: AMBARI-22321
> URL: https://issues.apache.org/jira/browse/AMBARI-22321
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.6.1
>
>
> {code}
> {
> "name": "registry_remove_rootpath",
> "description": "Registry remove root path setting",
> "min_version": "2.6.0.0"
> },
> {
> "name": "registry_allowed_resources_support",
> "description": "Registry allowed resources",
> "min_version": "2.6.0.0"
> },
> {
> "name": "registry_rewriteuri_filter_support",
> "description": "Registry RewriteUri servlet filter",
> "min_version": "2.6.0.0"
> }
> {code}
--
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)
