[jira] [Commented] (AMBARI-16677) Sticky bit keeps getting changed back to 777 after restart causing security checks to fail
[
https://issues.apache.org/jira/browse/AMBARI-16677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284208#comment-15284208
]
Hadoop QA commented on AMBARI-16677:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12804114/AMBARI-16677.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 2 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/6853//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6853//console
This message is automatically generated.
> Sticky bit keeps getting changed back to 777 after restart causing security
> checks to fail
> --
>
> Key: AMBARI-16677
> URL: https://issues.apache.org/jira/browse/AMBARI-16677
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-16677.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16677) Sticky bit keeps getting changed back to 777 after restart causing security checks to fail
[ https://issues.apache.org/jira/browse/AMBARI-16677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-16677: - Status: Patch Available (was: Open) > Sticky bit keeps getting changed back to 777 after restart causing security > checks to fail > -- > > Key: AMBARI-16677 > URL: https://issues.apache.org/jira/browse/AMBARI-16677 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-16677.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16677) Sticky bit keeps getting changed back to 777 after restart causing security checks to fail
Andrew Onischuk created AMBARI-16677: Summary: Sticky bit keeps getting changed back to 777 after restart causing security checks to fail Key: AMBARI-16677 URL: https://issues.apache.org/jira/browse/AMBARI-16677 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.4.0 Attachments: AMBARI-16677.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16677) Sticky bit keeps getting changed back to 777 after restart causing security checks to fail
[ https://issues.apache.org/jira/browse/AMBARI-16677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-16677: - Attachment: AMBARI-16677.patch > Sticky bit keeps getting changed back to 777 after restart causing security > checks to fail > -- > > Key: AMBARI-16677 > URL: https://issues.apache.org/jira/browse/AMBARI-16677 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.4.0 > > Attachments: AMBARI-16677.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-15612) Add Livy to HDP 2.5 as slave component of Spark
[ https://issues.apache.org/jira/browse/AMBARI-15612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya reopened AMBARI-15612: > Add Livy to HDP 2.5 as slave component of Spark > --- > > Key: AMBARI-15612 > URL: https://issues.apache.org/jira/browse/AMBARI-15612 > Project: Ambari > Issue Type: New Feature >Reporter: Jeff Zhang >Assignee: Jeff Zhang > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15612) Add Livy to HDP 2.5 as slave component of Spark
[ https://issues.apache.org/jira/browse/AMBARI-15612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284185#comment-15284185 ] Jayush Luniya commented on AMBARI-15612: Reverted patch as Blueprint deployments are failing. Trunk commit 0e6e4d21d5d30305048b603897d54677a9bb94e9 Author: Jayush Luniya Date: Sun May 15 23:15:58 2016 -0700 Revert "AMBARI-15612: Add Livy to HDP 2.5 as slave component of Spark (Jeff Zhang via jluniya)" This reverts commit 4e272347441918c0f7ef0010f1530eeceb9187f4. Branch-2.4 commit c41a1eb12fc796de4348f2b52a3ca6590f2dc39c Author: Jayush Luniya Date: Sun May 15 23:18:07 2016 -0700 Revert "AMBARI-15612: Add Livy to HDP 2.5 as slave component of Spark (Jeff Zhang via jluniya)" This reverts commit 26452312acb83d03fd496c6b80b9cafedfafd54d. > Add Livy to HDP 2.5 as slave component of Spark > --- > > Key: AMBARI-15612 > URL: https://issues.apache.org/jira/browse/AMBARI-15612 > Project: Ambari > Issue Type: New Feature >Reporter: Jeff Zhang >Assignee: Jeff Zhang > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-16668) Create RANGER service versions in common-services
[ https://issues.apache.org/jira/browse/AMBARI-16668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-16668. Resolution: Fixed > Create RANGER service versions in common-services > - > > Key: AMBARI-16668 > URL: https://issues.apache.org/jira/browse/AMBARI-16668 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.4.0 > > > Create common-services/STORM/0.9.1 common-services/SOTRM/0.9.3 and > common-services/SOTRM/0.10.0 service versions and update HDP stack > inheritance to extend these service definitions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16668) Create RANGER service versions in common-services
[ https://issues.apache.org/jira/browse/AMBARI-16668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284184#comment-15284184 ] Jayush Luniya commented on AMBARI-16668: Branch-2.4 commit 02db3b2f6554a5e5d420554bea09cd52daccd4a0 Author: Jayush Luniya Date: Sun May 15 23:12:19 2016 -0700 AMBARI-16668: Create RANGER service versions in common-services (jluniya) > Create RANGER service versions in common-services > - > > Key: AMBARI-16668 > URL: https://issues.apache.org/jira/browse/AMBARI-16668 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.4.0 > > > Create common-services/STORM/0.9.1 common-services/SOTRM/0.9.3 and > common-services/SOTRM/0.10.0 service versions and update HDP stack > inheritance to extend these service definitions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16668) Create RANGER service versions in common-services
[ https://issues.apache.org/jira/browse/AMBARI-16668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284182#comment-15284182 ] Jayush Luniya commented on AMBARI-16668: Trunk commit ab2d40aa1f315671ac15ce0d64ec08ae38a337ed Author: Jayush Luniya Date: Sun May 15 23:12:19 2016 -0700 AMBARI-16668: Create RANGER service versions in common-services (jluniya) > Create RANGER service versions in common-services > - > > Key: AMBARI-16668 > URL: https://issues.apache.org/jira/browse/AMBARI-16668 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.4.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya > Fix For: 2.4.0 > > > Create common-services/STORM/0.9.1 common-services/SOTRM/0.9.3 and > common-services/SOTRM/0.10.0 service versions and update HDP stack > inheritance to extend these service definitions -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16676) Consistent logsearch/logfeeder property names
[ https://issues.apache.org/jira/browse/AMBARI-16676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-16676: --- Priority: Major (was: Minor) > Consistent logsearch/logfeeder property names > - > > Key: AMBARI-16676 > URL: https://issues.apache.org/jira/browse/AMBARI-16676 > Project: Ambari > Issue Type: Improvement > Components: ambari-logsearch >Affects Versions: trunk, 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-16676.patch > > > In the stack definition logsearch/logfeeder.properties looks like this: > "logsearch."/ "logfeeder." > Use the same names in logsearch module too -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15881) Mark primary log of the component
[
https://issues.apache.org/jira/browse/AMBARI-15881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miklos Gergely updated AMBARI-15881:
Attachment: AMBARI-15881_appendum.patch
My previous patch contained a superfluous, but mostly harmless additional 'h'
character in the YARN metainfo.xml file. Removing it with this patch.
[~oleewere], please commit it.
> Mark primary log of the component
> -
>
> Key: AMBARI-15881
> URL: https://issues.apache.org/jira/browse/AMBARI-15881
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
>Priority: Minor
> Fix For: 2.4.0
>
> Attachments: AMBARI-15881.patch, AMBARI-15881_appendum.patch
>
>
> Mark at most one log of a component as primary.
> In the metainfo.xml file the log will have a primary element in it with true
> value.
> Example:
> {code}
>
> NAMENODE
> NameNode
> MASTER
> 1-2
> true
>
>
> hdfs_namenode
> true
>
>
> hdfs_audit
>
>
> ...
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-16676) Consistent logsearch/logfeeder property names
[ https://issues.apache.org/jira/browse/AMBARI-16676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-16676: Status: Patch Available (was: Open) > Consistent logsearch/logfeeder property names > - > > Key: AMBARI-16676 > URL: https://issues.apache.org/jira/browse/AMBARI-16676 > Project: Ambari > Issue Type: Improvement > Components: ambari-logsearch >Affects Versions: trunk, 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Minor > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-16676.patch > > > In the stack definition logsearch/logfeeder.properties looks like this: > "logsearch."/ "logfeeder." > Use the same names in logsearch module too -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16676) Consistent logsearch/logfeeder property names
[ https://issues.apache.org/jira/browse/AMBARI-16676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-16676: Attachment: AMBARI-16676.patch > Consistent logsearch/logfeeder property names > - > > Key: AMBARI-16676 > URL: https://issues.apache.org/jira/browse/AMBARI-16676 > Project: Ambari > Issue Type: Improvement > Components: ambari-logsearch >Affects Versions: trunk, 2.4.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Minor > Fix For: trunk, 2.4.0 > > Attachments: AMBARI-16676.patch > > > In the stack definition logsearch/logfeeder.properties looks like this: > "logsearch."/ "logfeeder." > Use the same names in logsearch module too -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16642) After enabling ssl for Node Manager UI, some metrics on Node Manager Heatmaps show NA
[ https://issues.apache.org/jira/browse/AMBARI-16642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15283895#comment-15283895 ] Qin Liu commented on AMBARI-16642: -- Description: After enabling HTTPS for Node Manager UI, "NodeManager GC Time" and "NodeManager JVM Heap Memory Used" widgets on YARN Heatmaps show NA. Steps to reproduce: 1. install a cluster with default from Ambari Web UI. 2. configuring SSL for HDFS, YARN, and MapReduce. 3. enable HTTPS for YARN 1). Set the following properties in Advanced yarn-site from Ambari Web UI: yarn.http.policy=HTTPS_ONLY yarn.resourcemanager.webapp.https.address=:8090 2). Add the following property in Custom yarn-site from Ambari Web UI: yarn.nodemanager.webapp.https.address=0.0.0.0:8044 4. "NodeManager GC Time" and "NodeManager JVM Heap Memory Used" widgets on YARN Heatmaps show NA. > After enabling ssl for Node Manager UI, some metrics on Node Manager Heatmaps > show NA > - > > Key: AMBARI-16642 > URL: https://issues.apache.org/jira/browse/AMBARI-16642 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15106) Ambari should manage Sqoop metastore to facilitate incremental loads
[ https://issues.apache.org/jira/browse/AMBARI-15106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15283888#comment-15283888 ] simran commented on AMBARI-15106: - Would be very helpful. Infact I have not yet figured out a workaround for this. Would be great if someone could please share so. > Ambari should manage Sqoop metastore to facilitate incremental loads > > > Key: AMBARI-15106 > URL: https://issues.apache.org/jira/browse/AMBARI-15106 > Project: Ambari > Issue Type: Improvement >Reporter: Vlad > > Sqoop metastore is needed to enable incremental import jobs executed through > Oozie. This metastore should be managed (install/start/stop/monitor) by > Ambari. > Sqoop incremental import jobs require --last-value parameter. So that a > user doesn't have to remember the parameter after each Sqoop execution a > Sqoop job can be saved to the metastore where this parameter is remembered. > With out a central metastore Sqoop saves the data to $HOME/.sqoop/ and that > does not work when executing a Sqoop job from Oozie. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16676) Consistent logsearch/logfeeder property names
Miklos Gergely created AMBARI-16676: --- Summary: Consistent logsearch/logfeeder property names Key: AMBARI-16676 URL: https://issues.apache.org/jira/browse/AMBARI-16676 Project: Ambari Issue Type: Improvement Components: ambari-logsearch Affects Versions: trunk, 2.4.0 Reporter: Miklos Gergely Assignee: Miklos Gergely Priority: Minor Fix For: trunk, 2.4.0 In the stack definition logsearch/logfeeder.properties looks like this: "logsearch."/ "logfeeder." Use the same names in logsearch module too -- This message was sent by Atlassian JIRA (v6.3.4#6332)
