[jira] [Updated] (AMBARI-19861) Improve display for Action messages pop ups
[ https://issues.apache.org/jira/browse/AMBARI-19861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yesha Vora updated AMBARI-19861: Attachment: Screen Shot 2017-02-02 at 2.38.30 PM.png > Improve display for Action messages pop ups > --- > > Key: AMBARI-19861 > URL: https://issues.apache.org/jira/browse/AMBARI-19861 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Reporter: Yesha Vora > Attachments: Screen Shot 2017-02-02 at 2.38.30 PM.png > > > Improve display for Action Needed pop up box. > Example: If a user tries to delete a service , Ambari pops up a message a box > to stop the services first. > This pop up box does not highlight that an action is required before > proceeding to the deletion. > It looks like a "confirmation needed" pop up box. > It will be great if we can highlight the message or pop box to explicitly > draw user's attention that its an prompt for an action. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19861) Improve display for Action messages pop ups
Yesha Vora created AMBARI-19861: --- Summary: Improve display for Action messages pop ups Key: AMBARI-19861 URL: https://issues.apache.org/jira/browse/AMBARI-19861 Project: Ambari Issue Type: Improvement Components: ambari-web Reporter: Yesha Vora Improve display for Action Needed pop up box. Example: If a user tries to delete a service , Ambari pops up a message a box to stop the services first. This pop up box does not highlight that an action is required before proceeding to the deletion. It looks like a "confirmation needed" pop up box. It will be great if we can highlight the message or pop box to explicitly draw user's attention that its an prompt for an action. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19860) Ambari upgrade to HDP 2.5 from earlier versions does not update storm worker/cluster log directory
[
https://issues.apache.org/jira/browse/AMBARI-19860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Mahadevan updated AMBARI-19860:
Description:
During upgrade the storm worker.xml and cluster.xml files should have updated
path.
{noformat}
{noformat}
was:
During upgrade the storm worker.xml and cluster.xml files should have updated
path.
> Ambari upgrade to HDP 2.5 from earlier versions does not update storm
> worker/cluster log directory
> --
>
> Key: AMBARI-19860
> URL: https://issues.apache.org/jira/browse/AMBARI-19860
> Project: Ambari
> Issue Type: Bug
>Reporter: Arun Mahadevan
>
> During upgrade the storm worker.xml and cluster.xml files should have updated
> path.
> {noformat}
>
> fileName="${sys:workers.artifacts}/${sys:storm.id}/${sys:worker.port}/${sys:logfile.name}"
>
> filePattern="${sys:workers.artifacts}/${sys:storm.id}/${sys:worker.port}/${sys:logfile.name}.%i.gz">
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-19860) Ambari upgrade to HDP 2.5 from earlier versions does not update storm worker/cluster log directory
Arun Mahadevan created AMBARI-19860: --- Summary: Ambari upgrade to HDP 2.5 from earlier versions does not update storm worker/cluster log directory Key: AMBARI-19860 URL: https://issues.apache.org/jira/browse/AMBARI-19860 Project: Ambari Issue Type: Bug Reporter: Arun Mahadevan During upgrade the storm worker.xml and cluster.xml files should have updated path. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19859) The user must be clearly communicated about YARN pre-emption requirements when Hive LLAP is enabled
[ https://issues.apache.org/jira/browse/AMBARI-19859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19859: Attachment: AMBARI-19859.v1.patch > The user must be clearly communicated about YARN pre-emption requirements > when Hive LLAP is enabled > --- > > Key: AMBARI-19859 > URL: https://issues.apache.org/jira/browse/AMBARI-19859 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19859.v0.patch, AMBARI-19859.v1.patch, Ambari > c1.png, Screen Shot 2017-02-02 at 7.02.45 PM.png > > > Capacity Scheduler preemption is not enabled by default in HDP. Enabling it > affects the entire cluster. But it is strongly recommended to enable YARN > pre-emption before enabling Hive LLAP. The user needs to be warned about this > before enabling Interactive Query in Hive configs page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19859) The user must be clearly communicated about YARN pre-emption requirements when Hive LLAP is enabled
[ https://issues.apache.org/jira/browse/AMBARI-19859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19859: Attachment: Screen Shot 2017-02-02 at 7.02.45 PM.png Ambari c1.png > The user must be clearly communicated about YARN pre-emption requirements > when Hive LLAP is enabled > --- > > Key: AMBARI-19859 > URL: https://issues.apache.org/jira/browse/AMBARI-19859 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19859.v0.patch, Ambari c1.png, Screen Shot > 2017-02-02 at 7.02.45 PM.png > > > Capacity Scheduler preemption is not enabled by default in HDP. Enabling it > affects the entire cluster. But it is strongly recommended to enable YARN > pre-emption before enabling Hive LLAP. The user needs to be warned about this > before enabling Interactive Query in Hive configs page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19859) The user must be clearly communicated about YARN pre-emption requirements when Hive LLAP is enabled
[ https://issues.apache.org/jira/browse/AMBARI-19859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15851001#comment-15851001 ] Vivek Ratnavel Subramanian commented on AMBARI-19859: - Attached are the screen-shots after the patch. > The user must be clearly communicated about YARN pre-emption requirements > when Hive LLAP is enabled > --- > > Key: AMBARI-19859 > URL: https://issues.apache.org/jira/browse/AMBARI-19859 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19859.v0.patch, Ambari c1.png, Screen Shot > 2017-02-02 at 7.02.45 PM.png > > > Capacity Scheduler preemption is not enabled by default in HDP. Enabling it > affects the entire cluster. But it is strongly recommended to enable YARN > pre-emption before enabling Hive LLAP. The user needs to be warned about this > before enabling Interactive Query in Hive configs page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19859) The user must be clearly communicated about YARN pre-emption requirements when Hive LLAP is enabled
[ https://issues.apache.org/jira/browse/AMBARI-19859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19859: Attachment: AMBARI-19859.v0.patch > The user must be clearly communicated about YARN pre-emption requirements > when Hive LLAP is enabled > --- > > Key: AMBARI-19859 > URL: https://issues.apache.org/jira/browse/AMBARI-19859 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19859.v0.patch > > > Capacity Scheduler preemption is not enabled by default in HDP. Enabling it > affects the entire cluster. But it is strongly recommended to enable YARN > pre-emption before enabling Hive LLAP. The user needs to be warned about this > before enabling Interactive Query in Hive configs page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19859) The user must be clearly communicated about YARN pre-emption requirements when Hive LLAP is enabled
[ https://issues.apache.org/jira/browse/AMBARI-19859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19859: Status: Patch Available (was: In Progress) > The user must be clearly communicated about YARN pre-emption requirements > when Hive LLAP is enabled > --- > > Key: AMBARI-19859 > URL: https://issues.apache.org/jira/browse/AMBARI-19859 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19859.v0.patch > > > Capacity Scheduler preemption is not enabled by default in HDP. Enabling it > affects the entire cluster. But it is strongly recommended to enable YARN > pre-emption before enabling Hive LLAP. The user needs to be warned about this > before enabling Interactive Query in Hive configs page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19859) The user must be clearly communicated about YARN pre-emption requirements when Hive LLAP is enabled
Vivek Ratnavel Subramanian created AMBARI-19859: --- Summary: The user must be clearly communicated about YARN pre-emption requirements when Hive LLAP is enabled Key: AMBARI-19859 URL: https://issues.apache.org/jira/browse/AMBARI-19859 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 2.5.0 Capacity Scheduler preemption is not enabled by default in HDP. Enabling it affects the entire cluster. But it is strongly recommended to enable YARN pre-emption before enabling Hive LLAP. The user needs to be warned about this before enabling Interactive Query in Hive configs page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19858) Add "live_hosts" metric in AMS for apps
[
https://issues.apache.org/jira/browse/AMBARI-19858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle updated AMBARI-19858:
-
Status: Patch Available (was: Open)
> Add "live_hosts" metric in AMS for apps
> ---
>
> Key: AMBARI-19858
> URL: https://issues.apache.org/jira/browse/AMBARI-19858
> Project: Ambari
> Issue Type: Task
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
> Fix For: 2.5.0
>
> Attachments: AMBARI-19858.patch
>
>
> {quote}
> live_hosts=> # count of total hosts reporting
> metrics
> live_hosts & appId = => # count of hosts hosting this appId
> {quote}
> Where appId = { namenode, datanode, hbase ... etc }
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19858) Add "live_hosts" metric in AMS for apps
[
https://issues.apache.org/jira/browse/AMBARI-19858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle updated AMBARI-19858:
-
Attachment: AMBARI-19858.patch
> Add "live_hosts" metric in AMS for apps
> ---
>
> Key: AMBARI-19858
> URL: https://issues.apache.org/jira/browse/AMBARI-19858
> Project: Ambari
> Issue Type: Task
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
> Fix For: 2.5.0
>
> Attachments: AMBARI-19858.patch
>
>
> {quote}
> live_hosts=> # count of total hosts reporting
> metrics
> live_hosts & appId = => # count of hosts hosting this appId
> {quote}
> Where appId = { namenode, datanode, hbase ... etc }
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-19858) Add "live_hosts" metric in AMS for apps
Siddharth Wagle created AMBARI-19858:
Summary: Add "live_hosts" metric in AMS for apps
Key: AMBARI-19858
URL: https://issues.apache.org/jira/browse/AMBARI-19858
Project: Ambari
Issue Type: Task
Components: ambari-metrics
Affects Versions: 2.5.0
Reporter: Siddharth Wagle
Assignee: Siddharth Wagle
Fix For: 2.5.0
{quote}
live_hosts=> # count of total hosts reporting
metrics
live_hosts & appId = => # count of hosts hosting this appId
{quote}
Where appId = { namenode, datanode, hbase ... etc }
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-18930) Ambari thinks a component is installed, even if the install is partially done
[ https://issues.apache.org/jira/browse/AMBARI-18930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18930: - Attachment: AMBARI-19830.patch > Ambari thinks a component is installed, even if the install is partially done > - > > Key: AMBARI-18930 > URL: https://issues.apache.org/jira/browse/AMBARI-18930 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Zsombor Gegesy > Attachments: AMBARI-19830.patch > > > We have lot's of deployment problems which ends up in a state, where Ambari > thinks a component is installed, but when it tries to start it, the component > fails to start up, because missing kerberos keytabs. > The investigation found the following scenario : > * blueprint install > * For the datanode to install it's needs the following steps: > ** install the datanode package on host A > ** generate keytab(s) on server > ** set up datanode-keytab on host A > * In the "Install components on host " step the following steps are > scheduled : > ** package install > ** (other package install) > ** keytab setup > * If there was an error in the 'other package install', then the kerberos key > generation, and host setup is skipped. > * But Ambari thinks, this component is installed - because the package > install step succeeded. > * However, when/if someone tries to start the component, it fails with the > missing keytabs > * The only way to fix this is to manually "Delete" and "Reinstall" the > component, which doesn't make the best impression on the user. > Proposed ideas to fix : > * re-order the install steps - first generate the keytabs on the server, > distribute to the host, and later install the package. This would ensure, > when the package is installed on a host, it's keytabs are there as well. > * mark the partially installed component as 'install failed' on the UI - so > the user could try to re-install, when they see it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-18930) Ambari thinks a component is installed, even if the install is partially done
[ https://issues.apache.org/jira/browse/AMBARI-18930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18930: - Status: Patch Available (was: Open) > Ambari thinks a component is installed, even if the install is partially done > - > > Key: AMBARI-18930 > URL: https://issues.apache.org/jira/browse/AMBARI-18930 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Zsombor Gegesy > Attachments: AMBARI-19830.patch > > > We have lot's of deployment problems which ends up in a state, where Ambari > thinks a component is installed, but when it tries to start it, the component > fails to start up, because missing kerberos keytabs. > The investigation found the following scenario : > * blueprint install > * For the datanode to install it's needs the following steps: > ** install the datanode package on host A > ** generate keytab(s) on server > ** set up datanode-keytab on host A > * In the "Install components on host " step the following steps are > scheduled : > ** package install > ** (other package install) > ** keytab setup > * If there was an error in the 'other package install', then the kerberos key > generation, and host setup is skipped. > * But Ambari thinks, this component is installed - because the package > install step succeeded. > * However, when/if someone tries to start the component, it fails with the > missing keytabs > * The only way to fix this is to manually "Delete" and "Reinstall" the > component, which doesn't make the best impression on the user. > Proposed ideas to fix : > * re-order the install steps - first generate the keytabs on the server, > distribute to the host, and later install the package. This would ensure, > when the package is installed on a host, it's keytabs are there as well. > * mark the partially installed component as 'install failed' on the UI - so > the user could try to re-install, when they see it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19857) Side Nav: create clickable breadcrumbs on top showing current path
[ https://issues.apache.org/jira/browse/AMBARI-19857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19857: - Status: Patch Available (was: Open) > Side Nav: create clickable breadcrumbs on top showing current path > -- > > Key: AMBARI-19857 > URL: https://issues.apache.org/jira/browse/AMBARI-19857 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19857.patch > > > Should show breadcrumbs on the top bar showing current path. > User can navigate to any parent page by clicking on the breadcrumbs > Eg. Ambari / Services-HDFS > Ambari / Hosts / hostname -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19857) Side Nav: create clickable breadcrumbs on top showing current path
[ https://issues.apache.org/jira/browse/AMBARI-19857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-19857: - Attachment: AMBARI-19857.patch > Side Nav: create clickable breadcrumbs on top showing current path > -- > > Key: AMBARI-19857 > URL: https://issues.apache.org/jira/browse/AMBARI-19857 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-19857.patch > > > Should show breadcrumbs on the top bar showing current path. > User can navigate to any parent page by clicking on the breadcrumbs > Eg. Ambari / Services-HDFS > Ambari / Hosts / hostname -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19857) Side Nav: create clickable breadcrumbs on top showing current path
[ https://issues.apache.org/jira/browse/AMBARI-19857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850901#comment-15850901 ] Xi Wang commented on AMBARI-19857: -- 20325 passing (30s) 153 pending > Side Nav: create clickable breadcrumbs on top showing current path > -- > > Key: AMBARI-19857 > URL: https://issues.apache.org/jira/browse/AMBARI-19857 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > > Should show breadcrumbs on the top bar showing current path. > User can navigate to any parent page by clicking on the breadcrumbs > Eg. Ambari / Services-HDFS > Ambari / Hosts / hostname -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19857) Side Nav: create clickable breadcrumbs on top showing current path
Xi Wang created AMBARI-19857: Summary: Side Nav: create clickable breadcrumbs on top showing current path Key: AMBARI-19857 URL: https://issues.apache.org/jira/browse/AMBARI-19857 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Xi Wang Assignee: Xi Wang Fix For: 3.0.0 Should show breadcrumbs on the top bar showing current path. User can navigate to any parent page by clicking on the breadcrumbs Eg. Ambari / Services-HDFS Ambari / Hosts / hostname -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19856) Perf: start/stop all actions works much slower after few days of testing
[
https://issues.apache.org/jira/browse/AMBARI-19856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850882#comment-15850882
]
Hadoop QA commented on AMBARI-19856:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12850729/AMBARI-19856.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10391//console
This message is automatically generated.
> Perf: start/stop all actions works much slower after few days of testing
>
>
> Key: AMBARI-19856
> URL: https://issues.apache.org/jira/browse/AMBARI-19856
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19856.patch
>
>
> Add changes to gce script, to deploy perf cluster with all options needed.
> Try to find more code to optimize.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19805) Add outputFormat attribute to all PXF Hive-related profiles
[ https://issues.apache.org/jira/browse/AMBARI-19805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850842#comment-15850842 ] Hudson commented on AMBARI-19805: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #893 (See [https://builds.apache.org/job/Ambari-branch-2.5/893/]) AMBARI-19805. Add outputFormat attribute to all PXF Hive-related (odiachenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ccaa4a8a0b51dd3436db9bff9cbbb13e9455ec7c]) * (edit) ambari-server/src/main/resources/common-services/PXF/3.0.0/configuration/pxf-profiles.xml > Add outputFormat attribute to all PXF Hive-related profiles > --- > > Key: AMBARI-19805 > URL: https://issues.apache.org/jira/browse/AMBARI-19805 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Oleksandr Diachenko >Assignee: Oleksandr Diachenko >Priority: Minor > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19805.patch > > > There was new attribute outputFormat introduced in > https://issues.apache.org/jira/browse/HAWQ-1228, which needs to be reflected > in PXF as a common service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19805) Add outputFormat attribute to all PXF Hive-related profiles
[ https://issues.apache.org/jira/browse/AMBARI-19805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850817#comment-15850817 ] Hudson commented on AMBARI-19805: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6635 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6635/]) AMBARI-19805. Add outputFormat attribute to all PXF Hive-related (odiachenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=14cd837ea5c33ca4ebf5daf9262fe40d1f5a9130]) * (edit) ambari-server/src/main/resources/common-services/PXF/3.0.0/configuration/pxf-profiles.xml > Add outputFormat attribute to all PXF Hive-related profiles > --- > > Key: AMBARI-19805 > URL: https://issues.apache.org/jira/browse/AMBARI-19805 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Oleksandr Diachenko >Assignee: Oleksandr Diachenko >Priority: Minor > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19805.patch > > > There was new attribute outputFormat introduced in > https://issues.apache.org/jira/browse/HAWQ-1228, which needs to be reflected > in PXF as a common service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19856) Perf: start/stop all actions works much slower after few days of testing
[ https://issues.apache.org/jira/browse/AMBARI-19856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-19856: --- Status: Patch Available (was: Open) > Perf: start/stop all actions works much slower after few days of testing > > > Key: AMBARI-19856 > URL: https://issues.apache.org/jira/browse/AMBARI-19856 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19856.patch > > > Add changes to gce script, to deploy perf cluster with all options needed. > Try to find more code to optimize. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19856) Perf: start/stop all actions works much slower after few days of testing
[ https://issues.apache.org/jira/browse/AMBARI-19856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-19856: --- Attachment: AMBARI-19856.patch > Perf: start/stop all actions works much slower after few days of testing > > > Key: AMBARI-19856 > URL: https://issues.apache.org/jira/browse/AMBARI-19856 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19856.patch > > > Add changes to gce script, to deploy perf cluster with all options needed. > Try to find more code to optimize. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19856) Perf: start/stop all actions works much slower after few days of testing
Vitaly Brodetskyi created AMBARI-19856: -- Summary: Perf: start/stop all actions works much slower after few days of testing Key: AMBARI-19856 URL: https://issues.apache.org/jira/browse/AMBARI-19856 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Vitaly Brodetskyi Assignee: Vitaly Brodetskyi Priority: Critical Fix For: 2.5.0 Add changes to gce script, to deploy perf cluster with all options needed. Try to find more code to optimize. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19805) Add outputFormat attribute to all PXF Hive-related profiles
[ https://issues.apache.org/jira/browse/AMBARI-19805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleksandr Diachenko updated AMBARI-19805: - Resolution: Fixed Status: Resolved (was: Patch Available) > Add outputFormat attribute to all PXF Hive-related profiles > --- > > Key: AMBARI-19805 > URL: https://issues.apache.org/jira/browse/AMBARI-19805 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Oleksandr Diachenko >Assignee: Oleksandr Diachenko >Priority: Minor > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19805.patch > > > There was new attribute outputFormat introduced in > https://issues.apache.org/jira/browse/HAWQ-1228, which needs to be reflected > in PXF as a common service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19805) Add outputFormat attribute to all PXF Hive-related profiles
[
https://issues.apache.org/jira/browse/AMBARI-19805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850767#comment-15850767
]
Oleksandr Diachenko commented on AMBARI-19805:
--
Pushed to branch-2.5:
{code}
commit ccaa4a8a0b51dd3436db9bff9cbbb13e9455ec7c
Author: Oleksandr Diachenko
Date: Thu Feb 2 16:01:24 2017 -0800
AMBARI-19805. Add outputFormat attribute to all PXF Hive-related profiles.
{code}
> Add outputFormat attribute to all PXF Hive-related profiles
> ---
>
> Key: AMBARI-19805
> URL: https://issues.apache.org/jira/browse/AMBARI-19805
> Project: Ambari
> Issue Type: Improvement
> Components: stacks
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
>Priority: Minor
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19805.patch
>
>
> There was new attribute outputFormat introduced in
> https://issues.apache.org/jira/browse/HAWQ-1228, which needs to be reflected
> in PXF as a common service.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19805) Add outputFormat attribute to all PXF Hive-related profiles
[
https://issues.apache.org/jira/browse/AMBARI-19805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850766#comment-15850766
]
Oleksandr Diachenko commented on AMBARI-19805:
--
Pushed to trunk:
{code}
commit 14cd837ea5c33ca4ebf5daf9262fe40d1f5a9130
Author: Oleksandr Diachenko
Date: Thu Feb 2 15:58:28 2017 -0800
AMBARI-19805. Add outputFormat attribute to all PXF Hive-related profiles.
{code}
> Add outputFormat attribute to all PXF Hive-related profiles
> ---
>
> Key: AMBARI-19805
> URL: https://issues.apache.org/jira/browse/AMBARI-19805
> Project: Ambari
> Issue Type: Improvement
> Components: stacks
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
>Priority: Minor
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19805.patch
>
>
> There was new attribute outputFormat introduced in
> https://issues.apache.org/jira/browse/HAWQ-1228, which needs to be reflected
> in PXF as a common service.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
[
https://issues.apache.org/jira/browse/AMBARI-19810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850765#comment-15850765
]
Hudson commented on AMBARI-19810:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6634 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6634/])
AMBARI-19810. Remove upgrade logic in UpdateCatalog250 for (sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=975dd1d40c6136a61e7d014fb0dfc32e09863a2b])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
> Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's
> 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
> ---
>
> Key: AMBARI-19810
> URL: https://issues.apache.org/jira/browse/AMBARI-19810
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19810.01.patch, AMBARI-19810.trunk.01.patch
>
>
> Remove the following code and its references:
> {code}
> + protected void updateTEZInteractiveConfigs() throws AmbariException {
> +AmbariManagementController ambariManagementController =
> injector.getInstance(AmbariManagementController.class);
> +Clusters clusters = ambariManagementController.getClusters();
> +if (clusters != null) {
> + Map clusterMap = clusters.getClusters();
> +
> + if (clusterMap != null && !clusterMap.isEmpty()) {
> +for (final Cluster cluster : clusterMap.values()) {
> + Config tezInteractiveSite =
> cluster.getDesiredConfigByType("tez-interactive-site");
> + if (tezInteractiveSite != null) {
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.io.sort.mb", "512"), true, true);
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.unordered.output.buffer.size-mb",
> +"100"), true, true);
> + }
> +}
> + }
> +}
> + }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19805) Add outputFormat attribute to all PXF Hive-related profiles
[ https://issues.apache.org/jira/browse/AMBARI-19805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850759#comment-15850759 ] Oleksandr Diachenko commented on AMBARI-19805: -- [~adenissov] yes, it's compatible, PXF loads profiles file as map and access necessary properties by keys. In older version PXF won't use newer key. > Add outputFormat attribute to all PXF Hive-related profiles > --- > > Key: AMBARI-19805 > URL: https://issues.apache.org/jira/browse/AMBARI-19805 > Project: Ambari > Issue Type: Improvement > Components: stacks >Reporter: Oleksandr Diachenko >Assignee: Oleksandr Diachenko >Priority: Minor > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19805.patch > > > There was new attribute outputFormat introduced in > https://issues.apache.org/jira/browse/HAWQ-1228, which needs to be reflected > in PXF as a common service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
[
https://issues.apache.org/jira/browse/AMBARI-19810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850740#comment-15850740
]
Hudson commented on AMBARI-19810:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #892 (See
[https://builds.apache.org/job/Ambari-branch-2.5/892/])
AMBARI-19810. Remove upgrade logic in UpdateCatalog250 for (sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a8887c44500d92e225d6d53774595500fc1a6c01])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
> Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's
> 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
> ---
>
> Key: AMBARI-19810
> URL: https://issues.apache.org/jira/browse/AMBARI-19810
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19810.01.patch, AMBARI-19810.trunk.01.patch
>
>
> Remove the following code and its references:
> {code}
> + protected void updateTEZInteractiveConfigs() throws AmbariException {
> +AmbariManagementController ambariManagementController =
> injector.getInstance(AmbariManagementController.class);
> +Clusters clusters = ambariManagementController.getClusters();
> +if (clusters != null) {
> + Map clusterMap = clusters.getClusters();
> +
> + if (clusterMap != null && !clusterMap.isEmpty()) {
> +for (final Cluster cluster : clusterMap.values()) {
> + Config tezInteractiveSite =
> cluster.getDesiredConfigByType("tez-interactive-site");
> + if (tezInteractiveSite != null) {
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.io.sort.mb", "512"), true, true);
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.unordered.output.buffer.size-mb",
> +"100"), true, true);
> + }
> +}
> + }
> +}
> + }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
[
https://issues.apache.org/jira/browse/AMBARI-19810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19810:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's
> 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
> ---
>
> Key: AMBARI-19810
> URL: https://issues.apache.org/jira/browse/AMBARI-19810
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19810.01.patch, AMBARI-19810.trunk.01.patch
>
>
> Remove the following code and its references:
> {code}
> + protected void updateTEZInteractiveConfigs() throws AmbariException {
> +AmbariManagementController ambariManagementController =
> injector.getInstance(AmbariManagementController.class);
> +Clusters clusters = ambariManagementController.getClusters();
> +if (clusters != null) {
> + Map clusterMap = clusters.getClusters();
> +
> + if (clusterMap != null && !clusterMap.isEmpty()) {
> +for (final Cluster cluster : clusterMap.values()) {
> + Config tezInteractiveSite =
> cluster.getDesiredConfigByType("tez-interactive-site");
> + if (tezInteractiveSite != null) {
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.io.sort.mb", "512"), true, true);
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.unordered.output.buffer.size-mb",
> +"100"), true, true);
> + }
> +}
> + }
> +}
> + }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
[
https://issues.apache.org/jira/browse/AMBARI-19810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850690#comment-15850690
]
Swapan Shridhar commented on AMBARI-19810:
--
commit
trunk:
{code}
commit 975dd1d40c6136a61e7d014fb0dfc32e09863a2b
Author: Swapan Shridhar
Date: Thu Feb 2 14:09:00 2017 -0800
AMBARI-19810. Remove upgrade logic in UpdateCatalog250 for
tez-interactive-site's 'tez.runtime.io.sort.mb' and
'tez.runtime.unordered.output.buffer.size-mb'.
{code}
branch-2.5:
{code}
commit a8887c44500d92e225d6d53774595500fc1a6c01
Author: Swapan Shridhar
Date: Thu Feb 2 11:23:17 2017 -0800
AMBARI-19810. Remove upgrade logic in UpdateCatalog250 for
tez-interactive-site's 'tez.runtime.io.sort.mb' and
'tez.runtime.unordered.output.buffer.size-mb'.
{code}
> Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's
> 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
> ---
>
> Key: AMBARI-19810
> URL: https://issues.apache.org/jira/browse/AMBARI-19810
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19810.01.patch, AMBARI-19810.trunk.01.patch
>
>
> Remove the following code and its references:
> {code}
> + protected void updateTEZInteractiveConfigs() throws AmbariException {
> +AmbariManagementController ambariManagementController =
> injector.getInstance(AmbariManagementController.class);
> +Clusters clusters = ambariManagementController.getClusters();
> +if (clusters != null) {
> + Map clusterMap = clusters.getClusters();
> +
> + if (clusterMap != null && !clusterMap.isEmpty()) {
> +for (final Cluster cluster : clusterMap.values()) {
> + Config tezInteractiveSite =
> cluster.getDesiredConfigByType("tez-interactive-site");
> + if (tezInteractiveSite != null) {
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.io.sort.mb", "512"), true, true);
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.unordered.output.buffer.size-mb",
> +"100"), true, true);
> + }
> +}
> + }
> +}
> + }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
[
https://issues.apache.org/jira/browse/AMBARI-19810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19810:
-
Status: Open (was: Patch Available)
> Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's
> 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
> ---
>
> Key: AMBARI-19810
> URL: https://issues.apache.org/jira/browse/AMBARI-19810
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19810.01.patch, AMBARI-19810.trunk.01.patch
>
>
> Remove the following code and its references:
> {code}
> + protected void updateTEZInteractiveConfigs() throws AmbariException {
> +AmbariManagementController ambariManagementController =
> injector.getInstance(AmbariManagementController.class);
> +Clusters clusters = ambariManagementController.getClusters();
> +if (clusters != null) {
> + Map clusterMap = clusters.getClusters();
> +
> + if (clusterMap != null && !clusterMap.isEmpty()) {
> +for (final Cluster cluster : clusterMap.values()) {
> + Config tezInteractiveSite =
> cluster.getDesiredConfigByType("tez-interactive-site");
> + if (tezInteractiveSite != null) {
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.io.sort.mb", "512"), true, true);
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.unordered.output.buffer.size-mb",
> +"100"), true, true);
> + }
> +}
> + }
> +}
> + }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
[
https://issues.apache.org/jira/browse/AMBARI-19810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19810:
-
Attachment: AMBARI-19810.01.patch
> Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's
> 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
> ---
>
> Key: AMBARI-19810
> URL: https://issues.apache.org/jira/browse/AMBARI-19810
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19810.01.patch, AMBARI-19810.trunk.01.patch
>
>
> Remove the following code and its references:
> {code}
> + protected void updateTEZInteractiveConfigs() throws AmbariException {
> +AmbariManagementController ambariManagementController =
> injector.getInstance(AmbariManagementController.class);
> +Clusters clusters = ambariManagementController.getClusters();
> +if (clusters != null) {
> + Map clusterMap = clusters.getClusters();
> +
> + if (clusterMap != null && !clusterMap.isEmpty()) {
> +for (final Cluster cluster : clusterMap.values()) {
> + Config tezInteractiveSite =
> cluster.getDesiredConfigByType("tez-interactive-site");
> + if (tezInteractiveSite != null) {
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.io.sort.mb", "512"), true, true);
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.unordered.output.buffer.size-mb",
> +"100"), true, true);
> + }
> +}
> + }
> +}
> + }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
[
https://issues.apache.org/jira/browse/AMBARI-19810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19810:
-
Attachment: AMBARI-19810.trunk.01.patch
> Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's
> 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
> ---
>
> Key: AMBARI-19810
> URL: https://issues.apache.org/jira/browse/AMBARI-19810
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19810.01.patch, AMBARI-19810.trunk.01.patch
>
>
> Remove the following code and its references:
> {code}
> + protected void updateTEZInteractiveConfigs() throws AmbariException {
> +AmbariManagementController ambariManagementController =
> injector.getInstance(AmbariManagementController.class);
> +Clusters clusters = ambariManagementController.getClusters();
> +if (clusters != null) {
> + Map clusterMap = clusters.getClusters();
> +
> + if (clusterMap != null && !clusterMap.isEmpty()) {
> +for (final Cluster cluster : clusterMap.values()) {
> + Config tezInteractiveSite =
> cluster.getDesiredConfigByType("tez-interactive-site");
> + if (tezInteractiveSite != null) {
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.io.sort.mb", "512"), true, true);
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.unordered.output.buffer.size-mb",
> +"100"), true, true);
> + }
> +}
> + }
> +}
> + }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
[
https://issues.apache.org/jira/browse/AMBARI-19810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19810:
-
Status: Patch Available (was: Open)
> Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's
> 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
> ---
>
> Key: AMBARI-19810
> URL: https://issues.apache.org/jira/browse/AMBARI-19810
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19810.01.patch, AMBARI-19810.trunk.01.patch
>
>
> Remove the following code and its references:
> {code}
> + protected void updateTEZInteractiveConfigs() throws AmbariException {
> +AmbariManagementController ambariManagementController =
> injector.getInstance(AmbariManagementController.class);
> +Clusters clusters = ambariManagementController.getClusters();
> +if (clusters != null) {
> + Map clusterMap = clusters.getClusters();
> +
> + if (clusterMap != null && !clusterMap.isEmpty()) {
> +for (final Cluster cluster : clusterMap.values()) {
> + Config tezInteractiveSite =
> cluster.getDesiredConfigByType("tez-interactive-site");
> + if (tezInteractiveSite != null) {
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.io.sort.mb", "512"), true, true);
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.unordered.output.buffer.size-mb",
> +"100"), true, true);
> + }
> +}
> + }
> +}
> + }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19810) Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
[
https://issues.apache.org/jira/browse/AMBARI-19810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19810:
-
Attachment: (was: AMBARI-19810.01.patch)
> Remove upgrade logic in UpdateCatalog250 for tez-interactive-site's
> 'tez.runtime.io.sort.mb' and 'tez.runtime.unordered.output.buffer.size-mb'.
> ---
>
> Key: AMBARI-19810
> URL: https://issues.apache.org/jira/browse/AMBARI-19810
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
>
> Remove the following code and its references:
> {code}
> + protected void updateTEZInteractiveConfigs() throws AmbariException {
> +AmbariManagementController ambariManagementController =
> injector.getInstance(AmbariManagementController.class);
> +Clusters clusters = ambariManagementController.getClusters();
> +if (clusters != null) {
> + Map clusterMap = clusters.getClusters();
> +
> + if (clusterMap != null && !clusterMap.isEmpty()) {
> +for (final Cluster cluster : clusterMap.values()) {
> + Config tezInteractiveSite =
> cluster.getDesiredConfigByType("tez-interactive-site");
> + if (tezInteractiveSite != null) {
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.io.sort.mb", "512"), true, true);
> +
> +updateConfigurationProperties("tez-interactive-site",
> Collections.singletonMap("tez.runtime.unordered.output.buffer.size-mb",
> +"100"), true, true);
> + }
> +}
> + }
> +}
> + }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-17722) Add some of value-attributes to property files in TEZ
[ https://issues.apache.org/jira/browse/AMBARI-17722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850561#comment-15850561 ] Hudson commented on AMBARI-17722: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6633 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6633/]) AMBARI-17722. Add some of value-attributes to property files in TEZ. (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ebc05a917597eaa0b9cba60bb205478143538a78]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/TEZ/configuration/tez-site.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/TEZ/configuration/tez-site.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/TEZ/configuration/tez-site.xml * (edit) ambari-server/src/main/resources/stacks/HDPWIN/2.2/services/TEZ/configuration/tez-site.xml * (edit) ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/configuration/tez-site.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/TEZ/configuration/tez-site.xml > Add some of value-attributes to property files in TEZ > - > > Key: AMBARI-17722 > URL: https://issues.apache.org/jira/browse/AMBARI-17722 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka >Priority: Minor > Fix For: 2.5.0 > > Attachments: after_tez_capture.PNG, AMBARI-17722.patch, > tez_capture.PNG > > > Some of the property files in TEZ lack value-attributes. > It would be nice to have value-attributes on most of the properties. If so, > we can notice a careless mistakes in Ambari Server WebUI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-17722) Add some of value-attributes to property files in TEZ
[ https://issues.apache.org/jira/browse/AMBARI-17722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850555#comment-15850555 ] Hudson commented on AMBARI-17722: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #891 (See [https://builds.apache.org/job/Ambari-branch-2.5/891/]) AMBARI-17722. Add some of value-attributes to property files in TEZ. (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9b51e8b5f3a088c9ee2d4e557c003acf39487c53]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/services/TEZ/configuration/tez-site.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/TEZ/configuration/tez-site.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/TEZ/configuration/tez-site.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/TEZ/configuration/tez-site.xml * (edit) ambari-server/src/main/resources/common-services/TEZ/0.4.0.2.1/configuration/tez-site.xml * (edit) ambari-server/src/main/resources/stacks/HDPWIN/2.2/services/TEZ/configuration/tez-site.xml > Add some of value-attributes to property files in TEZ > - > > Key: AMBARI-17722 > URL: https://issues.apache.org/jira/browse/AMBARI-17722 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka >Priority: Minor > Fix For: 2.5.0 > > Attachments: after_tez_capture.PNG, AMBARI-17722.patch, > tez_capture.PNG > > > Some of the property files in TEZ lack value-attributes. > It would be nice to have value-attributes on most of the properties. If so, > we can notice a careless mistakes in Ambari Server WebUI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-14754) Description going out of the explain view when we execute a query in hive view
[ https://issues.apache.org/jira/browse/AMBARI-14754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850544#comment-15850544 ] Yusaku Sako commented on AMBARI-14754: -- [~pallavkul] can you review the patch? > Description going out of the explain view when we execute a query in hive view > -- > > Key: AMBARI-14754 > URL: https://issues.apache.org/jira/browse/AMBARI-14754 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.2.1 > Environment: CentOS 6 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.0 > > Attachments: ambari-14754_branch-2.2.patch, Ambari-14754.png > > > In hive view, after executing a query, the description in explain view was > going out of the container. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19819) Styling changes and spelling fixes
[ https://issues.apache.org/jira/browse/AMBARI-19819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-19819: - Resolution: Fixed Status: Resolved (was: Patch Available) > Styling changes and spelling fixes > --- > > Key: AMBARI-19819 > URL: https://issues.apache.org/jira/browse/AMBARI-19819 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: M Madhan Mohan Reddy >Assignee: M Madhan Mohan Reddy > Labels: WFD > Fix For: 2.5.0 > > Attachments: AMBARI-19819_trunk.patch > > > Spelling fixes given by Beverley and minor coolor changes based on inputs > from Priyanka -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19720) when restarting HSI, Ambari should not run slider stop and slider destroy (LLAP script already does that)
[ https://issues.apache.org/jira/browse/AMBARI-19720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-19720: - Resolution: Fixed Status: Resolved (was: Patch Available) > when restarting HSI, Ambari should not run slider stop and slider destroy > (LLAP script already does that) > - > > Key: AMBARI-19720 > URL: https://issues.apache.org/jira/browse/AMBARI-19720 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.5.0 >Reporter: Sumit Mohanty >Assignee: Sumit Mohanty >Priority: Critical > Fix For: 2.5.0 > > > These commands are pure overhead, because spinning up slider and connecting > to things is slow. On some test cluster it took ~12sec to do 100ms of noop > work. > LLAP script already runs them and will eventually avoid the overhead by > calling Slider APIs from an existing JVM. However we just noticed when > restarting HSI (but not when restarting LLAP only), Ambari also runs these > commands. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19433) Increase default timeout and threadpool size for the external script to work on slower machines
[ https://issues.apache.org/jira/browse/AMBARI-19433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850529#comment-15850529 ] Yusaku Sako commented on AMBARI-19433: -- +1 for the patch. > Increase default timeout and threadpool size for the external script to work > on slower machines > --- > > Key: AMBARI-19433 > URL: https://issues.apache.org/jira/browse/AMBARI-19433 > Project: Ambari > Issue Type: Task >Affects Versions: 2.5.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > Attachments: AMBARI-19433.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19375) Update the execution mode for hive interactive in HDP 2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-19375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-19375: - Resolution: Fixed Status: Resolved (was: Patch Available) > Update the execution mode for hive interactive in HDP 2.6 stack > --- > > Key: AMBARI-19375 > URL: https://issues.apache.org/jira/browse/AMBARI-19375 > Project: Ambari > Issue Type: Task > Components: stacks >Reporter: Siddharth Seth >Assignee: Siddharth Seth > Fix For: 2.5.0 > > Attachments: AMBARI-19375.01.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19286) Handle permissions for setting service auto start in FE
[ https://issues.apache.org/jira/browse/AMBARI-19286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-19286: - Resolution: Fixed Status: Resolved (was: Patch Available) > Handle permissions for setting service auto start in FE > --- > > Key: AMBARI-19286 > URL: https://issues.apache.org/jira/browse/AMBARI-19286 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19286.patch > > > The UI needs to be updated to handle permissions to manage cluster- and > service-level auto start settings. > If authorization failure occurs, the UI takes the user to the login screen > and then to the dashboard. > The following roles should be able to toggle auto-start at the cluster level > (permission: CLUSTER.MANAGE_AUTO_START): > * Ambari Administrator > * Cluster Administrator > * Cluster Operator > The following roles should be able to toggle auto-start at the service level > (permission: SERVICE.MANAGE_AUTO_START): > * Ambari Administrator > * Cluster Administrator > * Cluster Operator > * Service Administrator -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19329) Install Wizard cannot proceed beyond Select Services page
[ https://issues.apache.org/jira/browse/AMBARI-19329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-19329: - Resolution: Fixed Status: Resolved (was: Patch Available) > Install Wizard cannot proceed beyond Select Services page > - > > Key: AMBARI-19329 > URL: https://issues.apache.org/jira/browse/AMBARI-19329 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Blocker > Fix For: 2.5.0 > > Attachments: 1.png, 2.png, AMBARI-19329.patch > > > See attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19014) Add Service Wizard: error thrown during transition on deploy step
[
https://issues.apache.org/jira/browse/AMBARI-19014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako updated AMBARI-19014:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Add Service Wizard: error thrown during transition on deploy step
> -
>
> Key: AMBARI-19014
> URL: https://issues.apache.org/jira/browse/AMBARI-19014
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19014.patch
>
>
> STR:
> * Install cluster with Zookeeper
> * Run Add Service Wizard
> * Select HDFS
> * Proceed to Review step
> * Click Next button
> AR: Transition to deploy stopped because of error {{TypeError: Cannot read
> property 'get' of undefined(...)}}
> ER: Successful transition to deploy step
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-18964) unable to add users permission for tez view
[ https://issues.apache.org/jira/browse/AMBARI-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-18964: - Fix Version/s: (was: 2.4.2) > unable to add users permission for tez view > --- > > Key: AMBARI-18964 > URL: https://issues.apache.org/jira/browse/AMBARI-18964 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Attachments: AMBARI-18964.branch-2.4.patch, Screen Shot 2016-11-22 at > 13.45.25.png > > > During upgrade from 2.4.0, the privileges for the tez view got migrated to > the new tez view version but after a restart the same privileges again got > inserted into the privilege table(due to a piece of view migration that runs > during every restart) and hence in the admin view while opening the tez view > instance, JS errors were thrown which prevented insertion of further users to > the permission box. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-18964) unable to add users permission for tez view
[ https://issues.apache.org/jira/browse/AMBARI-18964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-18964: - Fix Version/s: (was: 2.5.0) 2.4.2 > unable to add users permission for tez view > --- > > Key: AMBARI-18964 > URL: https://issues.apache.org/jira/browse/AMBARI-18964 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: DIPAYAN BHOWMICK >Assignee: DIPAYAN BHOWMICK > Fix For: 2.4.2 > > Attachments: AMBARI-18964.branch-2.4.patch, Screen Shot 2016-11-22 at > 13.45.25.png > > > During upgrade from 2.4.0, the privileges for the tez view got migrated to > the new tez view version but after a restart the same privileges again got > inserted into the privilege table(due to a piece of view migration that runs > during every restart) and hence in the admin view while opening the tez view > instance, JS errors were thrown which prevented insertion of further users to > the permission box. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-18744) Ambari-server: REST API changes to GET and PUT credential store information
[
https://issues.apache.org/jira/browse/AMBARI-18744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako updated AMBARI-18744:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.5.
> Ambari-server: REST API changes to GET and PUT credential store information
> ---
>
> Key: AMBARI-18744
> URL: https://issues.apache.org/jira/browse/AMBARI-18744
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53283.patch
>
>
> *Support stack definition for credential store information*
> To support backward compatibility, services must be tagged to indicate
> whether they support credential store backed passwords. This requires changes
> in the stack definition object model.
> {code}
>
> SERVICE_NAME
> :
>
> true
> false
>
> :
> :
>
> {code}
> *REST API support is required to GET _credential_store_supported_ and
> _credential_store_enabled_ values for a service:*
> {quote}api/v1/clusters//services?fields=ServiceInfo/service_name,ServiceInfo/credential_store_supported,ServiceInfo/credential_store_enabled{quote}
> *REST API support is required to PUT _credential_store_enabled_ value for a
> service:*
> {quote}curl -u admin:admin -H "X-Requested-By: ambari"
> http://localhost:8080/api/v1/clusters/cl1/services -X PUT -d
> '{"ServceInfo":{"credential_store_enabled":"true"},
> "RequestInfo":{"query":"ServiceInfo/service_name.in(HIVE,YARN)"}}'{quote}
> {quote}api/v1/clusters/testcluster/services/RANGER -X PUT -d '{"ServiceInfo"
> : {"credential_store_enabled":"true"}}'
> {quote}
> {quote}api/v1/clusters/testcluster/services?ServiceInfo/service_name=ZOOKEEPER
> -X PUT -d '{"ServiceInfo" : {"credential_store_enabled":"false"}}'{quote}
> *REST API to get Stack definition*
> {quote}
> curl -u admin:admin -H "X-Requested-By: ambari" -X GET
> http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services
> {quote}
> {quote}
> {
> "href" : "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/";,
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/YARN";,
> "StackServices" : {
> "service_name" : "YARN",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> },
> {
> "href" :
> "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/ZOOKEEPER";,
> "StackServices" : {
> "service_name" : "ZOOKEEPER",
> "stack_name" : "HDP",
> "stack_version" : "2.0",
> "credential_store_supported" : "false",
> "credential_store_enabled" : "false"
> }
> }
> ]
> }
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-17722) Add some of value-attributes to property files in TEZ
[ https://issues.apache.org/jira/browse/AMBARI-17722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-17722: - Resolution: Fixed Status: Resolved (was: Patch Available) > Add some of value-attributes to property files in TEZ > - > > Key: AMBARI-17722 > URL: https://issues.apache.org/jira/browse/AMBARI-17722 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka >Priority: Minor > Fix For: 2.5.0 > > Attachments: after_tez_capture.PNG, AMBARI-17722.patch, > tez_capture.PNG > > > Some of the property files in TEZ lack value-attributes. > It would be nice to have value-attributes on most of the properties. If so, > we can notice a careless mistakes in Ambari Server WebUI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-18712) compare functionality between config versions is not working
[ https://issues.apache.org/jira/browse/AMBARI-18712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-18712: - Resolution: Fixed Status: Resolved (was: Patch Available) > compare functionality between config versions is not working > > > Key: AMBARI-18712 > URL: https://issues.apache.org/jira/browse/AMBARI-18712 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 2.5.0 > > Attachments: AMBARI-18712.patch > > > STR: > Navigate to Hive service page. Try comparing versions > Expected Result: Only config with difference should be shown > Actual Result: All configs are shown. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-15563) hcat_log_dir is still not editable in UI
[ https://issues.apache.org/jira/browse/AMBARI-15563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-15563: - Resolution: Fixed Status: Resolved (was: Patch Available) > hcat_log_dir is still not editable in UI > > > Key: AMBARI-15563 > URL: https://issues.apache.org/jira/browse/AMBARI-15563 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-15563.patch > > > we should be able to edit all log dirs post install. This is not true for > hcat_log_dir property, and needs to be fixed -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-15563) hcat_log_dir is still not editable in UI
[ https://issues.apache.org/jira/browse/AMBARI-15563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-15563: - Fix Version/s: (was: 2.5.0) 2.4.0 > hcat_log_dir is still not editable in UI > > > Key: AMBARI-15563 > URL: https://issues.apache.org/jira/browse/AMBARI-15563 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-15563.patch > > > we should be able to edit all log dirs post install. This is not true for > hcat_log_dir property, and needs to be fixed -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-15153) Change Ranger's default value for LDAP Group Sync Case Conversion properties to "none"
[ https://issues.apache.org/jira/browse/AMBARI-15153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-15153: - Resolution: Fixed Status: Resolved (was: Patch Available) > Change Ranger's default value for LDAP Group Sync Case Conversion properties > to "none" > -- > > Key: AMBARI-15153 > URL: https://issues.apache.org/jira/browse/AMBARI-15153 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Gautam Borad >Assignee: Gautam Borad > Fix For: 2.5.0 > > Attachments: AMBARI-15153.patch > > > *Use Case:* > If user's LDAP / AD has uppercase usernames and produce uppercase user > Kerberos principals. When doing the initial user sync into Ranger, the > default setting of "lower" causes all their user names to be saved in lower > case, meaning they don't match the Kerberos principals that LDAP / AD is > handing out. > It seems to me the more sensible default for both username and group case > conversion should be "none" and to just use whatever the backend directory > hands out, as-is, to prevent unexpected confusion such as this. > *Proposed Solution:* > Change Ranger's default settings for below given properties : > ldapGroupSync.username.caseConversion = "none" > ldapGroupSync.groupname.caseConversion = "none" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-15197) Make use of log dir properties while installing Ranger
[ https://issues.apache.org/jira/browse/AMBARI-15197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-15197: - Resolution: Fixed Status: Resolved (was: Patch Available) > Make use of log dir properties while installing Ranger > -- > > Key: AMBARI-15197 > URL: https://issues.apache.org/jira/browse/AMBARI-15197 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0 >Reporter: Gautam Borad >Assignee: Gautam Borad > Fix For: 2.5.0 > > Attachments: AMBARI-15197.patch > > > *PROBLEM:* > The ranger_admin_log_dir and ranger_usersync_log_dir settings under "Advanced > ranger-env" doesn't do anything. > It is not using the value given in above properties to create / set the log > directory for Ranger service. Fix it for HDP-2.3. > *PROPOSED SOLUTION:* > Need to use these properties and create / set log dir and set correct > permissions for log dir for Ranger. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-18709) Javascript Error When Using ComponentState Filter On Host Page
[
https://issues.apache.org/jira/browse/AMBARI-18709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yusaku Sako updated AMBARI-18709:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.5.
> Javascript Error When Using ComponentState Filter On Host Page
> --
>
> Key: AMBARI-18709
> URL: https://issues.apache.org/jira/browse/AMBARI-18709
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.5.0
>
> Attachments: AMBARI-18709.patch
>
>
> Filter:
> NameNode: All Returns JS Error.
> {code}
> Uncaught ReferenceError: key is not definedcreateComboParamURL @
> app.js:22618generateQueryParam @ app.js:22607(anonymous function) @
> app.js:2343computeParameters @ app.js:2304getComplexUrl @
> app.js:2290getHostByHostComponents @ app.js:2561preLoadHosts @
> app.js:2544updateHost @ app.js:2480refresh @ app.js:209658updateComboFilter @
> app.js:62571search @ app.js:210406searchEvent @ vendor.js:61440search @
> vendor.js:61993(anonymous function) @ vendor.js:61878_trigger @
> vendor.js:49109selected @ vendor.js:49300_trigger @ vendor.js:49109select @
> vendor.js:49742(anonymous function) @ vendor.js:49200dispatch @
> vendor.js:3178elemData.handle @ vendor.js:2854
> app.js:22618 Uncaught ReferenceError: key is not definedcreateComboParamURL @
> app.js:22618generateQueryParam @ app.js:22607(anonymous function) @
> app.js:2343computeParameters @ app.js:2304getComplexUrl @
> app.js:2290getHostByHostComponents @ app.js:2561preLoadHosts @
> app.js:2544updateHost @ app.js:2480func @ app.js:179592
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19824) Add consistency checker for blueprint tables
[
https://issues.apache.org/jira/browse/AMBARI-19824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850503#comment-15850503
]
Hadoop QA commented on AMBARI-19824:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12850673/AMBARI-19824.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.serveraction.upgrades.UpgradeActionTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10390//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10390//console
This message is automatically generated.
> Add consistency checker for blueprint tables
>
>
> Key: AMBARI-19824
> URL: https://issues.apache.org/jira/browse/AMBARI-19824
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19824.patch
>
>
> Additional check for topolgy tables: check that for each row in
> topology_request there is at least one row in topology_logical_request,
> topology_host_request, topology_host_task, topology_logical_task.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-17722) Add some of value-attributes to property files in TEZ
[ https://issues.apache.org/jira/browse/AMBARI-17722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850499#comment-15850499 ] Yusaku Sako commented on AMBARI-17722: -- +1 for the patch. Committed to trunk and branch-2.5. > Add some of value-attributes to property files in TEZ > - > > Key: AMBARI-17722 > URL: https://issues.apache.org/jira/browse/AMBARI-17722 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka >Priority: Minor > Fix For: 2.5.0 > > Attachments: after_tez_capture.PNG, AMBARI-17722.patch, > tez_capture.PNG > > > Some of the property files in TEZ lack value-attributes. > It would be nice to have value-attributes on most of the properties. If so, > we can notice a careless mistakes in Ambari Server WebUI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-16974) Service config page is broken on kerberized cluster
[ https://issues.apache.org/jira/browse/AMBARI-16974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850490#comment-15850490 ] Yusaku Sako commented on AMBARI-16974: -- This was part of 2.4.0 but never got resolved to Fixed by mistake. > Service config page is broken on kerberized cluster > --- > > Key: AMBARI-16974 > URL: https://issues.apache.org/jira/browse/AMBARI-16974 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16974.patch > > > This happens due to JS error -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-17283) Display LLAP calculated configs as 'Labels' (non-editable) on 'Hive Server Interactive' Panel and Textboxes (editable) in HIVE Advanced section.
[ https://issues.apache.org/jira/browse/AMBARI-17283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850492#comment-15850492 ] Yusaku Sako commented on AMBARI-17283: -- The fix was already in 2.4.0. > Display LLAP calculated configs as 'Labels' (non-editable) on 'Hive Server > Interactive' Panel and Textboxes (editable) in HIVE Advanced section. > > > Key: AMBARI-17283 > URL: https://issues.apache.org/jira/browse/AMBARI-17283 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17283.2.patch, AMBARI-17283.patch > > > Following configs need to be shown as Labels on Hive Server Interactive Panel. > - hive-interactive-site/hive.llap.daemon.yarn.container.mb > - hive-interactive-site/hive.llap.daemon.num.executors > - hive-interactive-site/hive.llap.io.memory.size > - hive-interactive-env/num_llap_nodes > User will have the option to edit them on HIVE Advanced page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-16974) Service config page is broken on kerberized cluster
[ https://issues.apache.org/jira/browse/AMBARI-16974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-16974: - Resolution: Fixed Status: Resolved (was: Patch Available) > Service config page is broken on kerberized cluster > --- > > Key: AMBARI-16974 > URL: https://issues.apache.org/jira/browse/AMBARI-16974 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16974.patch > > > This happens due to JS error -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-17283) Display LLAP calculated configs as 'Labels' (non-editable) on 'Hive Server Interactive' Panel and Textboxes (editable) in HIVE Advanced section.
[ https://issues.apache.org/jira/browse/AMBARI-17283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-17283: - Fix Version/s: (was: 2.5.0) 2.4.0 > Display LLAP calculated configs as 'Labels' (non-editable) on 'Hive Server > Interactive' Panel and Textboxes (editable) in HIVE Advanced section. > > > Key: AMBARI-17283 > URL: https://issues.apache.org/jira/browse/AMBARI-17283 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17283.2.patch, AMBARI-17283.patch > > > Following configs need to be shown as Labels on Hive Server Interactive Panel. > - hive-interactive-site/hive.llap.daemon.yarn.container.mb > - hive-interactive-site/hive.llap.daemon.num.executors > - hive-interactive-site/hive.llap.io.memory.size > - hive-interactive-env/num_llap_nodes > User will have the option to edit them on HIVE Advanced page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-17283) Display LLAP calculated configs as 'Labels' (non-editable) on 'Hive Server Interactive' Panel and Textboxes (editable) in HIVE Advanced section.
[ https://issues.apache.org/jira/browse/AMBARI-17283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-17283: - Resolution: Fixed Status: Resolved (was: Patch Available) > Display LLAP calculated configs as 'Labels' (non-editable) on 'Hive Server > Interactive' Panel and Textboxes (editable) in HIVE Advanced section. > > > Key: AMBARI-17283 > URL: https://issues.apache.org/jira/browse/AMBARI-17283 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Swapan Shridhar >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17283.2.patch, AMBARI-17283.patch > > > Following configs need to be shown as Labels on Hive Server Interactive Panel. > - hive-interactive-site/hive.llap.daemon.yarn.container.mb > - hive-interactive-site/hive.llap.daemon.num.executors > - hive-interactive-site/hive.llap.io.memory.size > - hive-interactive-env/num_llap_nodes > User will have the option to edit them on HIVE Advanced page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-16928) Unable navigate to "Service Accounts" and "Kerberos" tab during upgrade
[ https://issues.apache.org/jira/browse/AMBARI-16928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-16928: - Resolution: Fixed Status: Resolved (was: Patch Available) > Unable navigate to "Service Accounts" and "Kerberos" tab during upgrade > --- > > Key: AMBARI-16928 > URL: https://issues.apache.org/jira/browse/AMBARI-16928 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-16928.patch > > > STR: > # Start Rolling upgrade > # Try to navigate to "Service Accounts" and "Kerberos" tab -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-16928) Unable navigate to "Service Accounts" and "Kerberos" tab during upgrade
[ https://issues.apache.org/jira/browse/AMBARI-16928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-16928: - Fix Version/s: (was: 2.5.0) 2.4.0 > Unable navigate to "Service Accounts" and "Kerberos" tab during upgrade > --- > > Key: AMBARI-16928 > URL: https://issues.apache.org/jira/browse/AMBARI-16928 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-16928.patch > > > STR: > # Start Rolling upgrade > # Try to navigate to "Service Accounts" and "Kerberos" tab -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-16974) Service config page is broken on kerberized cluster
[ https://issues.apache.org/jira/browse/AMBARI-16974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-16974: - Fix Version/s: (was: 2.5.0) 2.4.0 > Service config page is broken on kerberized cluster > --- > > Key: AMBARI-16974 > URL: https://issues.apache.org/jira/browse/AMBARI-16974 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16974.patch > > > This happens due to JS error -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-16004) Hive-view change to show "UNKNOWN" status for saved queries,history queries
[ https://issues.apache.org/jira/browse/AMBARI-16004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-16004: - Fix Version/s: (was: 2.5.0) 3.0.0 > Hive-view change to show "UNKNOWN" status for saved queries,history queries > > > Key: AMBARI-16004 > URL: https://issues.apache.org/jira/browse/AMBARI-16004 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.2.1 >Reporter: Pradarttana >Priority: Minor > Labels: patch > Fix For: 3.0.0 > > Attachments: AMBARI-16004_trunk.patch > > Original Estimate: 24h > Remaining Estimate: 24h > > Hive-view should show the "UNKNOWN" status to the queries in saved queries > and history queries. > This is done in order to facilitate the migration of hive queries from hue to > ambari. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-15763) Delete service: UX edits v2
[ https://issues.apache.org/jira/browse/AMBARI-15763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-15763: - Fix Version/s: (was: 2.5.0) 2.4.0 > Delete service: UX edits v2 > --- > > Key: AMBARI-15763 > URL: https://issues.apache.org/jira/browse/AMBARI-15763 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-15763.patch, minor-wording (1).pptx > > > Minor text edit to dependent service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-15763) Delete service: UX edits v2
[ https://issues.apache.org/jira/browse/AMBARI-15763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-15763: - Resolution: Fixed Status: Resolved (was: Patch Available) > Delete service: UX edits v2 > --- > > Key: AMBARI-15763 > URL: https://issues.apache.org/jira/browse/AMBARI-15763 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-15763.patch, minor-wording (1).pptx > > > Minor text edit to dependent service. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19828) UI changes to resolve discrepancies between what the stack vs Ambari reports as "live" for NodeManagers
[ https://issues.apache.org/jira/browse/AMBARI-19828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850449#comment-15850449 ] Hudson commented on AMBARI-19828: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #890 (See [https://builds.apache.org/job/Ambari-branch-2.5/890/]) AMBARI-19828. UI changes to resolve discrepancies between what the stack (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0ffa1bcd924d1d1c3e7236cafe2f23a2199bbdad]) * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/views/main/service/services/yarn.js * (edit) ambari-web/test/views/main/service/services/hdfs_test.js * (edit) ambari-web/app/views/main/service/services/hdfs.js * (edit) ambari-web/test/views/main/service/services/yarn_test.js > UI changes to resolve discrepancies between what the stack vs Ambari reports > as "live" for NodeManagers > --- > > Key: AMBARI-19828 > URL: https://issues.apache.org/jira/browse/AMBARI-19828 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19828.v0.branch-2.5.patch, > AMBARI-19828.v0.trunk.patch > > > Looks like the changes in https://issues.apache.org/jira/browse/AMBARI-9418 > was meant to be applied to YARN summary / NodeManagers as well, but that is > not happening. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19319) Disable auto start before RU/EU and enable during finalization phase
[ https://issues.apache.org/jira/browse/AMBARI-19319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850450#comment-15850450 ] Hudson commented on AMBARI-19319: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #890 (See [https://builds.apache.org/job/Ambari-branch-2.5/890/]) AMBARI-19319 Disable auto start before RU/EU and enable during (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=53e1bd8afa994715fcbd5ab69aae7f512e345246]) * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/templates/main/admin/stack_upgrade/stack_upgrade_wizard.hbs > Disable auto start before RU/EU and enable during finalization phase > > > Key: AMBARI-19319 > URL: https://issues.apache.org/jira/browse/AMBARI-19319 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19319.patch > > > Add the API calls to disable/enable auto start and assign it to the UI team > to make the changes as part of RU/EU orchestration. > Lets see if we can also design an alert that WARNs when autostart is disabled > - especially if it was disabled due to EU/RU. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19319) Disable auto start before RU/EU and enable during finalization phase
[
https://issues.apache.org/jira/browse/AMBARI-19319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850438#comment-15850438
]
Hadoop QA commented on AMBARI-19319:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12850670/AMBARI-19319.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10389//console
This message is automatically generated.
> Disable auto start before RU/EU and enable during finalization phase
>
>
> Key: AMBARI-19319
> URL: https://issues.apache.org/jira/browse/AMBARI-19319
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19319.patch
>
>
> Add the API calls to disable/enable auto start and assign it to the UI team
> to make the changes as part of RU/EU orchestration.
> Lets see if we can also design an alert that WARNs when autostart is disabled
> - especially if it was disabled due to EU/RU.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19319) Disable auto start before RU/EU and enable during finalization phase
[ https://issues.apache.org/jira/browse/AMBARI-19319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850435#comment-15850435 ] Hudson commented on AMBARI-19319: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6632 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6632/]) AMBARI-19319 Disable auto start before RU/EU and enable during (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b457d7b874364b105d08a657e37721de973f9dca]) * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/templates/main/admin/stack_upgrade/stack_upgrade_wizard.hbs > Disable auto start before RU/EU and enable during finalization phase > > > Key: AMBARI-19319 > URL: https://issues.apache.org/jira/browse/AMBARI-19319 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19319.patch > > > Add the API calls to disable/enable auto start and assign it to the UI team > to make the changes as part of RU/EU orchestration. > Lets see if we can also design an alert that WARNs when autostart is disabled > - especially if it was disabled due to EU/RU. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19825) Metrics data is not getting collected for different services when AMS HTTPS is enabled
[
https://issues.apache.org/jira/browse/AMBARI-19825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850434#comment-15850434
]
Hudson commented on AMBARI-19825:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6632 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6632/])
AMBARI-19825 : Metrics data is not getting collected for different (avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9c1b153e21f04d96f0afa806436c8e4d702be0cc])
* (edit)
ambari-metrics/ambari-metrics-hadoop-sink/src/main/java/org/apache/hadoop/metrics2/sink/timeline/HadoopTimelineMetricsSink.java
* (edit)
ambari-metrics/ambari-metrics-flume-sink/src/main/java/org/apache/hadoop/metrics2/sink/flume/FlumeTimelineMetricsSink.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/AmbariMetricSinkImpl.java
> Metrics data is not getting collected for different services when AMS HTTPS
> is enabled
> --
>
> Key: AMBARI-19825
> URL: https://issues.apache.org/jira/browse/AMBARI-19825
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19825-2.5.patch, AMBARI-19825-trunk.patch
>
>
> {code}
> org.apache.hadoop.metrics2.impl.MetricsConfigException: Error creating
> plugin: org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink
> at
> org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:203)
> at
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.newSink(MetricsSystemImpl.java:529)
> at
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configureSinks(MetricsSystemImpl.java:501)
> at
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configure(MetricsSystemImpl.java:480)
> at
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.start(MetricsSystemImpl.java:189)
> at
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.init(MetricsSystemImpl.java:164)
> at
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.init(DefaultMetricsSystem.java:54)
> at
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.initialize(DefaultMetricsSystem.java:50)
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.makeInstance(DataNode.java:2530)
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:2435)
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.createDataNode(DataNode.java:2482)
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.secureMain(DataNode.java:2622)
> at
> org.apache.hadoop.hdfs.server.datanode.SecureDataNodeStarter.start(SecureDataNodeStarter.java:77)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243)
> Caused by: java.lang.IllegalArgumentException: no SSLSocketFactory specified
> at
> javax.net.ssl.HttpsURLConnection.setSSLSocketFactory(HttpsURLConnection.java:357)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.getSSLConnection(AbstractTimelineMetricsSink.java:284)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findLiveCollectorHostsFromKnownCollector(AbstractTimelineMetricsSink.java:440)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.refreshCollectorsFromConfigured(AbstractTimelineMetricsSink.java:412)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:352)
> at
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.init(HadoopTimelineMetricsSink.java:110)
> at
> org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:199)
> ... 17 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19828) UI changes to resolve discrepancies between what the stack vs Ambari reports as "live" for NodeManagers
[ https://issues.apache.org/jira/browse/AMBARI-19828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850433#comment-15850433 ] Hudson commented on AMBARI-19828: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6632 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6632/]) AMBARI-19828. UI changes to resolve discrepancies between what the stack (yusaku: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=69c8389ef8d76e8a7a41a8a796f51be044033026]) * (edit) ambari-web/test/views/main/service/services/yarn_test.js * (edit) ambari-web/test/views/main/service/services/hdfs_test.js * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/views/main/service/services/yarn.js * (edit) ambari-web/app/views/main/service/services/hdfs.js > UI changes to resolve discrepancies between what the stack vs Ambari reports > as "live" for NodeManagers > --- > > Key: AMBARI-19828 > URL: https://issues.apache.org/jira/browse/AMBARI-19828 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19828.v0.branch-2.5.patch, > AMBARI-19828.v0.trunk.patch > > > Looks like the changes in https://issues.apache.org/jira/browse/AMBARI-9418 > was meant to be applied to YARN summary / NodeManagers as well, but that is > not happening. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19319) Disable auto start before RU/EU and enable during finalization phase
[
https://issues.apache.org/jira/browse/AMBARI-19319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850401#comment-15850401
]
Hadoop QA commented on AMBARI-19319:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12850670/AMBARI-19319.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10388//console
This message is automatically generated.
> Disable auto start before RU/EU and enable during finalization phase
>
>
> Key: AMBARI-19319
> URL: https://issues.apache.org/jira/browse/AMBARI-19319
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19319.patch
>
>
> Add the API calls to disable/enable auto start and assign it to the UI team
> to make the changes as part of RU/EU orchestration.
> Lets see if we can also design an alert that WARNs when autostart is disabled
> - especially if it was disabled due to EU/RU.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19829) Several HDFS/YARN widgets on Heatmaps show N/A
[ https://issues.apache.org/jira/browse/AMBARI-19829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-19829: - Component/s: (was: ambari-server) ambari-metrics > Several HDFS/YARN widgets on Heatmaps show N/A > -- > > Key: AMBARI-19829 > URL: https://issues.apache.org/jira/browse/AMBARI-19829 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-19829.patch > > > The following HDFS/YARN widgets on Heatmaps show N/A: > 1. HDFS - HDFS Bytes Written, HDFS Bytes Read, DataNode Process Disk I/O > Utilization, and DataNode Process Network I/O Utilization > 2. YARN - Container Failures > The issue was introduced by AMBARI-15835 "Rate metrics requesting widgets do > not show up on Ambari" which introduced rate metrics and applied rate metrics > to several HBASE/HDFS/YARN widgets on Summary pages as well as Heatmap > pages. Rate metrics work fine on Summary pages but they don't work on Heatmap > pages because current Heatmap design can only show point-in-time metrics and > rate metrics need a time range. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19813) findLatestServiceConfigsByStack query returns deleted config group
[ https://issues.apache.org/jira/browse/AMBARI-19813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850386#comment-15850386 ] Amruta Borkar commented on AMBARI-19813: Test failures don't seem to be related to the patch. > findLatestServiceConfigsByStack query returns deleted config group > -- > > Key: AMBARI-19813 > URL: https://issues.apache.org/jira/browse/AMBARI-19813 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-19813.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19824) Add consistency checker for blueprint tables
[ https://issues.apache.org/jira/browse/AMBARI-19824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-19824: Description: Additional check for topolgy tables: check that for each row in topology_request there is at least one row in topology_logical_request, topology_host_request, topology_host_task, topology_logical_task. was:Check the we have at least 1 or more rows in topology_logical_task for each topology_request through those joins: topology_request --> topology_logical_request --> topology_host_request --> topology_host_task --> topology_logical_task. > Add consistency checker for blueprint tables > > > Key: AMBARI-19824 > URL: https://issues.apache.org/jira/browse/AMBARI-19824 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Sandor Magyari >Assignee: Sandor Magyari >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19824.patch > > > Additional check for topolgy tables: check that for each row in > topology_request there is at least one row in topology_logical_request, > topology_host_request, topology_host_task, topology_logical_task. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19824) Add consistency checker for blueprint tables
[ https://issues.apache.org/jira/browse/AMBARI-19824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-19824: Attachment: AMBARI-19824.patch > Add consistency checker for blueprint tables > > > Key: AMBARI-19824 > URL: https://issues.apache.org/jira/browse/AMBARI-19824 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Sandor Magyari >Assignee: Sandor Magyari >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19824.patch > > > Check the we have at least 1 or more rows in topology_logical_task for each > topology_request through those joins: topology_request --> > topology_logical_request --> topology_host_request --> topology_host_task --> > topology_logical_task. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19824) Add consistency checker for blueprint tables
[ https://issues.apache.org/jira/browse/AMBARI-19824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-19824: Status: Patch Available (was: Open) > Add consistency checker for blueprint tables > > > Key: AMBARI-19824 > URL: https://issues.apache.org/jira/browse/AMBARI-19824 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Sandor Magyari >Assignee: Sandor Magyari >Priority: Critical > Fix For: 2.5.0 > > > Check the we have at least 1 or more rows in topology_logical_task for each > topology_request through those joins: topology_request --> > topology_logical_request --> topology_host_request --> topology_host_task --> > topology_logical_task. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-19854) Download all client configs doesnt contain all files for zookeeper client
[ https://issues.apache.org/jira/browse/AMBARI-19854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly reassigned AMBARI-19854: - Assignee: Jaimin Jetly > Download all client configs doesnt contain all files for zookeeper client > - > > Key: AMBARI-19854 > URL: https://issues.apache.org/jira/browse/AMBARI-19854 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran >Assignee: Jaimin Jetly > Fix For: 2.5.0 > > > Ambari-2.5.- introduced an option to download all client configs in one go. > Upon checking the content of downloaded tar and the conf file location at the > backend, ZOOKEEPER_CLIENT doesnt have all configs in the tar file. > /etc/zookeeper/conf has zoo.cfg whereas downloaded content has only > log4j.properties and zookeeper-env.sh -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19319) Disable auto start before RU/EU and enable during finalization phase
[ https://issues.apache.org/jira/browse/AMBARI-19319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850350#comment-15850350 ] Andrii Tkach commented on AMBARI-19319: --- updated patch committed to trunk and branch-2.5 > Disable auto start before RU/EU and enable during finalization phase > > > Key: AMBARI-19319 > URL: https://issues.apache.org/jira/browse/AMBARI-19319 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19319.patch > > > Add the API calls to disable/enable auto start and assign it to the UI team > to make the changes as part of RU/EU orchestration. > Lets see if we can also design an alert that WARNs when autostart is disabled > - especially if it was disabled due to EU/RU. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19855) Stack advisor issues encountered
[
https://issues.apache.org/jira/browse/AMBARI-19855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850349#comment-15850349
]
Hadoop QA commented on AMBARI-19855:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12850661/AMBARI-19855.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10387//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10387//console
This message is automatically generated.
> Stack advisor issues encountered
>
>
> Key: AMBARI-19855
> URL: https://issues.apache.org/jira/browse/AMBARI-19855
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
> Environment: 1. A default setting that did not hold so many cores in
> reserve. 20% seems very high.
> 2. This setting should be validated to flag when an impossible setting has
> been configured, specifically when the number of configured virtual cores is
> greater than actual number of cores it should be flagged.
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.5.0
>
> Attachments: AMBARI-19855.patch
>
>
> 1. A default setting that did not hold so many cores in reserve. 20% seems
> very high.
> 2. This setting should be validated to flag when an impossible setting has
> been configured, specifically when the number of configured virtual cores is
> greater than actual number of cores it should be flagged.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19319) Disable auto start before RU/EU and enable during finalization phase
[ https://issues.apache.org/jira/browse/AMBARI-19319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19319: -- Attachment: (was: AMBARI-19319.patch) > Disable auto start before RU/EU and enable during finalization phase > > > Key: AMBARI-19319 > URL: https://issues.apache.org/jira/browse/AMBARI-19319 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19319.patch > > > Add the API calls to disable/enable auto start and assign it to the UI team > to make the changes as part of RU/EU orchestration. > Lets see if we can also design an alert that WARNs when autostart is disabled > - especially if it was disabled due to EU/RU. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19319) Disable auto start before RU/EU and enable during finalization phase
[ https://issues.apache.org/jira/browse/AMBARI-19319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19319: -- Attachment: AMBARI-19319.patch > Disable auto start before RU/EU and enable during finalization phase > > > Key: AMBARI-19319 > URL: https://issues.apache.org/jira/browse/AMBARI-19319 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19319.patch > > > Add the API calls to disable/enable auto start and assign it to the UI team > to make the changes as part of RU/EU orchestration. > Lets see if we can also design an alert that WARNs when autostart is disabled > - especially if it was disabled due to EU/RU. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19319) Disable auto start before RU/EU and enable during finalization phase
[ https://issues.apache.org/jira/browse/AMBARI-19319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19319: -- Status: Patch Available (was: Reopened) > Disable auto start before RU/EU and enable during finalization phase > > > Key: AMBARI-19319 > URL: https://issues.apache.org/jira/browse/AMBARI-19319 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19319.patch > > > Add the API calls to disable/enable auto start and assign it to the UI team > to make the changes as part of RU/EU orchestration. > Lets see if we can also design an alert that WARNs when autostart is disabled > - especially if it was disabled due to EU/RU. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19319) Disable auto start before RU/EU and enable during finalization phase
[ https://issues.apache.org/jira/browse/AMBARI-19319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-19319: -- Attachment: AMBARI-19319.patch > Disable auto start before RU/EU and enable during finalization phase > > > Key: AMBARI-19319 > URL: https://issues.apache.org/jira/browse/AMBARI-19319 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19319.patch > > > Add the API calls to disable/enable auto start and assign it to the UI team > to make the changes as part of RU/EU orchestration. > Lets see if we can also design an alert that WARNs when autostart is disabled > - especially if it was disabled due to EU/RU. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19746) Ambari HDFS Metric alerts turns to UNKNOWN status with error "argument of type 'NoneType' is not iterable"
[
https://issues.apache.org/jira/browse/AMBARI-19746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850335#comment-15850335
]
Hudson commented on AMBARI-19746:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6631 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6631/])
AMBARI-19746 Ambari HDFS Metric alerts turns to UNKNOWN status with (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5d4d99efbd1a7de059c1257c09b396b90bade83e])
* (edit) ambari-agent/src/main/python/ambari_agent/ActionQueue.py
* (edit) ambari-common/src/main/python/ambari_commons/ambari_metrics_helper.py
> Ambari HDFS Metric alerts turns to UNKNOWN status with error "argument of
> type 'NoneType' is not iterable"
> --
>
> Key: AMBARI-19746
> URL: https://issues.apache.org/jira/browse/AMBARI-19746
> Project: Ambari
> Issue Type: Bug
> Components: alerts
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19746_2.patch, AMBARI-19746.patch
>
>
> Build used : ambari-2.5.0.0-724
> Test is updating the alert definition minimumValue to "0.0".
> Payload used to update the minimumValue
> {code:java}
> /{
> "AlertDefinition": {
> "cluster_name": "cl1",
> "id": 81,
> "name": "increase_nn_heap_usage_daily",
> "label": "NameNode Heap Usage (Daily)",
> "component_name": "NAMENODE",
> "description": "This service-level alert is triggered if the
> NameNode heap usage deviation has grown beyond the specified threshold within
> a day period.",
> "enabled": true,
> "ignore_host": false,
> "interval": 1,
> "scope": "ANY",
> "service_name": "HDFS",
> "source": {
> "parameters": [{
> "name": "mergeHaMetrics",
> "display_name": "Whether active and stanby
> NameNodes metrics should be merged",
> "value": "false",
> "description": "Whether active and stanby
> NameNodes metrics should be merged.",
> "type": "STRING",
> "visibility": "HIDDEN"
> }, {
> "name": "interval",
> "display_name": "Time interval in minutes",
> "value": "1440.0",
> "description": "Time interval in minutes.",
> "type": "NUMERIC",
> "visibility": "HIDDEN"
> }, {
> "name": "appId",
> "display_name": "AMS application id",
> "value": "NAMENODE",
> "description": "The application id used to
> retrieve the metric.",
> "type": "STRING",
> "visibility": "HIDDEN"
> }, {
> "name": "metricName",
> "display_name": "Metric Name",
> "value": "jvm.JvmMetrics.MemHeapUsedM",
> "description": "The metric to monitor.",
> "type": "STRING",
> "visibility": "HIDDEN"
> }, {
> "name": "metric.deviation.warning.threshold",
> "display_name": "Growth Rate",
> "value": "20.0",
> "description": "The percentage of NameNode heap
> usage growth.",
> "type": "PERCENT"
> }, {
> "name": "metric.deviation.critical.threshold",
> "display_name": "Growth Rate",
> "value": "50.0",
> "description": "The percentage of NameNode heap
> usage growth.",
> "type": "PERCENT"
> }, {
> "name": "metric.units",
> "display_name": "Metric Units",
> "value": "MB",
> "description": "The units that the metric data
> points are reported in.",
> "type": "STRING",
> "visibility": "HIDDEN"
> }, {
>
[jira] [Commented] (AMBARI-19800) Add precheck for Auto-Start being disabled
[ https://issues.apache.org/jira/browse/AMBARI-19800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850336#comment-15850336 ] Hudson commented on AMBARI-19800: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6631 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6631/]) AMBARI-19800. Add precheck for Auto-Start being disabled (ncole) (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f297c48f016c9deab2cf423fab3a87948496682b]) * (add) ambari-server/src/test/java/org/apache/ambari/server/checks/AutoStartDisabledCheckTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/CheckDescription.java * (add) ambari-server/src/main/java/org/apache/ambari/server/checks/AutoStartDisabledCheck.java > Add precheck for Auto-Start being disabled > -- > > Key: AMBARI-19800 > URL: https://issues.apache.org/jira/browse/AMBARI-19800 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.5.0 > > > A new precheck is required to make sure that auto-start is disabled before > starting an upgrade. This JIRA covers the backend requirements. The UI > changes will be linked to this one. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19825) Metrics data is not getting collected for different services when AMS HTTPS is enabled
[
https://issues.apache.org/jira/browse/AMBARI-19825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850328#comment-15850328
]
Hudson commented on AMBARI-19825:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #889 (See
[https://builds.apache.org/job/Ambari-branch-2.5/889/])
AMBARI-19825 : Metrics data is not getting collected for different (avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d2837f7864ddd0a961c1213761580576a772cedd])
* (edit)
ambari-metrics/ambari-metrics-hadoop-sink/src/main/java/org/apache/hadoop/metrics2/sink/timeline/HadoopTimelineMetricsSink.java
* (edit)
ambari-metrics/ambari-metrics-flume-sink/src/main/java/org/apache/hadoop/metrics2/sink/flume/FlumeTimelineMetricsSink.java
* (edit)
ambari-metrics/ambari-metrics-storm-sink/src/main/java/org/apache/hadoop/metrics2/sink/storm/StormTimelineMetricsReporter.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/AmbariMetricSinkImpl.java
> Metrics data is not getting collected for different services when AMS HTTPS
> is enabled
> --
>
> Key: AMBARI-19825
> URL: https://issues.apache.org/jira/browse/AMBARI-19825
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19825-2.5.patch, AMBARI-19825-trunk.patch
>
>
> {code}
> org.apache.hadoop.metrics2.impl.MetricsConfigException: Error creating
> plugin: org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink
> at
> org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:203)
> at
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.newSink(MetricsSystemImpl.java:529)
> at
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configureSinks(MetricsSystemImpl.java:501)
> at
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configure(MetricsSystemImpl.java:480)
> at
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.start(MetricsSystemImpl.java:189)
> at
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.init(MetricsSystemImpl.java:164)
> at
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.init(DefaultMetricsSystem.java:54)
> at
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.initialize(DefaultMetricsSystem.java:50)
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.makeInstance(DataNode.java:2530)
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:2435)
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.createDataNode(DataNode.java:2482)
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.secureMain(DataNode.java:2622)
> at
> org.apache.hadoop.hdfs.server.datanode.SecureDataNodeStarter.start(SecureDataNodeStarter.java:77)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243)
> Caused by: java.lang.IllegalArgumentException: no SSLSocketFactory specified
> at
> javax.net.ssl.HttpsURLConnection.setSSLSocketFactory(HttpsURLConnection.java:357)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.getSSLConnection(AbstractTimelineMetricsSink.java:284)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findLiveCollectorHostsFromKnownCollector(AbstractTimelineMetricsSink.java:440)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.refreshCollectorsFromConfigured(AbstractTimelineMetricsSink.java:412)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:352)
> at
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.init(HadoopTimelineMetricsSink.java:110)
> at
> org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:199)
> ... 17 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19746) Ambari HDFS Metric alerts turns to UNKNOWN status with error "argument of type 'NoneType' is not iterable"
[
https://issues.apache.org/jira/browse/AMBARI-19746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850327#comment-15850327
]
Hudson commented on AMBARI-19746:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #889 (See
[https://builds.apache.org/job/Ambari-branch-2.5/889/])
AMBARI-19746 Ambari HDFS Metric alerts turns to UNKNOWN status with (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c5ed48d798cb97b6573589f6eb3d280b1c5d48de])
* (edit) ambari-common/src/main/python/ambari_commons/ambari_metrics_helper.py
* (edit) ambari-agent/src/main/python/ambari_agent/ActionQueue.py
> Ambari HDFS Metric alerts turns to UNKNOWN status with error "argument of
> type 'NoneType' is not iterable"
> --
>
> Key: AMBARI-19746
> URL: https://issues.apache.org/jira/browse/AMBARI-19746
> Project: Ambari
> Issue Type: Bug
> Components: alerts
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19746_2.patch, AMBARI-19746.patch
>
>
> Build used : ambari-2.5.0.0-724
> Test is updating the alert definition minimumValue to "0.0".
> Payload used to update the minimumValue
> {code:java}
> /{
> "AlertDefinition": {
> "cluster_name": "cl1",
> "id": 81,
> "name": "increase_nn_heap_usage_daily",
> "label": "NameNode Heap Usage (Daily)",
> "component_name": "NAMENODE",
> "description": "This service-level alert is triggered if the
> NameNode heap usage deviation has grown beyond the specified threshold within
> a day period.",
> "enabled": true,
> "ignore_host": false,
> "interval": 1,
> "scope": "ANY",
> "service_name": "HDFS",
> "source": {
> "parameters": [{
> "name": "mergeHaMetrics",
> "display_name": "Whether active and stanby
> NameNodes metrics should be merged",
> "value": "false",
> "description": "Whether active and stanby
> NameNodes metrics should be merged.",
> "type": "STRING",
> "visibility": "HIDDEN"
> }, {
> "name": "interval",
> "display_name": "Time interval in minutes",
> "value": "1440.0",
> "description": "Time interval in minutes.",
> "type": "NUMERIC",
> "visibility": "HIDDEN"
> }, {
> "name": "appId",
> "display_name": "AMS application id",
> "value": "NAMENODE",
> "description": "The application id used to
> retrieve the metric.",
> "type": "STRING",
> "visibility": "HIDDEN"
> }, {
> "name": "metricName",
> "display_name": "Metric Name",
> "value": "jvm.JvmMetrics.MemHeapUsedM",
> "description": "The metric to monitor.",
> "type": "STRING",
> "visibility": "HIDDEN"
> }, {
> "name": "metric.deviation.warning.threshold",
> "display_name": "Growth Rate",
> "value": "20.0",
> "description": "The percentage of NameNode heap
> usage growth.",
> "type": "PERCENT"
> }, {
> "name": "metric.deviation.critical.threshold",
> "display_name": "Growth Rate",
> "value": "50.0",
> "description": "The percentage of NameNode heap
> usage growth.",
> "type": "PERCENT"
> }, {
> "name": "metric.units",
> "display_name": "Metric Units",
> "value": "MB",
> "description": "The units that the metric data
> points are reported in.",
> "type": "STRING",
> "visibility": "HIDDEN"
> }, {
>
[jira] [Commented] (AMBARI-19849) Recent workflows in Workflow designer should be in descending order of time of updation
[
https://issues.apache.org/jira/browse/AMBARI-19849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850296#comment-15850296
]
Hadoop QA commented on AMBARI-19849:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12850644/AMBARI-19849_branch-2.5.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10386//console
This message is automatically generated.
> Recent workflows in Workflow designer should be in descending order of time
> of updation
> ---
>
> Key: AMBARI-19849
> URL: https://issues.apache.org/jira/browse/AMBARI-19849
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: venkat
>Assignee: venkat
> Fix For: 2.5.0
>
> Attachments: AMBARI-19849_branch-2.5.patch
>
>
> Recent workflows in Workflow designer should be in descending order of
> updated_at field both in recent list as well as Recent Projects screen.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19768) Package Installation fails due to error in Berkeley DB library
[
https://issues.apache.org/jira/browse/AMBARI-19768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850290#comment-15850290
]
Hadoop QA commented on AMBARI-19768:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12850651/AMBARI-19768.1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-agent.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10385//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10385//console
This message is automatically generated.
> Package Installation fails due to error in Berkeley DB library
> --
>
> Key: AMBARI-19768
> URL: https://issues.apache.org/jira/browse/AMBARI-19768
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19768.1.patch, AMBARI-19768.patch
>
>
> *Steps*
> # Deploy HDP-2.5.0.0 with Ambari 2.4.1.0
> # Upgrade ambari to 2.5.0.0-481 (I did not register Falcon library, as the
> jar was already present in /var/lib/ambari-server/resources/je-5.0.73.jar on
> Ambari server node)
> # Register HDP-2.6.0.0-216
> # Start package installation
> *Result:*
> Got below errors:
> {code}
> 2016-12-16 13:47:10,419|INFO|MainThread|machine.py:145 -
> run()|CRITICAL:yum.main:
> 2016-12-16 13:47:10,419|INFO|MainThread|machine.py:145 - run()|
> 2016-12-16 13:47:10,419|INFO|MainThread|machine.py:145 - run()|Error: rpmdb
> open failed
> 2016-12-16 13:47:10,420|INFO|MainThread|machine.py:145 - run()|Traceback
> (most recent call last):
> 2016-12-16 13:47:10,420|INFO|MainThread|machine.py:145 - run()|File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 166, in actionexecute
> 2016-12-16 13:47:10,420|INFO|MainThread|machine.py:145 - run()|ret_code =
> self.install_packages(package_list)
> 2016-12-16 13:47:10,420|INFO|MainThread|machine.py:145 - run()|File
> "/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
> line 400, in install_packages
> 2016-12-16 13:47:10,420|INFO|MainThread|machine.py:145 - run()|if not
> verifyDependencies():
> 2016-12-16 13:47:10,421|INFO|MainThread|machine.py:145 - run()|File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/packages_analyzer.py",
> line 311, in verifyDependencies
> 2016-12-16 13:47:10,421|INFO|MainThread|machine.py:145 - run()|code, out =
> rmf_shell.checked_call(cmd, sudo=True)
> 2016-12-16 13:47:10,421|INFO|MainThread|machine.py:145 - run()|File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 72, in inner
> 2016-12-16 13:47:10,421|INFO|MainThread|machine.py:145 - run()|result =
> function(command, **kwargs)
> 2016-12-16 13:47:10,421|INFO|MainThread|machine.py:145 - run()|File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 102, in checked_call
> 2016-12-16 13:47:10,422|INFO|MainThread|machine.py:145 - run()|tries=tries,
> try_sleep=try_sleep, timeout_kill_strategy=timeout_kill_strategy)
> 2016-12-16 13:47:10,422|INFO|MainThread|machine.py:145 - run()|File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 150, in _call_wrapper
> 2016-12-16 13:47:10,422|INFO|MainThread|machine.py:145 - run()|result =
> _call(command, **kwargs_copy)
> 2016-12-16 13:47:10,422|INFO|MainThread|machine.py:145 - run()|File
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line
> 303, in _call
> 2016-12-16 13:47:10,423|INFO|MainThread|machine.py:145 - run()|raise
> ExecutionFailed(err_msg, code, out, err)
> 2016-12-16 13:47:10,423|INFO|MainThread|machine.py:145 -
> run()|ExecutionFailed: Execution of '/usr/bin/yum -d 0 -e 0 check
> dependencies' returned 1. error: rpmdb: BDB0113 Thread/process
> 16016/139791567193920 failed: BDB1507 Thread died in Berkeley DB library
> 2016-12-16 13:47:10,424|INFO|MainThread|machine.py:145 - run()|error: db5
> error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run
> database recovery
> 2016-12-16 13:47:10,424|INFO|MainThread|machine.py:145 - run()
[jira] [Updated] (AMBARI-19828) UI changes to resolve discrepancies between what the stack vs Ambari reports as "live" for NodeManagers
[ https://issues.apache.org/jira/browse/AMBARI-19828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-19828: - Resolution: Fixed Status: Resolved (was: Patch Available) > UI changes to resolve discrepancies between what the stack vs Ambari reports > as "live" for NodeManagers > --- > > Key: AMBARI-19828 > URL: https://issues.apache.org/jira/browse/AMBARI-19828 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19828.v0.branch-2.5.patch, > AMBARI-19828.v0.trunk.patch > > > Looks like the changes in https://issues.apache.org/jira/browse/AMBARI-9418 > was meant to be applied to YARN summary / NodeManagers as well, but that is > not happening. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19828) UI changes to resolve discrepancies between what the stack vs Ambari reports as "live" for NodeManagers
[ https://issues.apache.org/jira/browse/AMBARI-19828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850289#comment-15850289 ] Yusaku Sako commented on AMBARI-19828: -- +1'd on ReviewBoard. Committed to trunk and branch-2.5. > UI changes to resolve discrepancies between what the stack vs Ambari reports > as "live" for NodeManagers > --- > > Key: AMBARI-19828 > URL: https://issues.apache.org/jira/browse/AMBARI-19828 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19828.v0.branch-2.5.patch, > AMBARI-19828.v0.trunk.patch > > > Looks like the changes in https://issues.apache.org/jira/browse/AMBARI-9418 > was meant to be applied to YARN summary / NodeManagers as well, but that is > not happening. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19825) Metrics data is not getting collected for different services when AMS HTTPS is enabled
[
https://issues.apache.org/jira/browse/AMBARI-19825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-19825:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to branch-2.5 and trunk.
> Metrics data is not getting collected for different services when AMS HTTPS
> is enabled
> --
>
> Key: AMBARI-19825
> URL: https://issues.apache.org/jira/browse/AMBARI-19825
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.5.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-19825-2.5.patch, AMBARI-19825-trunk.patch
>
>
> {code}
> org.apache.hadoop.metrics2.impl.MetricsConfigException: Error creating
> plugin: org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink
> at
> org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:203)
> at
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.newSink(MetricsSystemImpl.java:529)
> at
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configureSinks(MetricsSystemImpl.java:501)
> at
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.configure(MetricsSystemImpl.java:480)
> at
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.start(MetricsSystemImpl.java:189)
> at
> org.apache.hadoop.metrics2.impl.MetricsSystemImpl.init(MetricsSystemImpl.java:164)
> at
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.init(DefaultMetricsSystem.java:54)
> at
> org.apache.hadoop.metrics2.lib.DefaultMetricsSystem.initialize(DefaultMetricsSystem.java:50)
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.makeInstance(DataNode.java:2530)
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.instantiateDataNode(DataNode.java:2435)
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.createDataNode(DataNode.java:2482)
> at
> org.apache.hadoop.hdfs.server.datanode.DataNode.secureMain(DataNode.java:2622)
> at
> org.apache.hadoop.hdfs.server.datanode.SecureDataNodeStarter.start(SecureDataNodeStarter.java:77)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243)
> Caused by: java.lang.IllegalArgumentException: no SSLSocketFactory specified
> at
> javax.net.ssl.HttpsURLConnection.setSSLSocketFactory(HttpsURLConnection.java:357)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.getSSLConnection(AbstractTimelineMetricsSink.java:284)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findLiveCollectorHostsFromKnownCollector(AbstractTimelineMetricsSink.java:440)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.refreshCollectorsFromConfigured(AbstractTimelineMetricsSink.java:412)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:352)
> at
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.init(HadoopTimelineMetricsSink.java:110)
> at
> org.apache.hadoop.metrics2.impl.MetricsConfig.getPlugin(MetricsConfig.java:199)
> ... 17 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19821) Recommendations for non-editable properties should be listed as 'Required Changes'
[ https://issues.apache.org/jira/browse/AMBARI-19821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-19821: - Resolution: Fixed Status: Resolved (was: Patch Available) UT failures above are not related to the patch. > Recommendations for non-editable properties should be listed as 'Required > Changes' > -- > > Key: AMBARI-19821 > URL: https://issues.apache.org/jira/browse/AMBARI-19821 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19821_branch-2.5.patch, AMBARI-19821_trunk.patch > > > As result of configs recommendation API call, the changes to be made are > displayed in popup, so that user can discard some of them. There should be no > discard ability for non-editable properties. > The above is correct for delete service popup, service configs page and > 'configure services' wizard step. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
