[jira] [Updated] (AMBARI-22656) Add slot info for Hosts page
[ https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mathildaMa09 updated AMBARI-22656: -- Attachment: AMBARI-22656_branch-2.5.patch > Add slot info for Hosts page > > > Key: AMBARI-22656 > URL: https://issues.apache.org/jira/browse/AMBARI-22656 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, ambari-server, ambari-web >Affects Versions: 2.5.2 >Reporter: mathildaMa09 > Fix For: 2.5.2 > > Attachments: AMBARI-22656.patch, AMBARI-22656_branch-2.5.patch > > > In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I > need more details about my hosts’ physical position, like slot for instance, > to know exactly where my machine locates. So, in hosts page, we can add slot > info to describe their location. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22656) Add slot info for Hosts page
[ https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mathildaMa09 updated AMBARI-22656: -- Attachment: (was: AMBARI-22656_branch-2.5.patch) > Add slot info for Hosts page > > > Key: AMBARI-22656 > URL: https://issues.apache.org/jira/browse/AMBARI-22656 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, ambari-server, ambari-web >Affects Versions: 2.5.2 >Reporter: mathildaMa09 > Fix For: 2.5.2 > > Attachments: AMBARI-22656.patch, AMBARI-22656_branch-2.5.patch > > > In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I > need more details about my hosts’ physical position, like slot for instance, > to know exactly where my machine locates. So, in hosts page, we can add slot > info to describe their location. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22656) Add slot info for Hosts page
[ https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mathildaMa09 updated AMBARI-22656: -- Attachment: AMBARI-22656.patch > Add slot info for Hosts page > > > Key: AMBARI-22656 > URL: https://issues.apache.org/jira/browse/AMBARI-22656 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, ambari-server, ambari-web >Affects Versions: 2.5.2 >Reporter: mathildaMa09 > Fix For: 2.5.2 > > Attachments: AMBARI-22656.patch, AMBARI-22656_branch-2.5.patch > > > In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I > need more details about my hosts’ physical position, like slot for instance, > to know exactly where my machine locates. So, in hosts page, we can add slot > info to describe their location. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22656) Add slot info for Hosts page
[ https://issues.apache.org/jira/browse/AMBARI-22656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mathildaMa09 updated AMBARI-22656: -- Attachment: (was: AMBARI-22656.patch) > Add slot info for Hosts page > > > Key: AMBARI-22656 > URL: https://issues.apache.org/jira/browse/AMBARI-22656 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, ambari-server, ambari-web >Affects Versions: 2.5.2 >Reporter: mathildaMa09 > Fix For: 2.5.2 > > Attachments: AMBARI-22656.patch, AMBARI-22656_branch-2.5.patch > > > In Hosts Page lists info about hosts like Rack、IP、Cores、DiskUsage .etc, but I > need more details about my hosts’ physical position, like slot for instance, > to know exactly where my machine locates. So, in hosts page, we can add slot > info to describe their location. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22708) Ranger HDFS logging health Ambari Alert
David F. Quiroga created AMBARI-22708: - Summary: Ranger HDFS logging health Ambari Alert Key: AMBARI-22708 URL: https://issues.apache.org/jira/browse/AMBARI-22708 Project: Ambari Issue Type: New Feature Components: alerts Environment: HDP 2.5.3.0 Reporter: David F. Quiroga Priority: Trivial Attachments: alert_ranger_hdfs_logging.json, alert_ranger_knox_logging.json, alert_ranger_logging.py First some background: We were directed to retain audit/access records "forever" (technically 7 years but that is basically forever in electronic log time). Each Hadoop component generates local audit logs as per their log4j settings. In our production system these logs would frequently fill up the disk. At first we would just compress them in place but that only works for so long and there was no redundancy with local disk storage. In others words, no long term plan. We started to discuss moving them to HDFS or a different storage solution. One of our team members pointed out the Ranger plugins are already logging the "same data" into HDFS. Probably after several meeting with the higher-ups, using Ranger logs as the record truth was approved. Components log4j settings were updated to purge data automatically. Purging local logs felt like operating with out a safety net. Thought it we be good to check that Ranger was successful logging to HDFS each day. Should mention this is a kerberized cluster, not that anything ever goes wrong with kerberos. *Checking this would have certainly been possible with a shell script, but we have been pushing to centralize warning/alerts in Ambari. And so an Ambari alert python script to check on Ranger Logging Health was crafted. * For the most part the alert was modeled after some of the hive alerts. At the moment it just checks that the daily /ranger/audit/ HDFS directory has been created. I am attaching the host script and the alert.json for HDFS and Knox components. In the alert.json, service_name and component_name should be set to local values. Everything else should "work out of the box". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22707) Implement resolving dependencies for each service
Vitaly Brodetskyi created AMBARI-22707: -- Summary: Implement resolving dependencies for each service Key: AMBARI-22707 URL: https://issues.apache.org/jira/browse/AMBARI-22707 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Vitaly Brodetskyi Assignee: Vitaly Brodetskyi Priority: Critical Fix For: 3.0.0 Resolve dependencies for services. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22706) Ranger installation fails
[ https://issues.apache.org/jira/browse/AMBARI-22706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22706: - Attachment: AMBARI-22706.patch > Ranger installation fails > - > > Key: AMBARI-22706 > URL: https://issues.apache.org/jira/browse/AMBARI-22706 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-22706.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22706) Ranger installation fails
Andrew Onischuk created AMBARI-22706: Summary: Ranger installation fails Key: AMBARI-22706 URL: https://issues.apache.org/jira/browse/AMBARI-22706 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22706) Ranger installation fails
[ https://issues.apache.org/jira/browse/AMBARI-22706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22706: - Status: Patch Available (was: Open) > Ranger installation fails > - > > Key: AMBARI-22706 > URL: https://issues.apache.org/jira/browse/AMBARI-22706 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-22706.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22704) Stack unit test fixes
[ https://issues.apache.org/jira/browse/AMBARI-22704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305406#comment-16305406 ] Andrew Onischuk commented on AMBARI-22704: -- Committed to branch-3.0-perf > Stack unit test fixes > - > > Key: AMBARI-22704 > URL: https://issues.apache.org/jira/browse/AMBARI-22704 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-22704.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22704) Stack unit test fixes
[ https://issues.apache.org/jira/browse/AMBARI-22704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305393#comment-16305393 ] Vitaly Brodetskyi commented on AMBARI-22704: LGTM +1 > Stack unit test fixes > - > > Key: AMBARI-22704 > URL: https://issues.apache.org/jira/browse/AMBARI-22704 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-22704.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22704) Stack unit test fixes
[ https://issues.apache.org/jira/browse/AMBARI-22704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305363#comment-16305363 ] Andrew Onischuk commented on AMBARI-22704: -- Cannot create reviewboard. Can somebody +1 here? > Stack unit test fixes > - > > Key: AMBARI-22704 > URL: https://issues.apache.org/jira/browse/AMBARI-22704 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-22704.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22705) Ambari 2.6.1 installation
NNN created AMBARI-22705:
Summary: Ambari 2.6.1 installation
Key: AMBARI-22705
URL: https://issues.apache.org/jira/browse/AMBARI-22705
Project: Ambari
Issue Type: Bug
Reporter: NNN
Files:
* ambari-funtest/pom.xml
* ambari-metrics/ambari-metrics-grafana/pom.xml
* ambari-logsearch/pom.xml
did not have the 'control' path in and adding the following
solves:
org.vafer
jdeb
1.0.1
stub-execution
none
jdeb
true
false
false
${project.basedir}/../src/main/package/deb/control
when building with:
sudo mvn -B clean package jdeb:jdeb
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22698) Custom zeppelin interpreter properties are getting removed after moving zeppelin to a different host
[ https://issues.apache.org/jira/browse/AMBARI-22698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-22698: - Status: Patch Available (was: In Progress) > Custom zeppelin interpreter properties are getting removed after moving > zeppelin to a different host > > > Key: AMBARI-22698 > URL: https://issues.apache.org/jira/browse/AMBARI-22698 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.6.1 > Environment: ambari-server --version 2.6.1.0-136 > HDP-2.6.4.0-85 >Reporter: Supreeth Sharma >Assignee: Prabhjyot Singh >Priority: Blocker > Attachments: AMBARI-22698_trunk_v1.patch > > > Custom zeppelin interpreter properties are getting lost after moving zeppelin > to a different host > Live Cluster : https://172.27.12.130:8443 > Steps to reproduce : > 1) Modify interpreter settings > a) Add new custom properties > b) Modify existing properties > Changes are getting saved in HDFS path /user/zeppelin/conf/interpreter.json > and they are getting synced to local path /etc/zeppelin/conf/interpreter.json > after zeppelin restart. > 2) Delete zeppelin server > 3) Install zeppelin server on a different host > 4) Modifications done in step 1 are lost. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22698) Custom zeppelin interpreter properties are getting removed after moving zeppelin to a different host
[ https://issues.apache.org/jira/browse/AMBARI-22698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-22698: - Attachment: AMBARI-22698_trunk_v1.patch > Custom zeppelin interpreter properties are getting removed after moving > zeppelin to a different host > > > Key: AMBARI-22698 > URL: https://issues.apache.org/jira/browse/AMBARI-22698 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.6.1 > Environment: ambari-server --version 2.6.1.0-136 > HDP-2.6.4.0-85 >Reporter: Supreeth Sharma >Assignee: Prabhjyot Singh >Priority: Blocker > Attachments: AMBARI-22698_trunk_v1.patch > > > Custom zeppelin interpreter properties are getting lost after moving zeppelin > to a different host > Live Cluster : https://172.27.12.130:8443 > Steps to reproduce : > 1) Modify interpreter settings > a) Add new custom properties > b) Modify existing properties > Changes are getting saved in HDFS path /user/zeppelin/conf/interpreter.json > and they are getting synced to local path /etc/zeppelin/conf/interpreter.json > after zeppelin restart. > 2) Delete zeppelin server > 3) Install zeppelin server on a different host > 4) Modifications done in step 1 are lost. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22698) Custom zeppelin interpreter properties are getting removed after moving zeppelin to a different host
[ https://issues.apache.org/jira/browse/AMBARI-22698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-22698: - Fix Version/s: (was: 2.6.1) > Custom zeppelin interpreter properties are getting removed after moving > zeppelin to a different host > > > Key: AMBARI-22698 > URL: https://issues.apache.org/jira/browse/AMBARI-22698 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.6.1 > Environment: ambari-server --version 2.6.1.0-136 > HDP-2.6.4.0-85 >Reporter: Supreeth Sharma >Assignee: Prabhjyot Singh >Priority: Blocker > > Custom zeppelin interpreter properties are getting lost after moving zeppelin > to a different host > Live Cluster : https://172.27.12.130:8443 > Steps to reproduce : > 1) Modify interpreter settings > a) Add new custom properties > b) Modify existing properties > Changes are getting saved in HDFS path /user/zeppelin/conf/interpreter.json > and they are getting synced to local path /etc/zeppelin/conf/interpreter.json > after zeppelin restart. > 2) Delete zeppelin server > 3) Install zeppelin server on a different host > 4) Modifications done in step 1 are lost. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-22698) Custom zeppelin interpreter properties are getting removed after moving zeppelin to a different host
[ https://issues.apache.org/jira/browse/AMBARI-22698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh reassigned AMBARI-22698: Assignee: Prabhjyot Singh > Custom zeppelin interpreter properties are getting removed after moving > zeppelin to a different host > > > Key: AMBARI-22698 > URL: https://issues.apache.org/jira/browse/AMBARI-22698 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.6.1 > Environment: ambari-server --version 2.6.1.0-136 > HDP-2.6.4.0-85 >Reporter: Supreeth Sharma >Assignee: Prabhjyot Singh >Priority: Blocker > > Custom zeppelin interpreter properties are getting lost after moving zeppelin > to a different host > Live Cluster : https://172.27.12.130:8443 > Steps to reproduce : > 1) Modify interpreter settings > a) Add new custom properties > b) Modify existing properties > Changes are getting saved in HDFS path /user/zeppelin/conf/interpreter.json > and they are getting synced to local path /etc/zeppelin/conf/interpreter.json > after zeppelin restart. > 2) Delete zeppelin server > 3) Install zeppelin server on a different host > 4) Modifications done in step 1 are lost. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22704) Stack unit test fixes
Andrew Onischuk created AMBARI-22704: Summary: Stack unit test fixes Key: AMBARI-22704 URL: https://issues.apache.org/jira/browse/AMBARI-22704 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22704) Stack unit test fixes
[ https://issues.apache.org/jira/browse/AMBARI-22704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22704: - Attachment: AMBARI-22704.patch > Stack unit test fixes > - > > Key: AMBARI-22704 > URL: https://issues.apache.org/jira/browse/AMBARI-22704 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-22704.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22704) Stack unit test fixes
[ https://issues.apache.org/jira/browse/AMBARI-22704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22704: - Status: Patch Available (was: Open) > Stack unit test fixes > - > > Key: AMBARI-22704 > URL: https://issues.apache.org/jira/browse/AMBARI-22704 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-22704.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-22703) Ambari WorkFlow manager doesn't work on a standalone ambari server with remove cluster configured and oozie has enabled SSL
[
https://issues.apache.org/jira/browse/AMBARI-22703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
venkat reassigned AMBARI-22703:
---
Assignee: venkat
> Ambari WorkFlow manager doesn't work on a standalone ambari server with
> remove cluster configured and oozie has enabled SSL
> ---
>
> Key: AMBARI-22703
> URL: https://issues.apache.org/jira/browse/AMBARI-22703
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.2
> Environment: Ambari Version : 2.5.1.0
> ssl enabled oozie and standalone ambari with remote cluster
>Reporter: Akhil S Naik
>Assignee: venkat
> Attachments: oozie keeps loading.png, remote cluster config.png
>
>
> We have a standalone ambari server with remote cluster configured,
> If we configure the workflow manager view of remote cluster with oozie is
> enabled with SSL . The Page keeps showing loading dialog
> (attached image of configuration and issue)
> It keeps loading as shown in the image
>
> !https://issues.apache.org/jira/secure/attachment/12903882/oozie%20keeps%20loading.png!
> possible root cause :
> The wfmanager-view.log shows the server pings on port 11000 instead it has to
> access the port 11443
> {code:java}
> 28 Dec 2017 09:29:51,821 INFO [ambari-client-thread-25] [WORKFLOW_MANAGER
> 1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
> http://host6.example.com:11000/oozie/v1/admin/configuration
> 28 Dec 2017 09:29:52,153 INFO [ambari-client-thread-30] [WORKFLOW_MANAGER
> 1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
> http://host6.example.com:11000/oozie/v2/jobs?filter==1=15=wf
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22703) Ambari WorkFlow manager doesn't work on a standalone ambari server with remove cluster configured and oozie has enabled SSL
[
https://issues.apache.org/jira/browse/AMBARI-22703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil S Naik updated AMBARI-22703:
--
Description:
We have a standalone ambari server with remote cluster configured,
If we configure the workflow manager view of remote cluster with oozie is
enabled with SSL . The Page keeps showing loading dialog
(attached image of configuration and issue)
It keeps loading as shown in the image
!https://issues.apache.org/jira/secure/attachment/12903882/oozie%20keeps%20loading.png!
possible root cause :
The wfmanager-view.log shows the server pings on port 11000 instead it has to
access the port 11443
{code:java}
28 Dec 2017 09:29:51,821 INFO [ambari-client-thread-25] [WORKFLOW_MANAGER
1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
http://host6.example.com:11000/oozie/v1/admin/configuration
28 Dec 2017 09:29:52,153 INFO [ambari-client-thread-30] [WORKFLOW_MANAGER
1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
http://host6.example.com:11000/oozie/v2/jobs?filter==1=15=wf
{code}
was:
We have a standalone ambari server with remote cluster configured,
oozie is enabled with SSL in remote cluster.
workflow manager (view) doesnt work if the view is configured as remote
cluster. (attached image of configuration and issue)
It keeps loading as shown in the image
!https://issues.apache.org/jira/secure/attachment/12903882/oozie%20keeps%20loading.png!
possible root cause :
The wfmanager-view.log shows the server pings on port 11000 instead it has to
access the port 11443
{code:java}
28 Dec 2017 09:29:51,821 INFO [ambari-client-thread-25] [WORKFLOW_MANAGER
1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
http://host6.example.com:11000/oozie/v1/admin/configuration
28 Dec 2017 09:29:52,153 INFO [ambari-client-thread-30] [WORKFLOW_MANAGER
1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
http://host6.example.com:11000/oozie/v2/jobs?filter==1=15=wf
{code}
> Ambari WorkFlow manager doesn't work on a standalone ambari server with
> remove cluster configured and oozie has enabled SSL
> ---
>
> Key: AMBARI-22703
> URL: https://issues.apache.org/jira/browse/AMBARI-22703
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.2
> Environment: Ambari Version : 2.5.1.0
> ssl enabled oozie and standalone ambari with remote cluster
>Reporter: Akhil S Naik
> Attachments: oozie keeps loading.png, remote cluster config.png
>
>
> We have a standalone ambari server with remote cluster configured,
> If we configure the workflow manager view of remote cluster with oozie is
> enabled with SSL . The Page keeps showing loading dialog
> (attached image of configuration and issue)
> It keeps loading as shown in the image
>
> !https://issues.apache.org/jira/secure/attachment/12903882/oozie%20keeps%20loading.png!
> possible root cause :
> The wfmanager-view.log shows the server pings on port 11000 instead it has to
> access the port 11443
> {code:java}
> 28 Dec 2017 09:29:51,821 INFO [ambari-client-thread-25] [WORKFLOW_MANAGER
> 1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
> http://host6.example.com:11000/oozie/v1/admin/configuration
> 28 Dec 2017 09:29:52,153 INFO [ambari-client-thread-30] [WORKFLOW_MANAGER
> 1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
> http://host6.example.com:11000/oozie/v2/jobs?filter==1=15=wf
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22703) Ambari WorkFlow manager doesn't work on a standalone ambari server with remove cluster configured and oozie has enabled SSL
[
https://issues.apache.org/jira/browse/AMBARI-22703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil S Naik updated AMBARI-22703:
--
Description:
We have a standalone ambari server with remote cluster configured,
oozie is enabled with SSL in remote cluster.
workflow manager (view) doesnt work if the view is configured as remote
cluster. (attached image of configuration and issue)
It keeps loading as shown in the image
!https://issues.apache.org/jira/secure/attachment/12903882/oozie%20keeps%20loading.png!
possible root cause :
The wfmanager-view.log shows the server pings on port 11000 instead it has to
access the port 11443
{code:java}
28 Dec 2017 09:29:51,821 INFO [ambari-client-thread-25] [WORKFLOW_MANAGER
1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
http://host6.example.com:11000/oozie/v1/admin/configuration
28 Dec 2017 09:29:52,153 INFO [ambari-client-thread-30] [WORKFLOW_MANAGER
1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
http://host6.example.com:11000/oozie/v2/jobs?filter==1=15=wf
{code}
was:
We have a standalone ambari server with remote cluster configured,
oozie is enabled with SSL in remote cluster.
workflow manager (view) doesnt work if the view is configured as remote
cluster. (attached image of configuration and issue)
It keeps loading as shown in the image
!https://issues.apache.org/jira/secure/attachment/12903882/oozie%20keeps%20loading.png|thumbnail!.
possible root cause :
The wfmanager-view.log shows the server pings on port 11000 instead it has to
access the port 11443
{code:java}
28 Dec 2017 09:29:51,821 INFO [ambari-client-thread-25] [WORKFLOW_MANAGER
1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
http://host6.example.com:11000/oozie/v1/admin/configuration
28 Dec 2017 09:29:52,153 INFO [ambari-client-thread-30] [WORKFLOW_MANAGER
1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
http://host6.example.com:11000/oozie/v2/jobs?filter==1=15=wf
{code}
> Ambari WorkFlow manager doesn't work on a standalone ambari server with
> remove cluster configured and oozie has enabled SSL
> ---
>
> Key: AMBARI-22703
> URL: https://issues.apache.org/jira/browse/AMBARI-22703
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.2
> Environment: Ambari Version : 2.5.1.0
> ssl enabled oozie and standalone ambari with remote cluster
>Reporter: Akhil S Naik
> Attachments: oozie keeps loading.png, remote cluster config.png
>
>
> We have a standalone ambari server with remote cluster configured,
> oozie is enabled with SSL in remote cluster.
> workflow manager (view) doesnt work if the view is configured as remote
> cluster. (attached image of configuration and issue)
> It keeps loading as shown in the image
>
> !https://issues.apache.org/jira/secure/attachment/12903882/oozie%20keeps%20loading.png!
> possible root cause :
> The wfmanager-view.log shows the server pings on port 11000 instead it has to
> access the port 11443
> {code:java}
> 28 Dec 2017 09:29:51,821 INFO [ambari-client-thread-25] [WORKFLOW_MANAGER
> 1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
> http://host6.example.com:11000/oozie/v1/admin/configuration
> 28 Dec 2017 09:29:52,153 INFO [ambari-client-thread-30] [WORKFLOW_MANAGER
> 1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
> http://host6.example.com:11000/oozie/v2/jobs?filter==1=15=wf
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22703) Ambari WorkFlow manager doesn't work on a standalone ambari server with remove cluster configured and oozie has enabled SSL
[
https://issues.apache.org/jira/browse/AMBARI-22703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil S Naik updated AMBARI-22703:
--
Description:
We have a standalone ambari server with remote cluster configured,
oozie is enabled with SSL in remote cluster.
workflow manager (view) doesnt work if the view is configured as remote
cluster. (attached image of configuration and issue)
It keeps loading as shown in the image
!https://issues.apache.org/jira/secure/attachment/12903882/oozie%20keeps%20loading.png|thumbnail!.
possible root cause :
The wfmanager-view.log shows the server pings on port 11000 instead it has to
access the port 11443
{code:java}
28 Dec 2017 09:29:51,821 INFO [ambari-client-thread-25] [WORKFLOW_MANAGER
1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
http://host6.example.com:11000/oozie/v1/admin/configuration
28 Dec 2017 09:29:52,153 INFO [ambari-client-thread-30] [WORKFLOW_MANAGER
1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
http://host6.example.com:11000/oozie/v2/jobs?filter==1=15=wf
{code}
was:
We have a standalone ambari server with remote cluster configured,
oozie is enabled with SSL in remote cluster.
workflow manager (view) doesnt work if the view is configured as remote
cluster. (attached image of configuration and issue)
It keeps loading as shown in the image !attachment-name.jpg|thumbnail!.
possible root cause :
The wfmanager-view.log shows the server pings on port 11000 instead it has to
access the port 11443
{code:java}
28 Dec 2017 09:29:51,821 INFO [ambari-client-thread-25] [WORKFLOW_MANAGER
1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
http://host6.example.com:11000/oozie/v1/admin/configuration
28 Dec 2017 09:29:52,153 INFO [ambari-client-thread-30] [WORKFLOW_MANAGER
1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
http://host6.example.com:11000/oozie/v2/jobs?filter==1=15=wf
{code}
> Ambari WorkFlow manager doesn't work on a standalone ambari server with
> remove cluster configured and oozie has enabled SSL
> ---
>
> Key: AMBARI-22703
> URL: https://issues.apache.org/jira/browse/AMBARI-22703
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.2
> Environment: Ambari Version : 2.5.1.0
> ssl enabled oozie and standalone ambari with remote cluster
>Reporter: Akhil S Naik
> Attachments: oozie keeps loading.png, remote cluster config.png
>
>
> We have a standalone ambari server with remote cluster configured,
> oozie is enabled with SSL in remote cluster.
> workflow manager (view) doesnt work if the view is configured as remote
> cluster. (attached image of configuration and issue)
> It keeps loading as shown in the image
>
> !https://issues.apache.org/jira/secure/attachment/12903882/oozie%20keeps%20loading.png|thumbnail!.
> possible root cause :
> The wfmanager-view.log shows the server pings on port 11000 instead it has to
> access the port 11443
> {code:java}
> 28 Dec 2017 09:29:51,821 INFO [ambari-client-thread-25] [WORKFLOW_MANAGER
> 1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
> http://host6.example.com:11000/oozie/v1/admin/configuration
> 28 Dec 2017 09:29:52,153 INFO [ambari-client-thread-30] [WORKFLOW_MANAGER
> 1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
> http://host6.example.com:11000/oozie/v2/jobs?filter==1=15=wf
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22703) Ambari WorkFlow manager doesn't work on a standalone ambari server with remove cluster configured and oozie has enabled SSL
[
https://issues.apache.org/jira/browse/AMBARI-22703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil S Naik updated AMBARI-22703:
--
Description:
We have a standalone ambari server with remote cluster configured,
oozie is enabled with SSL in remote cluster.
workflow manager (view) doesnt work if the view is configured as remote
cluster. (attached image of configuration and issue)
It keeps loading as shown in the image !attachment-name.jpg|thumbnail!.
possible root cause :
The wfmanager-view.log shows the server pings on port 11000 instead it has to
access the port 11443
{code:java}
28 Dec 2017 09:29:51,821 INFO [ambari-client-thread-25] [WORKFLOW_MANAGER
1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
http://host6.example.com:11000/oozie/v1/admin/configuration
28 Dec 2017 09:29:52,153 INFO [ambari-client-thread-30] [WORKFLOW_MANAGER
1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
http://host6.example.com:11000/oozie/v2/jobs?filter==1=15=wf
{code}
was:
We have a standalone ambari server with remote cluster configured,
oozie is enabled with SSL in remote cluster.
workflow manager (view) doesnt work if the view is configured as remote
cluster. (attached image of configuration and issue)
It keeps loading as shown in the image .
it works if the configuration is custom configuration ( attached image)
The wfmanager-view.log shows the server pings on port 11000 instead it has to
access the port 11443
{code:java}
28 Dec 2017 09:29:51,821 INFO [ambari-client-thread-25] [WORKFLOW_MANAGER
1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
http://host6.example.com:11000/oozie/v1/admin/configuration
28 Dec 2017 09:29:52,153 INFO [ambari-client-thread-30] [WORKFLOW_MANAGER
1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
http://host6.example.com:11000/oozie/v2/jobs?filter==1=15=wf
{code}
> Ambari WorkFlow manager doesn't work on a standalone ambari server with
> remove cluster configured and oozie has enabled SSL
> ---
>
> Key: AMBARI-22703
> URL: https://issues.apache.org/jira/browse/AMBARI-22703
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.2
> Environment: Ambari Version : 2.5.1.0
> ssl enabled oozie and standalone ambari with remote cluster
>Reporter: Akhil S Naik
> Attachments: oozie keeps loading.png, remote cluster config.png
>
>
> We have a standalone ambari server with remote cluster configured,
> oozie is enabled with SSL in remote cluster.
> workflow manager (view) doesnt work if the view is configured as remote
> cluster. (attached image of configuration and issue)
> It keeps loading as shown in the image !attachment-name.jpg|thumbnail!.
> possible root cause :
> The wfmanager-view.log shows the server pings on port 11000 instead it has to
> access the port 11443
> {code:java}
> 28 Dec 2017 09:29:51,821 INFO [ambari-client-thread-25] [WORKFLOW_MANAGER
> 1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
> http://host6.example.com:11000/oozie/v1/admin/configuration
> 28 Dec 2017 09:29:52,153 INFO [ambari-client-thread-30] [WORKFLOW_MANAGER
> 1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
> http://host6.example.com:11000/oozie/v2/jobs?filter==1=15=wf
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22703) Ambari WorkFlow manager doesn't work on a standalone ambari server with remove cluster configured and oozie has enabled SSL
[
https://issues.apache.org/jira/browse/AMBARI-22703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil S Naik updated AMBARI-22703:
--
Attachment: remote cluster config.png
> Ambari WorkFlow manager doesn't work on a standalone ambari server with
> remove cluster configured and oozie has enabled SSL
> ---
>
> Key: AMBARI-22703
> URL: https://issues.apache.org/jira/browse/AMBARI-22703
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.2
> Environment: Ambari Version : 2.5.1.0
> ssl enabled oozie and standalone ambari with remote cluster
>Reporter: Akhil S Naik
> Attachments: oozie keeps loading.png, remote cluster config.png
>
>
> We have a standalone ambari server with remote cluster configured,
> oozie is enabled with SSL in remote cluster.
> workflow manager (view) doesnt work if the view is configured as remote
> cluster. (attached image of configuration and issue)
> It keeps loading as shown in the image .
> it works if the configuration is custom configuration ( attached image)
> The wfmanager-view.log shows the server pings on port 11000 instead it has to
> access the port 11443
> {code:java}
> 28 Dec 2017 09:29:51,821 INFO [ambari-client-thread-25] [WORKFLOW_MANAGER
> 1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
> http://host6.example.com:11000/oozie/v1/admin/configuration
> 28 Dec 2017 09:29:52,153 INFO [ambari-client-thread-30] [WORKFLOW_MANAGER
> 1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
> http://host6.example.com:11000/oozie/v2/jobs?filter==1=15=wf
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22703) Ambari WorkFlow manager doesn't work on a standalone ambari server with remove cluster configured and oozie has enabled SSL
[
https://issues.apache.org/jira/browse/AMBARI-22703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil S Naik updated AMBARI-22703:
--
Attachment: oozie keeps loading.png
> Ambari WorkFlow manager doesn't work on a standalone ambari server with
> remove cluster configured and oozie has enabled SSL
> ---
>
> Key: AMBARI-22703
> URL: https://issues.apache.org/jira/browse/AMBARI-22703
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.2
> Environment: Ambari Version : 2.5.1.0
> ssl enabled oozie and standalone ambari with remote cluster
>Reporter: Akhil S Naik
> Attachments: oozie keeps loading.png
>
>
> We have a standalone ambari server with remote cluster configured,
> oozie is enabled with SSL in remote cluster.
> workflow manager (view) doesnt work if the view is configured as remote
> cluster. (attached image of configuration and issue)
> It keeps loading as shown in the image .
> it works if the configuration is custom configuration ( attached image)
> The wfmanager-view.log shows the server pings on port 11000 instead it has to
> access the port 11443
> {code:java}
> 28 Dec 2017 09:29:51,821 INFO [ambari-client-thread-25] [WORKFLOW_MANAGER
> 1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
> http://host6.example.com:11000/oozie/v1/admin/configuration
> 28 Dec 2017 09:29:52,153 INFO [ambari-client-thread-30] [WORKFLOW_MANAGER
> 1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
> http://host6.example.com:11000/oozie/v2/jobs?filter==1=15=wf
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22703) Ambari WorkFlow manager doesn't work on a standalone ambari server with remove cluster configured and oozie has enabled SSL
Akhil S Naik created AMBARI-22703:
-
Summary: Ambari WorkFlow manager doesn't work on a standalone
ambari server with remove cluster configured and oozie has enabled SSL
Key: AMBARI-22703
URL: https://issues.apache.org/jira/browse/AMBARI-22703
Project: Ambari
Issue Type: Bug
Components: ambari-views
Affects Versions: 2.5.2
Environment: Ambari Version : 2.5.1.0
ssl enabled oozie and standalone ambari with remote cluster
Reporter: Akhil S Naik
We have a standalone ambari server with remote cluster configured,
oozie is enabled with SSL in remote cluster.
workflow manager (view) doesnt work if the view is configured as remote
cluster. (attached image of configuration and issue)
It keeps loading as shown in the image .
it works if the configuration is custom configuration ( attached image)
The wfmanager-view.log shows the server pings on port 11000 instead it has to
access the port 11443
{code:java}
28 Dec 2017 09:29:51,821 INFO [ambari-client-thread-25] [WORKFLOW_MANAGER
1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
http://host6.example.com:11000/oozie/v1/admin/configuration
28 Dec 2017 09:29:52,153 INFO [ambari-client-thread-30] [WORKFLOW_MANAGER
1.0.0 WF] OozieDelegate:149 - Proxy request for url: [GET]
http://host6.example.com:11000/oozie/v2/jobs?filter==1=15=wf
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21757) Allow for keytab regeneration to be filtered for hosts
[ https://issues.apache.org/jira/browse/AMBARI-21757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305210#comment-16305210 ] wangyaoxin commented on AMBARI-21757: - Hi [~echekanskiy] , the patch has some problem . If regenerate keytab for host1, ambari-qa-clus...@example.com or hdfs-clus...@example.com will be affected, but the smokeuser.headless.keytab or hdfs.headless.keytab on other hosts will not created. cased password incorrect while getting initial credentials. > Allow for keytab regeneration to be filtered for hosts > -- > > Key: AMBARI-21757 > URL: https://issues.apache.org/jira/browse/AMBARI-21757 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0, 2.6.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 3.0.0, 2.6.0 > > Attachments: AMBARI-21757-trunk-2.patch, AMBARI-21757-trunk-3.patch, > AMBARI-21757-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22626) Zeppelin Interpreter settings are getting updated after zeppelin restart
[
https://issues.apache.org/jira/browse/AMBARI-22626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prabhjyot Singh updated AMBARI-22626:
-
Resolution: Fixed
Fix Version/s: 3.0.0
Status: Resolved (was: Patch Available)
> Zeppelin Interpreter settings are getting updated after zeppelin restart
>
>
> Key: AMBARI-22626
> URL: https://issues.apache.org/jira/browse/AMBARI-22626
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
>Affects Versions: 2.6.1
> Environment: ambari-server --version
> 2.6.1.0-114
>Reporter: Supreeth Sharma
>Assignee: Prabhjyot Singh
>Priority: Critical
> Fix For: 3.0.0, 2.6.2
>
> Attachments: AMBARI-22626_branch-2.6_v1.patch,
> AMBARI-22626_trunk_v1.patch
>
>
> Zeppelin Interpreter settings are getting updated after zeppelin restart.
> Live cluster :
> http://ctr-e135-1512069032975-20895-02-09.hwx.site:9995/#/interpreter
> Steps to reproduce :
> 1) Update the zeppelin.pyspark.python to /base/tools/python-2.7.14/bin/python
> for spark2 interpreter
> 2) Restart zeppelin
> 3) After restart zeppelin.pyspark.python is getting overridden with value
> 'python'.
> Same is observed with livy2 interpreter.
> But same steps for spark interpreter is working fine even after zeppelin
> restart.
> So looks like issue is happening only for spark2 and livy2 interpreter.
> Seeing below error in zeppelin logs :
> {code}
> INFO [2017-12-11 12:31:25,876] ({main} LuceneSearch.java[addIndexDocs]:305) -
> Indexing 20 notebooks took 472ms
> INFO [2017-12-11 12:31:25,876] ({main} Notebook.java[]:129) - Notebook
> indexing finished: 20 indexed in 0s
> WARN [2017-12-11 12:31:25,879] ({main} Helium.java[loadConf]:101) -
> /usr/hdp/current/zeppelin-server/conf/helium.json does not exists
> WARN [2017-12-11 12:31:25,882] ({main} NotebookRepoSync.java[]:88) -
> Failed to initialize org.apache.zeppelin.notebook.repo.FileSystemNotebookRepo
> notebook storage class
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.zeppelin.notebook.repo.NotebookRepoSync.(NotebookRepoSync.java:83)
> at
> org.apache.zeppelin.server.ZeppelinServer.(ZeppelinServer.java:155)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22506) Incorrect pie chart distribution
[ https://issues.apache.org/jira/browse/AMBARI-22506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-22506: - Resolution: Fixed Fix Version/s: 2.6.2 3.0.0 Status: Resolved (was: Patch Available) > Incorrect pie chart distribution > > > Key: AMBARI-22506 > URL: https://issues.apache.org/jira/browse/AMBARI-22506 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.6.1 >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Fix For: 3.0.0, 2.6.2 > > Attachments: AMBARI-22506_trunk_v1.patch, AMBARI-22506_trunk_v2.patch > > > Phoenix JDBC does number formatting if its a decimal, as describe in > https://phoenix.apache.org/tuning.html "phoenix.query.numberFormat" with > "#,##0.###", which causes a problem with displaying of graph. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
