[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[
https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qin Liu updated AMBARI-21821:
-
Status: Patch Available (was: Open)
> Update Ambari Metrics service check to support HTTP SPNEGO authentication
> -
>
> Key: AMBARI-21821
> URL: https://issues.apache.org/jira/browse/AMBARI-21821
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-21821.patch
>
>
> This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
> authenticate".
> In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
> Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
> Ambari Metrics service check currently does not support Kerberos HTTP SPNEGO
> authentication.
> 2017-08-24 16:13:44,078 - Ambari Metrics service check was started.
> 2017-08-24 16:13:44,109 - Generated metrics for host amshost.example.com :
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host.example.com",
> "timestamp": 1503616424000,
> "starttime": 1503616424000,
> "metrics": {
> "1503616424000": 0.164134766408,
> "1503616425000": 1503616424000
> }
> }
> ]
> }
> 2017-08-24 16:13:44,114 - Connecting (POST) to
> amshost.example.com:6188/ws/v1/timeline/metrics/
> 2017-08-24 16:13:44,117 - Http response for host amshost.example.com: 401
> Authentication required
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[
https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qin Liu updated AMBARI-21821:
-
Attachment: AMBARI-21821.patch
> Update Ambari Metrics service check to support HTTP SPNEGO authentication
> -
>
> Key: AMBARI-21821
> URL: https://issues.apache.org/jira/browse/AMBARI-21821
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-21821.patch
>
>
> This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
> authenticate".
> In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
> Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
> Ambari Metrics service check currently does not support Kerberos HTTP SPNEGO
> authentication.
> 2017-08-24 16:13:44,078 - Ambari Metrics service check was started.
> 2017-08-24 16:13:44,109 - Generated metrics for host amshost.example.com :
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host.example.com",
> "timestamp": 1503616424000,
> "starttime": 1503616424000,
> "metrics": {
> "1503616424000": 0.164134766408,
> "1503616425000": 1503616424000
> }
> }
> ]
> }
> 2017-08-24 16:13:44,114 - Connecting (POST) to
> amshost.example.com:6188/ws/v1/timeline/metrics/
> 2017-08-24 16:13:44,117 - Http response for host amshost.example.com: 401
> Authentication required
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[
https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qin Liu updated AMBARI-21821:
-
Attachment: (was: AMBARI-21821.patch)
> Update Ambari Metrics service check to support HTTP SPNEGO authentication
> -
>
> Key: AMBARI-21821
> URL: https://issues.apache.org/jira/browse/AMBARI-21821
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
>
> This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
> authenticate".
> In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
> Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
> Ambari Metrics service check currently does not support Kerberos HTTP SPNEGO
> authentication.
> 2017-08-24 16:13:44,078 - Ambari Metrics service check was started.
> 2017-08-24 16:13:44,109 - Generated metrics for host amshost.example.com :
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host.example.com",
> "timestamp": 1503616424000,
> "starttime": 1503616424000,
> "metrics": {
> "1503616424000": 0.164134766408,
> "1503616425000": 1503616424000
> }
> }
> ]
> }
> 2017-08-24 16:13:44,114 - Connecting (POST) to
> amshost.example.com:6188/ws/v1/timeline/metrics/
> 2017-08-24 16:13:44,117 - Http response for host amshost.example.com: 401
> Authentication required
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[
https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qin Liu updated AMBARI-21821:
-
Status: Open (was: Patch Available)
> Update Ambari Metrics service check to support HTTP SPNEGO authentication
> -
>
> Key: AMBARI-21821
> URL: https://issues.apache.org/jira/browse/AMBARI-21821
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
>
> This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
> authenticate".
> In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
> Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
> Ambari Metrics service check currently does not support Kerberos HTTP SPNEGO
> authentication.
> 2017-08-24 16:13:44,078 - Ambari Metrics service check was started.
> 2017-08-24 16:13:44,109 - Generated metrics for host amshost.example.com :
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host.example.com",
> "timestamp": 1503616424000,
> "starttime": 1503616424000,
> "metrics": {
> "1503616424000": 0.164134766408,
> "1503616425000": 1503616424000
> }
> }
> ]
> }
> 2017-08-24 16:13:44,114 - Connecting (POST) to
> amshost.example.com:6188/ws/v1/timeline/metrics/
> 2017-08-24 16:13:44,117 - Http response for host amshost.example.com: 401
> Authentication required
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[
https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qin Liu updated AMBARI-21821:
-
Attachment: AMBARI-21821.patch
> Update Ambari Metrics service check to support HTTP SPNEGO authentication
> -
>
> Key: AMBARI-21821
> URL: https://issues.apache.org/jira/browse/AMBARI-21821
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-21821.patch
>
>
> This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
> authenticate".
> In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
> Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
> Ambari Metrics service check currently does not support Kerberos HTTP SPNEGO
> authentication.
> 2017-08-24 16:13:44,078 - Ambari Metrics service check was started.
> 2017-08-24 16:13:44,109 - Generated metrics for host amshost.example.com :
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host.example.com",
> "timestamp": 1503616424000,
> "starttime": 1503616424000,
> "metrics": {
> "1503616424000": 0.164134766408,
> "1503616425000": 1503616424000
> }
> }
> ]
> }
> 2017-08-24 16:13:44,114 - Connecting (POST) to
> amshost.example.com:6188/ws/v1/timeline/metrics/
> 2017-08-24 16:13:44,117 - Http response for host amshost.example.com: 401
> Authentication required
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[
https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qin Liu updated AMBARI-21821:
-
Status: Patch Available (was: Open)
> Update Ambari Metrics service check to support HTTP SPNEGO authentication
> -
>
> Key: AMBARI-21821
> URL: https://issues.apache.org/jira/browse/AMBARI-21821
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-21821.patch
>
>
> This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
> authenticate".
> In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
> Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
> Ambari Metrics service check currently does not support Kerberos HTTP SPNEGO
> authentication.
> 2017-08-24 16:13:44,078 - Ambari Metrics service check was started.
> 2017-08-24 16:13:44,109 - Generated metrics for host amshost.example.com :
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host.example.com",
> "timestamp": 1503616424000,
> "starttime": 1503616424000,
> "metrics": {
> "1503616424000": 0.164134766408,
> "1503616425000": 1503616424000
> }
> }
> ]
> }
> 2017-08-24 16:13:44,114 - Connecting (POST) to
> amshost.example.com:6188/ws/v1/timeline/metrics/
> 2017-08-24 16:13:44,117 - Http response for host amshost.example.com: 401
> Authentication required
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[
https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qin Liu updated AMBARI-21821:
-
Status: Open (was: Patch Available)
> Update Ambari Metrics service check to support HTTP SPNEGO authentication
> -
>
> Key: AMBARI-21821
> URL: https://issues.apache.org/jira/browse/AMBARI-21821
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-21821.patch
>
>
> This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
> authenticate".
> In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
> Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
> Ambari Metrics service check currently does not support Kerberos HTTP SPNEGO
> authentication.
> 2017-08-24 16:13:44,078 - Ambari Metrics service check was started.
> 2017-08-24 16:13:44,109 - Generated metrics for host amshost.example.com :
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host.example.com",
> "timestamp": 1503616424000,
> "starttime": 1503616424000,
> "metrics": {
> "1503616424000": 0.164134766408,
> "1503616425000": 1503616424000
> }
> }
> ]
> }
> 2017-08-24 16:13:44,114 - Connecting (POST) to
> amshost.example.com:6188/ws/v1/timeline/metrics/
> 2017-08-24 16:13:44,117 - Http response for host amshost.example.com: 401
> Authentication required
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[
https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qin Liu updated AMBARI-21821:
-
Attachment: (was: AMBARI-21821.patch)
> Update Ambari Metrics service check to support HTTP SPNEGO authentication
> -
>
> Key: AMBARI-21821
> URL: https://issues.apache.org/jira/browse/AMBARI-21821
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-21821.patch
>
>
> This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
> authenticate".
> In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
> Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
> Ambari Metrics service check currently does not support Kerberos HTTP SPNEGO
> authentication.
> 2017-08-24 16:13:44,078 - Ambari Metrics service check was started.
> 2017-08-24 16:13:44,109 - Generated metrics for host amshost.example.com :
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host.example.com",
> "timestamp": 1503616424000,
> "starttime": 1503616424000,
> "metrics": {
> "1503616424000": 0.164134766408,
> "1503616425000": 1503616424000
> }
> }
> ]
> }
> 2017-08-24 16:13:44,114 - Connecting (POST) to
> amshost.example.com:6188/ws/v1/timeline/metrics/
> 2017-08-24 16:13:44,117 - Http response for host amshost.example.com: 401
> Authentication required
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[
https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qin Liu updated AMBARI-21821:
-
Attachment: (was: AMBARI-21821.patch)
> Update Ambari Metrics service check to support HTTP SPNEGO authentication
> -
>
> Key: AMBARI-21821
> URL: https://issues.apache.org/jira/browse/AMBARI-21821
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-21821.patch
>
>
> This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
> authenticate".
> In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
> Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
> Ambari Metrics service check currently does not support Kerberos HTTP SPNEGO
> authentication.
> 2017-08-24 16:13:44,078 - Ambari Metrics service check was started.
> 2017-08-24 16:13:44,109 - Generated metrics for host amshost.example.com :
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host.example.com",
> "timestamp": 1503616424000,
> "starttime": 1503616424000,
> "metrics": {
> "1503616424000": 0.164134766408,
> "1503616425000": 1503616424000
> }
> }
> ]
> }
> 2017-08-24 16:13:44,114 - Connecting (POST) to
> amshost.example.com:6188/ws/v1/timeline/metrics/
> 2017-08-24 16:13:44,117 - Http response for host amshost.example.com: 401
> Authentication required
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[
https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qin Liu updated AMBARI-21821:
-
Status: Patch Available (was: Open)
> Update Ambari Metrics service check to support HTTP SPNEGO authentication
> -
>
> Key: AMBARI-21821
> URL: https://issues.apache.org/jira/browse/AMBARI-21821
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-21821.patch
>
>
> This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
> authenticate".
> In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
> Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
> Ambari Metrics service check currently does not support Kerberos HTTP SPNEGO
> authentication.
> 2017-08-24 16:13:44,078 - Ambari Metrics service check was started.
> 2017-08-24 16:13:44,109 - Generated metrics for host amshost.example.com :
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host.example.com",
> "timestamp": 1503616424000,
> "starttime": 1503616424000,
> "metrics": {
> "1503616424000": 0.164134766408,
> "1503616425000": 1503616424000
> }
> }
> ]
> }
> 2017-08-24 16:13:44,114 - Connecting (POST) to
> amshost.example.com:6188/ws/v1/timeline/metrics/
> 2017-08-24 16:13:44,117 - Http response for host amshost.example.com: 401
> Authentication required
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[
https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qin Liu updated AMBARI-21821:
-
Attachment: AMBARI-21821.patch
> Update Ambari Metrics service check to support HTTP SPNEGO authentication
> -
>
> Key: AMBARI-21821
> URL: https://issues.apache.org/jira/browse/AMBARI-21821
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-21821.patch
>
>
> This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
> authenticate".
> In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
> Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
> Ambari Metrics service check currently does not support Kerberos HTTP SPNEGO
> authentication.
> 2017-08-24 16:13:44,078 - Ambari Metrics service check was started.
> 2017-08-24 16:13:44,109 - Generated metrics for host amshost.example.com :
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host.example.com",
> "timestamp": 1503616424000,
> "starttime": 1503616424000,
> "metrics": {
> "1503616424000": 0.164134766408,
> "1503616425000": 1503616424000
> }
> }
> ]
> }
> 2017-08-24 16:13:44,114 - Connecting (POST) to
> amshost.example.com:6188/ws/v1/timeline/metrics/
> 2017-08-24 16:13:44,117 - Http response for host amshost.example.com: 401
> Authentication required
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[
https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qin Liu updated AMBARI-21821:
-
Description:
This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
authenticate".
In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
Ambari Metrics service check currently does not support Kerberos HTTP SPNEGO
authentication.
2017-08-24 16:13:44,078 - Ambari Metrics service check was started.
2017-08-24 16:13:44,109 - Generated metrics for host amshost.example.com :
{
"metrics": [
{
"metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
"appid": "amssmoketestfake",
"hostname": "host.example.com",
"timestamp": 1503616424000,
"starttime": 1503616424000,
"metrics": {
"1503616424000": 0.164134766408,
"1503616425000": 1503616424000
}
}
]
}
2017-08-24 16:13:44,114 - Connecting (POST) to
amshost.example.com:6188/ws/v1/timeline/metrics/
2017-08-24 16:13:44,117 - Http response for host amshost.example.com: 401
Authentication required
> Update Ambari Metrics service check to support HTTP SPNEGO authentication
> -
>
> Key: AMBARI-21821
> URL: https://issues.apache.org/jira/browse/AMBARI-21821
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
>
> This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
> authenticate".
> In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
> Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
> Ambari Metrics service check currently does not support Kerberos HTTP SPNEGO
> authentication.
> 2017-08-24 16:13:44,078 - Ambari Metrics service check was started.
> 2017-08-24 16:13:44,109 - Generated metrics for host amshost.example.com :
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host.example.com",
> "timestamp": 1503616424000,
> "starttime": 1503616424000,
> "metrics": {
> "1503616424000": 0.164134766408,
> "1503616425000": 1503616424000
> }
> }
> ]
> }
> 2017-08-24 16:13:44,114 - Connecting (POST) to
> amshost.example.com:6188/ws/v1/timeline/metrics/
> 2017-08-24 16:13:44,117 - Http response for host amshost.example.com: 401
> Authentication required
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[ https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu reassigned AMBARI-21821: Assignee: Qin Liu > Update Ambari Metrics service check to support HTTP SPNEGO authentication > - > > Key: AMBARI-21821 > URL: https://issues.apache.org/jira/browse/AMBARI-21821 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: trunk >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[ https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21821: - Component/s: ambari-metrics > Update Ambari Metrics service check to support HTTP SPNEGO authentication > - > > Key: AMBARI-21821 > URL: https://issues.apache.org/jira/browse/AMBARI-21821 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: trunk >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[ https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21821: - Fix Version/s: trunk > Update Ambari Metrics service check to support HTTP SPNEGO authentication > - > > Key: AMBARI-21821 > URL: https://issues.apache.org/jira/browse/AMBARI-21821 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: trunk >Reporter: Qin Liu > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[ https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21821: - Affects Version/s: trunk > Update Ambari Metrics service check to support HTTP SPNEGO authentication > - > > Key: AMBARI-21821 > URL: https://issues.apache.org/jira/browse/AMBARI-21821 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: trunk >Reporter: Qin Liu > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[ https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21821: - Summary: Update Ambari Metrics service check to support HTTP SPNEGO authentication (was: Update Ambari Metrics ) > Update Ambari Metrics service check to support HTTP SPNEGO authentication > - > > Key: AMBARI-21821 > URL: https://issues.apache.org/jira/browse/AMBARI-21821 > Project: Ambari > Issue Type: Bug >Reporter: Qin Liu > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21821) Update Ambari Metrics
Qin Liu created AMBARI-21821: Summary: Update Ambari Metrics Key: AMBARI-21821 URL: https://issues.apache.org/jira/browse/AMBARI-21821 Project: Ambari Issue Type: Bug Reporter: Qin Liu -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-17898) Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor
[ https://issues.apache.org/jira/browse/AMBARI-17898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136350#comment-16136350 ] Qin Liu commented on AMBARI-17898: -- Hi Eric, Hmmm, The patch passed all the unit test on July 5. Let me check. > Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor > - > > Key: AMBARI-17898 > URL: https://issues.apache.org/jira/browse/AMBARI-17898 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-17898-trunk_2.patch, AMBARI-17898_trunk_june.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Ambari Metrics Monitor, a client of Ambari Metrics Collector, currently does > not support Kerberos HTTP SPNEGO authentication. > /var/log/ambari-metrics-monitor/ambari-metrics-monitor.out: > 2015-12-15 13:26:30,663 [INFO] emitter.py:101 - server: > http://metrics-collector:6188/ws/v1/timeline/metrics > 2015-12-15 13:26:30,671 [WARNING] emitter.py:84 - Error sending metrics to > server. HTTP Error 401: Authentication required > 2015-12-15 13:26:30,671 [WARNING] emitter.py:90 - Retrying after 5 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-17898) Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor
[ https://issues.apache.org/jira/browse/AMBARI-17898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16136342#comment-16136342 ] Qin Liu commented on AMBARI-17898: -- Hi Eric, Thank you so much! > Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor > - > > Key: AMBARI-17898 > URL: https://issues.apache.org/jira/browse/AMBARI-17898 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-17898-trunk_2.patch, AMBARI-17898_trunk_june.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Ambari Metrics Monitor, a client of Ambari Metrics Collector, currently does > not support Kerberos HTTP SPNEGO authentication. > /var/log/ambari-metrics-monitor/ambari-metrics-monitor.out: > 2015-12-15 13:26:30,663 [INFO] emitter.py:101 - server: > http://metrics-collector:6188/ws/v1/timeline/metrics > 2015-12-15 13:26:30,671 [WARNING] emitter.py:84 - Error sending metrics to > server. HTTP Error 401: Authentication required > 2015-12-15 13:26:30,671 [WARNING] emitter.py:90 - Retrying after 5 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21470) Kafka Sink does not exclude excluded metrics of type 'guage'
[ https://issues.apache.org/jira/browse/AMBARI-21470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116799#comment-16116799 ] Qin Liu commented on AMBARI-21470: -- Hi Aravindan, Thanks for your help! > Kafka Sink does not exclude excluded metrics of type 'guage' > > > Key: AMBARI-21470 > URL: https://issues.apache.org/jira/browse/AMBARI-21470 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.5.2 > > Attachments: AMBARI-21470.patch > > > Preparing this patch on behalf of [~qinliu] who fixed the bug. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-17898) Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor
[ https://issues.apache.org/jira/browse/AMBARI-17898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-17898: - Attachment: AMBARI-17898_trunk_june.patch > Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor > - > > Key: AMBARI-17898 > URL: https://issues.apache.org/jira/browse/AMBARI-17898 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-17898-trunk_2.patch, AMBARI-17898_trunk_june.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Ambari Metrics Monitor, a client of Ambari Metrics Collector, currently does > not support Kerberos HTTP SPNEGO authentication. > /var/log/ambari-metrics-monitor/ambari-metrics-monitor.out: > 2015-12-15 13:26:30,663 [INFO] emitter.py:101 - server: > http://metrics-collector:6188/ws/v1/timeline/metrics > 2015-12-15 13:26:30,671 [WARNING] emitter.py:84 - Error sending metrics to > server. HTTP Error 401: Authentication required > 2015-12-15 13:26:30,671 [WARNING] emitter.py:90 - Retrying after 5 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-17898) Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor
[ https://issues.apache.org/jira/browse/AMBARI-17898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-17898: - Status: Patch Available (was: Open) > Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor > - > > Key: AMBARI-17898 > URL: https://issues.apache.org/jira/browse/AMBARI-17898 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-17898-trunk_2.patch, AMBARI-17898_trunk_june.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Ambari Metrics Monitor, a client of Ambari Metrics Collector, currently does > not support Kerberos HTTP SPNEGO authentication. > /var/log/ambari-metrics-monitor/ambari-metrics-monitor.out: > 2015-12-15 13:26:30,663 [INFO] emitter.py:101 - server: > http://metrics-collector:6188/ws/v1/timeline/metrics > 2015-12-15 13:26:30,671 [WARNING] emitter.py:84 - Error sending metrics to > server. HTTP Error 401: Authentication required > 2015-12-15 13:26:30,671 [WARNING] emitter.py:90 - Retrying after 5 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-17898) Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor
[ https://issues.apache.org/jira/browse/AMBARI-17898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-17898: - Attachment: (was: AMBARI-17898_trunk_june.patch) > Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor > - > > Key: AMBARI-17898 > URL: https://issues.apache.org/jira/browse/AMBARI-17898 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-17898-trunk_2.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Ambari Metrics Monitor, a client of Ambari Metrics Collector, currently does > not support Kerberos HTTP SPNEGO authentication. > /var/log/ambari-metrics-monitor/ambari-metrics-monitor.out: > 2015-12-15 13:26:30,663 [INFO] emitter.py:101 - server: > http://metrics-collector:6188/ws/v1/timeline/metrics > 2015-12-15 13:26:30,671 [WARNING] emitter.py:84 - Error sending metrics to > server. HTTP Error 401: Authentication required > 2015-12-15 13:26:30,671 [WARNING] emitter.py:90 - Retrying after 5 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-17898) Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor
[ https://issues.apache.org/jira/browse/AMBARI-17898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-17898: - Status: Open (was: Patch Available) > Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor > - > > Key: AMBARI-17898 > URL: https://issues.apache.org/jira/browse/AMBARI-17898 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-17898-trunk_2.patch, AMBARI-17898_trunk_june.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Ambari Metrics Monitor, a client of Ambari Metrics Collector, currently does > not support Kerberos HTTP SPNEGO authentication. > /var/log/ambari-metrics-monitor/ambari-metrics-monitor.out: > 2015-12-15 13:26:30,663 [INFO] emitter.py:101 - server: > http://metrics-collector:6188/ws/v1/timeline/metrics > 2015-12-15 13:26:30,671 [WARNING] emitter.py:84 - Error sending metrics to > server. HTTP Error 401: Authentication required > 2015-12-15 13:26:30,671 [WARNING] emitter.py:90 - Retrying after 5 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-17898) Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor
[ https://issues.apache.org/jira/browse/AMBARI-17898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-17898: - Status: Patch Available (was: Open) > Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor > - > > Key: AMBARI-17898 > URL: https://issues.apache.org/jira/browse/AMBARI-17898 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-17898-trunk_2.patch, AMBARI-17898_trunk_june.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Ambari Metrics Monitor, a client of Ambari Metrics Collector, currently does > not support Kerberos HTTP SPNEGO authentication. > /var/log/ambari-metrics-monitor/ambari-metrics-monitor.out: > 2015-12-15 13:26:30,663 [INFO] emitter.py:101 - server: > http://metrics-collector:6188/ws/v1/timeline/metrics > 2015-12-15 13:26:30,671 [WARNING] emitter.py:84 - Error sending metrics to > server. HTTP Error 401: Authentication required > 2015-12-15 13:26:30,671 [WARNING] emitter.py:90 - Retrying after 5 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-17898) Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor
[ https://issues.apache.org/jira/browse/AMBARI-17898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-17898: - Attachment: AMBARI-17898_trunk_june.patch > Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor > - > > Key: AMBARI-17898 > URL: https://issues.apache.org/jira/browse/AMBARI-17898 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-17898-trunk_2.patch, AMBARI-17898_trunk_june.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Ambari Metrics Monitor, a client of Ambari Metrics Collector, currently does > not support Kerberos HTTP SPNEGO authentication. > /var/log/ambari-metrics-monitor/ambari-metrics-monitor.out: > 2015-12-15 13:26:30,663 [INFO] emitter.py:101 - server: > http://metrics-collector:6188/ws/v1/timeline/metrics > 2015-12-15 13:26:30,671 [WARNING] emitter.py:84 - Error sending metrics to > server. HTTP Error 401: Authentication required > 2015-12-15 13:26:30,671 [WARNING] emitter.py:90 - Retrying after 5 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-17898) Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor
[ https://issues.apache.org/jira/browse/AMBARI-17898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-17898: - Status: Open (was: Patch Available) > Add Kerberos HTTP SPNEGO authentication support to Ambari Metrics Monitor > - > > Key: AMBARI-17898 > URL: https://issues.apache.org/jira/browse/AMBARI-17898 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-17898-trunk_2.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Ambari Metrics Monitor, a client of Ambari Metrics Collector, currently does > not support Kerberos HTTP SPNEGO authentication. > /var/log/ambari-metrics-monitor/ambari-metrics-monitor.out: > 2015-12-15 13:26:30,663 [INFO] emitter.py:101 - server: > http://metrics-collector:6188/ws/v1/timeline/metrics > 2015-12-15 13:26:30,671 [WARNING] emitter.py:84 - Error sending metrics to > server. HTTP Error 401: Authentication required > 2015-12-15 13:26:30,671 [WARNING] emitter.py:90 - Retrying after 5 ... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16054395#comment-16054395 ] Qin Liu commented on AMBARI-21230: -- [~rlevas] Thank you! > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: 3.0.0, 2.5.2 > > Attachments: AMBARI-21230.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., /var/log/accumulo/tserver_.debug.log: > 2017-06-06 23:07:39,918 [timeline.HadoopTimelineMetricsSink] INFO : Received > WWW-Authentication header:Negotiate, for URL: > http://:6188/ws/v1/timeline/metrics > 2017-06-06 23:07:39,927 [timeline.HadoopTimelineMetricsSink] INFO : No live > collector to send metrics to. Metrics to be sent will be discarded. This > message will be skipped for the next 20 times. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Resolution: Fixed Status: Resolved (was: Patch Available) > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: 3.0.0, 2.5.2 > > Attachments: AMBARI-21230.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., /var/log/accumulo/tserver_.debug.log: > 2017-06-06 23:07:39,918 [timeline.HadoopTimelineMetricsSink] INFO : Received > WWW-Authentication header:Negotiate, for URL: > http://:6188/ws/v1/timeline/metrics > 2017-06-06 23:07:39,927 [timeline.HadoopTimelineMetricsSink] INFO : No live > collector to send metrics to. Metrics to be sent will be discarded. This > message will be skipped for the next 20 times. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21250) update yarn-env.xml in HDP2.6 for YARN sinks' HTTP SPNEGO Authentication
[ https://issues.apache.org/jira/browse/AMBARI-21250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16054233#comment-16054233 ] Qin Liu commented on AMBARI-21250: -- [~dsen] Thank you! > update yarn-env.xml in HDP2.6 for YARN sinks' HTTP SPNEGO Authentication > > > Key: AMBARI-21250 > URL: https://issues.apache.org/jira/browse/AMBARI-21250 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-21250 > > > This is an appendum of AMBARI-19369 "Add Kerberos HTTP SPNEGO authentication > support to Hadoop/hbase/kafka/storm sinks". > yarn-env.xml in HDP2.6 needs to update to support Kerberos HTTP SPNEGO > authentication for YARN sinks because yarn-env.xml in HDP2.6 does not extends > the one in HDP2.5. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21250) update yarn-env.xml in HDP2.6 for YARN sinks' HTTP SPNEGO Authentication
[ https://issues.apache.org/jira/browse/AMBARI-21250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21250: - Status: Patch Available (was: Open) > update yarn-env.xml in HDP2.6 for YARN sinks' HTTP SPNEGO Authentication > > > Key: AMBARI-21250 > URL: https://issues.apache.org/jira/browse/AMBARI-21250 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-21250 > > > This is an appendum of AMBARI-19369 "Add Kerberos HTTP SPNEGO authentication > support to Hadoop/hbase/kafka/storm sinks". > yarn-env.xml in HDP2.6 needs to update to support Kerberos HTTP SPNEGO > authentication for YARN sinks because yarn-env.xml in HDP2.6 does not extends > the one in HDP2.5. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21250) update yarn-env.xml in HDP2.6 for YARN sinks' HTTP SPNEGO Authentication
[ https://issues.apache.org/jira/browse/AMBARI-21250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21250: - Attachment: AMBARI-21250 > update yarn-env.xml in HDP2.6 for YARN sinks' HTTP SPNEGO Authentication > > > Key: AMBARI-21250 > URL: https://issues.apache.org/jira/browse/AMBARI-21250 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-21250 > > > This is an appendum of AMBARI-19369 "Add Kerberos HTTP SPNEGO authentication > support to Hadoop/hbase/kafka/storm sinks". > yarn-env.xml in HDP2.6 needs to update to support Kerberos HTTP SPNEGO > authentication for YARN sinks because yarn-env.xml in HDP2.6 does not extends > the one in HDP2.5. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21250) update yarn-env.xml in HDP2.6 for YARN sinks' HTTP SPNEGO Authentication
[ https://issues.apache.org/jira/browse/AMBARI-21250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21250: - Description: This is an appendum of AMBARI-19369 "Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks". yarn-env.xml in HDP2.6 needs to update to support Kerberos HTTP SPNEGO authentication for YARN sinks because yarn-env.xml in HDP2.6 does not extends the one in HDP2.5. > update yarn-env.xml in HDP2.6 for YARN sinks' HTTP SPNEGO Authentication > > > Key: AMBARI-21250 > URL: https://issues.apache.org/jira/browse/AMBARI-21250 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > > This is an appendum of AMBARI-19369 "Add Kerberos HTTP SPNEGO authentication > support to Hadoop/hbase/kafka/storm sinks". > yarn-env.xml in HDP2.6 needs to update to support Kerberos HTTP SPNEGO > authentication for YARN sinks because yarn-env.xml in HDP2.6 does not extends > the one in HDP2.5. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21250) update yarn-env.xml in HDP2.6 for YARN sinks' HTTP SPNEGO Authentication
[ https://issues.apache.org/jira/browse/AMBARI-21250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21250: - Issue Type: Task (was: Bug) > update yarn-env.xml in HDP2.6 for YARN sinks' HTTP SPNEGO Authentication > > > Key: AMBARI-21250 > URL: https://issues.apache.org/jira/browse/AMBARI-21250 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21250) update yarn-env.xml in HDP2.6 for YARN sinks' HTTP SPNEGO Authentication
Qin Liu created AMBARI-21250: Summary: update yarn-env.xml in HDP2.6 for YARN sinks' HTTP SPNEGO Authentication Key: AMBARI-21250 URL: https://issues.apache.org/jira/browse/AMBARI-21250 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Qin Liu Assignee: Qin Liu Fix For: trunk -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Description: This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to authenticate". In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But Accumulo sinks, clients of Ambari Metrics Collector, currently do not support Kerberos HTTP SPNEGO authentication. e.g., /var/log/accumulo/tserver_.debug.log: 2017-06-06 23:07:39,918 [timeline.HadoopTimelineMetricsSink] INFO : Received WWW-Authentication header:Negotiate, for URL: http://:6188/ws/v1/timeline/metrics 2017-06-06 23:07:39,927 [timeline.HadoopTimelineMetricsSink] INFO : No live collector to send metrics to. Metrics to be sent will be discarded. This message will be skipped for the next 20 times. was: This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to authenticate". In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But Accumulo sinks, clients of Ambari Metrics Collector, currently do not support Kerberos HTTP SPNEGO authentication. e.g., /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, statusCode = 401 > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-21230.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., /var/log/accumulo/tserver_.debug.log: > 2017-06-06 23:07:39,918 [timeline.HadoopTimelineMetricsSink] INFO : Received > WWW-Authentication header:Negotiate, for URL: > http://:6188/ws/v1/timeline/metrics > 2017-06-06 23:07:39,927 [timeline.HadoopTimelineMetricsSink] INFO : No live > collector to send metrics to. Metrics to be sent will be discarded. This > message will be skipped for the next 20 times. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Status: Patch Available (was: Open) > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-21230.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Attachment: (was: AMBARI-21230.patch) > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-21230.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Attachment: AMBARI-21230.patch > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-21230.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Status: Open (was: Patch Available) > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-21230.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Status: Open (was: Patch Available) > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-21230.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Attachment: AMBARI-21230.patch > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-21230.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Attachment: (was: AMBARI-21230.patch) > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-21230.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Status: Patch Available (was: Open) > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-21230.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Status: Patch Available (was: Open) > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-21230.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Attachment: AMBARI-21230.patch > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-21230.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Status: Open (was: Patch Available) > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Attachment: (was: AMBARI-21230.patch) > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Status: Patch Available (was: In Progress) > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-21230.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
[ https://issues.apache.org/jira/browse/AMBARI-21230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21230: - Attachment: AMBARI-21230.patch > Add Kerberos HTTP SPNEGO authentication support to Accumulo > --- > > Key: AMBARI-21230 > URL: https://issues.apache.org/jira/browse/AMBARI-21230 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.5.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-21230.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Accumulo sinks, clients of Ambari Metrics Collector, currently do not support > Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21230) Add Kerberos HTTP SPNEGO authentication support to Accumulo
Qin Liu created AMBARI-21230: Summary: Add Kerberos HTTP SPNEGO authentication support to Accumulo Key: AMBARI-21230 URL: https://issues.apache.org/jira/browse/AMBARI-21230 Project: Ambari Issue Type: Improvement Components: ambari-metrics, ambari-server Affects Versions: 2.5.0 Reporter: Qin Liu Assignee: Qin Liu Fix For: trunk This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to authenticate". In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But Accumulo sinks, clients of Ambari Metrics Collector, currently do not support Kerberos HTTP SPNEGO authentication. e.g., /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[ https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-19369: - Resolution: Fixed Status: Resolved (was: Patch Available) > Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm > sinks > - > > Key: AMBARI-19369 > URL: https://issues.apache.org/jira/browse/AMBARI-19369 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: 3.0.0, 2.5.2 > > Attachments: AMBARI-19369_branch-2.5.patch, AMBARI-19369.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector, > currently do not support Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[ https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043996#comment-16043996 ] Qin Liu commented on AMBARI-19369: -- [~rlevas] Hi Robert, the patch for branch-2.5 is attached. > Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm > sinks > - > > Key: AMBARI-19369 > URL: https://issues.apache.org/jira/browse/AMBARI-19369 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: 3.0.0, 2.5.2 > > Attachments: AMBARI-19369_branch-2.5.patch, AMBARI-19369.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector, > currently do not support Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[ https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-19369: - Attachment: AMBARI-19369_branch-2.5.patch > Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm > sinks > - > > Key: AMBARI-19369 > URL: https://issues.apache.org/jira/browse/AMBARI-19369 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: 3.0.0, 2.5.2 > > Attachments: AMBARI-19369_branch-2.5.patch, AMBARI-19369.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector, > currently do not support Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[ https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-19369: - Sure, will do it. > Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm > sinks > - > > Key: AMBARI-19369 > URL: https://issues.apache.org/jira/browse/AMBARI-19369 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: 3.0.0, 2.5.2 > > Attachments: AMBARI-19369.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector, > currently do not support Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[ https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043102#comment-16043102 ] Qin Liu commented on AMBARI-19369: -- Hi Robert, The patch is for trunk. I think it should go in Ambari 2.5.2 as well. > Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm > sinks > - > > Key: AMBARI-19369 > URL: https://issues.apache.org/jira/browse/AMBARI-19369 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-19369.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector, > currently do not support Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[ https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16033431#comment-16033431 ] Qin Liu commented on AMBARI-19369: -- The failure does not seem to relate to the patch. > Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm > sinks > - > > Key: AMBARI-19369 > URL: https://issues.apache.org/jira/browse/AMBARI-19369 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-19369.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector, > currently do not support Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[ https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-19369: - Attachment: AMBARI-19369.patch > Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm > sinks > - > > Key: AMBARI-19369 > URL: https://issues.apache.org/jira/browse/AMBARI-19369 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-19369.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector, > currently do not support Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[ https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-19369: - Status: Patch Available (was: Open) > Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm > sinks > - > > Key: AMBARI-19369 > URL: https://issues.apache.org/jira/browse/AMBARI-19369 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-19369.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector, > currently do not support Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[ https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-19369: - Status: Open (was: Patch Available) > Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm > sinks > - > > Key: AMBARI-19369 > URL: https://issues.apache.org/jira/browse/AMBARI-19369 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-19369.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector, > currently do not support Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[ https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-19369: - Status: Patch Available (was: Open) > Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm > sinks > - > > Key: AMBARI-19369 > URL: https://issues.apache.org/jira/browse/AMBARI-19369 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-19369.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector, > currently do not support Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[ https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-19369: - Attachment: AMBARI-19369.patch > Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm > sinks > - > > Key: AMBARI-19369 > URL: https://issues.apache.org/jira/browse/AMBARI-19369 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-19369.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector, > currently do not support Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[ https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-19369: - Attachment: (was: AMBARI-19369.patch) > Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm > sinks > - > > Key: AMBARI-19369 > URL: https://issues.apache.org/jira/browse/AMBARI-19369 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector, > currently do not support Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[ https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-19369: - Status: Open (was: Patch Available) > Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm > sinks > - > > Key: AMBARI-19369 > URL: https://issues.apache.org/jira/browse/AMBARI-19369 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector, > currently do not support Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[ https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-19369: - Status: Patch Available (was: Open) > Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm > sinks > - > > Key: AMBARI-19369 > URL: https://issues.apache.org/jira/browse/AMBARI-19369 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-19369.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector, > currently do not support Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[ https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-19369: - Attachment: AMBARI-19369.patch > Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm > sinks > - > > Key: AMBARI-19369 > URL: https://issues.apache.org/jira/browse/AMBARI-19369 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-19369.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector, > currently do not support Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[ https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-19369: - Status: Open (was: Patch Available) > Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm > sinks > - > > Key: AMBARI-19369 > URL: https://issues.apache.org/jira/browse/AMBARI-19369 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector, > currently do not support Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[ https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-19369: - Attachment: (was: AMBARI-19369.patch) > Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm > sinks > - > > Key: AMBARI-19369 > URL: https://issues.apache.org/jira/browse/AMBARI-19369 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector, > currently do not support Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[ https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-19369: - Status: Patch Available (was: Open) > Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm > sinks > - > > Key: AMBARI-19369 > URL: https://issues.apache.org/jira/browse/AMBARI-19369 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-19369.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector, > currently do not support Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[ https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-19369: - Attachment: AMBARI-19369.patch > Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm > sinks > - > > Key: AMBARI-19369 > URL: https://issues.apache.org/jira/browse/AMBARI-19369 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-19369.patch > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector, > currently do not support Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[ https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-19369: - Attachment: (was: AMBARI-19369.patch) > Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm > sinks > - > > Key: AMBARI-19369 > URL: https://issues.apache.org/jira/browse/AMBARI-19369 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector, > currently do not support Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19369) Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm sinks
[ https://issues.apache.org/jira/browse/AMBARI-19369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-19369: - Status: Open (was: Patch Available) > Add Kerberos HTTP SPNEGO authentication support to Hadoop/hbase/kafka/storm > sinks > - > > Key: AMBARI-19369 > URL: https://issues.apache.org/jira/browse/AMBARI-19369 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics, ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > > This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to > authenticate". > In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari > Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But > Hadoop/hbase/kafka/storm sinks, clients of Ambari Metrics Collector, > currently do not support Kerberos HTTP SPNEGO authentication. > e.g., > /var/log/hadoop-yarn/yarn/yarn-yarn-timelineserver-.log: > 2016-12-16 22:25:29,471 INFO timeline.HadoopTimelineMetricsSink > (AbstractTimelineMetricsSink.java:emitMetricsJson(169)) - Unable to POST > metrics to collector, http://metrics-collector:6188/ws/v1/timeline/metrics, > statusCode = 401 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Status: Patch Available (was: Open) > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20726.patch > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK" - "CRIT" is > expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT" - "OK" is > expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Attachment: AMBARI-20726.patch submit it again > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20726.patch > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK" - "CRIT" is > expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT" - "OK" is > expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Attachment: AMBARI-20726.patch > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK" - "CRIT" is > expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT" - "OK" is > expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Attachment: (was: AMBARI-20726.patch) > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK" - "CRIT" is > expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT" - "OK" is > expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Attachment: (was: AMBARI-20726.patch) > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK" - "CRIT" is > expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT" - "OK" is > expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Status: Open (was: Patch Available) > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20726.patch > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK" - "CRIT" is > expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT" - "OK" is > expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15988095#comment-15988095 ] Qin Liu commented on AMBARI-20726: -- need to mention that the results of testing has nothing to do with my patch because the following job also failed in the same way: https://builds.apache.org/job/Ambari-trunk-test-patch/11523/artifact/patch-work/trunkJavacWarnings.txt > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20726.patch > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK" - "CRIT" is > expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT" - "OK" is > expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Status: Patch Available (was: Open) > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20726.patch > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK" - "CRIT" is > expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT" - "OK" is > expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Attachment: (was: AMBARI-20726.patch) > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20726.patch > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK" - "CRIT" is > expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT" - "OK" is > expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Attachment: AMBARI-20726.patch > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20726.patch > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK" - "CRIT" is > expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT" - "OK" is > expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Status: Open (was: Patch Available) > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20726.patch > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK" - "CRIT" is > expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT" - "OK" is > expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Status: Patch Available (was: Open) > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20726.patch > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK" - "CRIT" is > expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT" - "OK" is > expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Attachment: AMBARI-20726.patch > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20726.patch > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK" - "CRIT" is > expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT" - "OK" is > expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Status: Open (was: Patch Available) > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK" - "CRIT" is > expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT" - "OK" is > expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Attachment: (was: AMBARI-20726.patch) > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK" - "CRIT" is > expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT" - "OK" is > expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Status: Patch Available (was: Open) > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20726.patch > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK" - "CRIT" is > expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT" - "OK" is > expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Attachment: (was: AMBARI-20726.patch) > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20726.patch > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK" - "CRIT" is > expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT" - "OK" is > expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Attachment: AMBARI-20726.patch > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20726.patch > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK" - "CRIT" is > expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT" - "OK" is > expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Status: Open (was: Patch Available) > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20726.patch > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK" - "CRIT" is > expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT" - "OK" is > expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15969346#comment-15969346 ] Qin Liu commented on AMBARI-20726: -- @jhurley and @jluniya Hi Jonathan and Jayush, Could you please help to review the code changes? Thank you very much! > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20726.patch > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK" - "CRIT" is > expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT" - "OK" is > expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Description: Aggregate alert does not show status properly at Maintenance Mode change. Steps to reproduce: Install a cluster that has HBase with one regionserver installed. Scenario 1: 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host or on the HBase service. 2. Stop the RegionServer after that. 3. No red alerts will show as expected. Percent RegionServers Available - OK affected: [0], total: [1] 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. But Percent RegionServers Available alert will still show "OK" - "CRIT" is expected. Scenario 2: 1) Stop the RegionServer - Red alert will show as expected. Percent RegionServers Available - CRIT affected: [1], total: [1] 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be gone as expected. But Percent RegionServers Available alert will still show "CRIT" - "OK" is expected. was: Aggregate alert does not show status properly at Maintenance Mode change. Steps to reproduce: Install a cluster that has HBase with one regionserver installed. Scenario 1: 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host or on the HBase service. 2. Stop the RegionServer after that. 3. No red alerts will show as expected. Percent RegionServers Available - OK affected: [0], total: [1] 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. But Percent RegionServers Available alert will still show "OK". Scenario 2: 1) Stop the RegionServer - Red alert will show as expected. Percent RegionServers Available - CRIT affected: [1], total: [1] 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be gone as expected. But Percent RegionServers Available alert will still show "CRIT". Scenario 2: 1) Stopped one RegionServer - Red alert seen as expected Percent RegionServers Available - CRIT affected: [1], total: [1] 2) Now Turned On Maintenance Mode - For RegionServer status, Red alert gone as expected. But Percent RegionServers Available alert showing "CRIT". > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20726.patch > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK" - "CRIT" is > expected. > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT" - "OK" is > expected. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Description: Aggregate alert does not show status properly at Maintenance Mode change. Steps to reproduce: Install a cluster that has HBase with one regionserver installed. Scenario 1: 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host or on the HBase service. 2. Stop the RegionServer after that. 3. No red alerts will show as expected. Percent RegionServers Available - OK affected: [0], total: [1] 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. But Percent RegionServers Available alert will still show "OK". Scenario 2: 1) Stop the RegionServer - Red alert will show as expected. Percent RegionServers Available - CRIT affected: [1], total: [1] 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be gone as expected. But Percent RegionServers Available alert will still show "CRIT". Scenario 2: 1) Stopped one RegionServer - Red alert seen as expected Percent RegionServers Available - CRIT affected: [1], total: [1] 2) Now Turned On Maintenance Mode - For RegionServer status, Red alert gone as expected. But Percent RegionServers Available alert showing "CRIT". was: Aggregate alert does not show status properly at Maintenance Mode change. Steps to reproduce: Install a cluster that has HBase with one regionserver installed. Scenario 1: 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host or on the HBase service. 2. Stop the RegionServer after that. 3. No red alerts will show as expected. Percent RegionServers Available - OK affected: [0], total: [1] 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. But Percent RegionServers Available alert will still show "OK". Scenario 2: 1) Stop the RegionServer - Red alert will show as expected. Percent RegionServers Available - CRIT affected: [1], total: [1] 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be gone as expected. But Percent RegionServers Available alert will still show "CRIT". Scenario 2: 1) Stopped one RegionServer - Red alert seen as expected Percent RegionServers Available - CRIT affected: [1], total: [1] 2) Now Turned On Maintenance Mode - For RegionServer status, Red alert gone as expected But Percent RegionServers Available alert showing "CRIT" > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20726.patch > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK". > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT". > Scenario 2: > 1) Stopped one RegionServer - Red alert seen as expected > Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turned On Maintenance Mode - For RegionServer status, Red alert gone > as expected. > But Percent RegionServers Available alert showing "CRIT". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Description: Aggregate alert does not show status properly at Maintenance Mode change. Steps to reproduce: Install a cluster that has HBase with one regionserver installed. Scenario 1: 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host or on the HBase service. 2. Stop the RegionServer after that. 3. No red alerts will show as expected. Percent RegionServers Available - OK affected: [0], total: [1] 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. But Percent RegionServers Available alert will still show "OK". Scenario 2: 1) Stop the RegionServer - Red alert will show as expected. Percent RegionServers Available - CRIT affected: [1], total: [1] 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be gone as expected. But Percent RegionServers Available alert will still show "CRIT". Scenario 2: 1) Stopped one RegionServer - Red alert seen as expected Percent RegionServers Available - CRIT affected: [1], total: [1] 2) Now Turned On Maintenance Mode - For RegionServer status, Red alert gone as expected But Percent RegionServers Available alert showing "CRIT" was: Aggregate alert does not show status properly after Maintenance Mode change. Steps to reproduce: install a cluster that has HBase with 1 regionserver installed Scenario 1 1. Turn On Maintenance Mode on one RegionServer or on the RegionServer host or on HBase service 2. Stop the RegionServer after that 3. No red alerts came as expected. Percent RegionServers Available - OK affected: [0], total: [1] 4. Now Turned Off Maintenance Mode, still kept the Region Server down. But Percent RegionServers Available alert still showing "OK" Scenario 2: 1) Stopped one RegionServer - Red alert seen as expected Percent RegionServers Available - CRIT affected: [1], total: [1] 2) Now Turned On Maintenance Mode - For RegionServer status, Red alert gone as expected But Percent RegionServers Available alert showing "CRIT" > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20726.patch > > > Aggregate alert does not show status properly at Maintenance Mode change. > Steps to reproduce: > Install a cluster that has HBase with one regionserver installed. > Scenario 1: > 1. Turn On Maintenance Mode on the RegionServer or on the RegionServer host > or on the HBase service. > 2. Stop the RegionServer after that. > 3. No red alerts will show as expected. >Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turn Off Maintenance Mode, still keep the RegionServer down. >But Percent RegionServers Available alert will still show "OK". > Scenario 2: > 1) Stop the RegionServer - Red alert will show as expected. >Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turn On Maintenance Mode - For RegionServer status, Red alert will be > gone as expected. >But Percent RegionServers Available alert will still show "CRIT". > Scenario 2: > 1) Stopped one RegionServer - Red alert seen as expected > Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turned On Maintenance Mode - For RegionServer status, Red alert gone > as expected > But Percent RegionServers Available alert showing "CRIT" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly at Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Summary: Aggregate alert does not show status properly at Maintenance Mode change (was: Aggregate alert does not show status properly after Maintenance Mode change) > Aggregate alert does not show status properly at Maintenance Mode change > > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20726.patch > > > Aggregate alert does not show status properly after Maintenance Mode change. > Steps to reproduce: > install a cluster that has HBase with 1 regionserver installed > Scenario 1 > 1. Turn On Maintenance Mode on one RegionServer or on the RegionServer host > or on HBase service > 2. Stop the RegionServer after that > 3. No red alerts came as expected. > Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turned Off Maintenance Mode, still kept the Region Server down. > But Percent RegionServers Available alert still showing "OK" > Scenario 2: > 1) Stopped one RegionServer - Red alert seen as expected > Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turned On Maintenance Mode - For RegionServer status, Red alert gone > as expected > But Percent RegionServers Available alert showing "CRIT" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly after Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Status: Patch Available (was: Open) > Aggregate alert does not show status properly after Maintenance Mode change > --- > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20726.patch > > > Aggregate alert does not show status properly after Maintenance Mode change. > Steps to reproduce: > install a cluster that has HBase with 1 regionserver installed > Scenario 1 > 1. Turn On Maintenance Mode on one RegionServer or on the RegionServer host > or on HBase service > 2. Stop the RegionServer after that > 3. No red alerts came as expected. > Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turned Off Maintenance Mode, still kept the Region Server down. > But Percent RegionServers Available alert still showing "OK" > Scenario 2: > 1) Stopped one RegionServer - Red alert seen as expected > Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turned On Maintenance Mode - For RegionServer status, Red alert gone > as expected > But Percent RegionServers Available alert showing "CRIT" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly after Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Attachment: AMBARI-20726.patch > Aggregate alert does not show status properly after Maintenance Mode change > --- > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-20726.patch > > > Aggregate alert does not show status properly after Maintenance Mode change. > Steps to reproduce: > install a cluster that has HBase with 1 regionserver installed > Scenario 1 > 1. Turn On Maintenance Mode on one RegionServer or on the RegionServer host > or on HBase service > 2. Stop the RegionServer after that > 3. No red alerts came as expected. > Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turned Off Maintenance Mode, still kept the Region Server down. > But Percent RegionServers Available alert still showing "OK" > Scenario 2: > 1) Stopped one RegionServer - Red alert seen as expected > Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turned On Maintenance Mode - For RegionServer status, Red alert gone > as expected > But Percent RegionServers Available alert showing "CRIT" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20726) Aggregate alert does not show status properly after Maintenance Mode change
[ https://issues.apache.org/jira/browse/AMBARI-20726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-20726: - Description: Aggregate alert does not show status properly after Maintenance Mode change. Steps to reproduce: install a cluster that has HBase with 1 regionserver installed Scenario 1 1. Turn On Maintenance Mode on one RegionServer or on the RegionServer host or on HBase service 2. Stop the RegionServer after that 3. No red alerts came as expected. Percent RegionServers Available - OK affected: [0], total: [1] 4. Now Turned Off Maintenance Mode, still kept the Region Server down. But Percent RegionServers Available alert still showing "OK" Scenario 2: 1) Stopped one RegionServer - Red alert seen as expected Percent RegionServers Available - CRIT affected: [1], total: [1] 2) Now Turned On Maintenance Mode - For RegionServer status, Red alert gone as expected But Percent RegionServers Available alert showing "CRIT" was: Availability alert does not show status properly after Maintenance Mode change. Steps to reproduce: install a cluster that has HBase with 1 regionserver installed Scenario 1 1. Turn On Maintenance Mode on one RegionServer or on the RegionServer host or on HBase service 2. Stop the RegionServer after that 3. No red alerts came as expected. Percent RegionServers Available - OK affected: [0], total: [1] 4. Now Turned Off Maintenance Mode, still kept the Region Server down. But Percent RegionServers Available alert still showing "OK" Scenario 2: 1) Stopped one RegionServer - Red alert seen as expected Percent RegionServers Available - CRIT affected: [1], total: [1] 2) Now Turned On Maintenance Mode - For RegionServer status, Red alert gone as expected But Percent RegionServers Available alert showing "CRIT" > Aggregate alert does not show status properly after Maintenance Mode change > --- > > Key: AMBARI-20726 > URL: https://issues.apache.org/jira/browse/AMBARI-20726 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.4.2 >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > > Aggregate alert does not show status properly after Maintenance Mode change. > Steps to reproduce: > install a cluster that has HBase with 1 regionserver installed > Scenario 1 > 1. Turn On Maintenance Mode on one RegionServer or on the RegionServer host > or on HBase service > 2. Stop the RegionServer after that > 3. No red alerts came as expected. > Percent RegionServers Available - OK affected: [0], total: [1] > 4. Now Turned Off Maintenance Mode, still kept the Region Server down. > But Percent RegionServers Available alert still showing "OK" > Scenario 2: > 1) Stopped one RegionServer - Red alert seen as expected > Percent RegionServers Available - CRIT affected: [1], total: [1] > 2) Now Turned On Maintenance Mode - For RegionServer status, Red alert gone > as expected > But Percent RegionServers Available alert showing "CRIT" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
