[jira] [Created] (AMBARI-18521) Ranger upgrade fix from stack 2.4 to 2.5 in secure env
Mugdha Varadkar created AMBARI-18521: Summary: Ranger upgrade fix from stack 2.4 to 2.5 in secure env Key: AMBARI-18521 URL: https://issues.apache.org/jira/browse/AMBARI-18521 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0, 2.4.1 Reporter: Mugdha Varadkar Assignee: Mugdha Varadkar Priority: Critical Fix For: 2.5.0, 2.4.2 Stack changes required while upgrading to 2.4 in secure env * Remove adding spnego principal value to ranger-admin-site/ranger.spnego.kerberos.principal * Calculate storm principal and update it accordingly -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18245) Upgrade node to version 4.x
[
https://issues.apache.org/jira/browse/AMBARI-18245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544291#comment-15544291
]
Hadoop QA commented on AMBARI-18245:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831417/AMBARI-18245.v0.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8799//console
This message is automatically generated.
> Upgrade node to version 4.x
> ---
>
> Key: AMBARI-18245
> URL: https://issues.apache.org/jira/browse/AMBARI-18245
> Project: Ambari
> Issue Type: Task
> Components: ambari-admin, ambari-views, ambari-web
>Affects Versions: trunk
>Reporter: Yusaku Sako
>Assignee: Zhe (Joe) Wang
> Fix For: trunk
>
> Attachments: AMBARI-18245.v0.patch
>
>
> We are currently using 0.10, which is very old and going EOL 2016-10-01:
> https://github.com/nodejs/LTS
> We should look into upgrading to Node 4.x:
> * Upgrade Node on Ambari Web
> * Upgrade Node on Ambari Admin
> * Upgrade Node on contrib/views/* modules
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18518) Sinks should not try to read collector hosts from Zk if AMS is in embedded mode
[
https://issues.apache.org/jira/browse/AMBARI-18518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544276#comment-15544276
]
Hadoop QA commented on AMBARI-18518:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831418/AMBARI-18518.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-metrics/ambari-metrics-common.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8798//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8798//console
This message is automatically generated.
> Sinks should not try to read collector hosts from Zk if AMS is in embedded
> mode
> ---
>
> Key: AMBARI-18518
> URL: https://issues.apache.org/jira/browse/AMBARI-18518
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 3.0.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18518.patch
>
>
> Currently, an exception is constantly being thrown in sink logs.
> {code}
> 2016-10-03 21:01:06,537 WARN availability.MetricCollectorHAHelper
> (MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(91)) - Unable
> to connect to z
> ookeeper.
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException$ConnectionLossException:
> KeeperErrorCode = ConnectionLoss for /ambari-metrics-cluster
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException.create(KeeperException.java:99)
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException.create(KeeperException.java:51)
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.ZooKeeper.exists(ZooKeeper.java:1045)
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.ZooKeeper.exists(ZooKeeper.java:1073)
> at
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper.findLiveCollectorHostsFromZNode(MetricCollectorHAHelper.java:78)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:344)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.emitMetrics(AbstractTimelineMetricsSink.java:216)
> at
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.putMetrics(HadoopTimelineMetricsSink.java:345)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:186)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
> at
> org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:134)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
> {code}
> After the change
> {code}
> 2016-10-03 21:08:31,494 INFO availability.MetricCollectorHAHelper
> (MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(80)) -
> /ambari-metrics-cluster znode does not exist. Skipping requesting live
> instances from zookeeper
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18519) Enable Add/Remove JournalNode on NNHA Wizard Step 2
[
https://issues.apache.org/jira/browse/AMBARI-18519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544246#comment-15544246
]
Hadoop QA commented on AMBARI-18519:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831423/AMBARI-18519.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8797//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8797//console
This message is automatically generated.
> Enable Add/Remove JournalNode on NNHA Wizard Step 2
> ---
>
> Key: AMBARI-18519
> URL: https://issues.apache.org/jira/browse/AMBARI-18519
> 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-18519.patch
>
>
> Enable Add/Remove JournalNode on NNHA Wizard Step 2
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18517) Changes in upgrade path for Kafka metrics collector hosts config
[ https://issues.apache.org/jira/browse/AMBARI-18517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544176#comment-15544176 ] Siddharth Wagle commented on AMBARI-18517: -- +1 LGTM > Changes in upgrade path for Kafka metrics collector hosts config > > > Key: AMBARI-18517 > URL: https://issues.apache.org/jira/browse/AMBARI-18517 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 3.0.0 > > Attachments: AMBARI-18517.patch, Screen Shot 2016-08-22 at 11.00.37 > AM.png > > > Config change for Kafka was added through AMBARI-18170 (Seen in attached > screensot). This jira is used to track Upgrade path changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18520) Ambari usernames should not be converted to lowercase before storing in the DB.
[ https://issues.apache.org/jira/browse/AMBARI-18520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18520: --- Summary: Ambari usernames should not be converted to lowercase before storing in the DB. (was: Ambari usernames should not be stored in lowercase in the DB.) > Ambari usernames should not be converted to lowercase before storing in the > DB. > --- > > Key: AMBARI-18520 > URL: https://issues.apache.org/jira/browse/AMBARI-18520 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram >Priority: Critical > Fix For: 2.4.2 > > > AMBARI-17383 searches the username in a case-insensitive way but introduced a > regression by storing the usernames in lowercase in the DB. Usernames should > be stored as-is. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18520) Ambari usernames should not be stored in lowercase in the DB.
Nahappan Somasundaram created AMBARI-18520: -- Summary: Ambari usernames should not be stored in lowercase in the DB. Key: AMBARI-18520 URL: https://issues.apache.org/jira/browse/AMBARI-18520 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Nahappan Somasundaram Assignee: Nahappan Somasundaram Priority: Critical Fix For: 2.4.2 AMBARI-17383 searches the username in a case-insensitive way but introduced a regression by storing the usernames in lowercase in the DB. Usernames should be stored as-is. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18496) Include an option to download the saved query in hive view
[
https://issues.apache.org/jira/browse/AMBARI-18496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544133#comment-15544133
]
Hadoop QA commented on AMBARI-18496:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831426/AMBARI-18496-Oct3.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 test build failed in
contrib/views/hive-next contrib/views/hive
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8796//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8796//console
This message is automatically generated.
> Include an option to download the saved query in hive view
> --
>
> Key: AMBARI-18496
> URL: https://issues.apache.org/jira/browse/AMBARI-18496
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-18496-Oct3.patch, AMBARI-18496.patch,
> screenshot1.jpg, screenshot2.jpg
>
>
> An option to download the saved query can be included.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18501) If ambari-server fails to start, appropriate error message should be displayed.
[ https://issues.apache.org/jira/browse/AMBARI-18501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544046#comment-15544046 ] Hudson commented on AMBARI-18501: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5755 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5755/]) AMBARI-18501. If ambari-server fails to start, appropriate error message (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=98ba7e075458404f63e2ca16c73068a6df32a800]) * (edit) ambari-server/src/main/python/ambari_server/utils.py * (edit) ambari-server/src/main/python/ambari_server_main.py * (edit) ambari-server/src/test/python/TestUtils.py > If ambari-server fails to start, appropriate error message should be > displayed. > --- > > Key: AMBARI-18501 > URL: https://issues.apache.org/jira/browse/AMBARI-18501 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi > Fix For: 3.0.0 > > Attachments: AMBARI-18501.patch > > > If due to some error, ambari-server JAR exits with -1, we still display > “Ambari Server ‘start’ completed successfully” > In AmbariServer.java::main(), if an exception occurs, the program exits with > -1. Howerver, the caller ambari-server.py::main() displays the status message > as "Ambari Server 'start' completed successfully". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18487) Test and refine Collector writes w.r.t sharing and timeouts
[
https://issues.apache.org/jira/browse/AMBARI-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544028#comment-15544028
]
Hadoop QA commented on AMBARI-18487:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831428/AMBARI-18487-trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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-metrics/ambari-metrics-common.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8795//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8795//console
This message is automatically generated.
> Test and refine Collector writes w.r.t sharing and timeouts
> ---
>
> Key: AMBARI-18487
> URL: https://issues.apache.org/jira/browse/AMBARI-18487
> Project: Ambari
> Issue Type: Task
> Components: ambari-metrics
>Affects Versions: 3.0.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18487-trunk.patch
>
>
> Change metric monitor sharding strategy to hostname based.
> Fix issues in AbstractTimelineMetricSink
> Change Sink Zk retry policy to BoundedExponentialBackoffRetry.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18487) Test and refine Collector writes w.r.t sharing and timeouts
[
https://issues.apache.org/jira/browse/AMBARI-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543931#comment-15543931
]
Hadoop QA commented on AMBARI-18487:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831428/AMBARI-18487-trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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-metrics/ambari-metrics-common.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8794//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8794//console
This message is automatically generated.
> Test and refine Collector writes w.r.t sharing and timeouts
> ---
>
> Key: AMBARI-18487
> URL: https://issues.apache.org/jira/browse/AMBARI-18487
> Project: Ambari
> Issue Type: Task
> Components: ambari-metrics
>Affects Versions: 3.0.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18487-trunk.patch
>
>
> Change metric monitor sharding strategy to hostname based.
> Fix issues in AbstractTimelineMetricSink
> Change Sink Zk retry policy to BoundedExponentialBackoffRetry.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-14439) Categorize unit tests so can run mvn test -P $PROFILE
[ https://issues.apache.org/jira/browse/AMBARI-14439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543860#comment-15543860 ] Hudson commented on AMBARI-14439: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #104 (See [https://builds.apache.org/job/Ambari-branch-2.5/104/]) AMBARI-14439. Categorize unit tests so can run mvn test -P $PROFILE (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=21e36a04311fd427dc8a02d9852ef8b38b8e76aa]) * (add) utility/src/main/java/category/FastTest.java * (edit) ambari-metrics/pom.xml * (add) utility/src/main/java/category/KerberosTest.java * (add) utility/pom.xml * (add) utility/src/main/java/category/SlowTest.java * (add) utility/src/main/java/category/StackUpgradeTest.java * (edit) pom.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosIdentityDescriptorTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/stack/ConfigUpgradeValidityTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosConfigurationDescriptorTest.java * (add) utility/src/main/java/category/AlertTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosServiceDescriptorTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosDescriptorUpdateHelperTest.java * (add) utility/src/main/java/category/AmbariUpgradeTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertDefinitionEqualityTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertEventPublisherTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AggregateAlertListenerTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/alerts/InitialAlertEventTest.java * (edit) ambari-server/pom.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosKeytabDescriptorTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertReceivedListenerTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosDescriptorTest.java * (edit) ambari-logsearch/pom.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosPrincipalDescriptorTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertDefinitionHashTest.java * (add) utility/src/main/java/category/MetricsTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/VariableReplacementHelperTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosComponentDescriptorTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertStateChangedEventTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/stack/ConfigUpgradePackTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/stack/UpgradePackTest.java * (edit) ambari-metrics/ambari-metrics-timelineservice/pom.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/stack/OSFamilyTest.java * (add) utility/src/main/java/category/BlueprintTest.java > Categorize unit tests so can run mvn test -P $PROFILE > - > > Key: AMBARI-14439 > URL: https://issues.apache.org/jira/browse/AMBARI-14439 > Project: Ambari > Issue Type: Story > Components: ambari-server >Affects Versions: 2.3.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-14439.branch-2.5.patch, AMBARI-14439.trunk.patch > > > Categorize the unit tests so we that "mvn test -P $PROFILE" command can run > only the desired category in order to run the tests faster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18496) Include an option to download the saved query in hive view
[
https://issues.apache.org/jira/browse/AMBARI-18496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543828#comment-15543828
]
Hadoop QA commented on AMBARI-18496:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831426/AMBARI-18496-Oct3.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 test build failed in
contrib/views/hive-next contrib/views/hive
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8793//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8793//console
This message is automatically generated.
> Include an option to download the saved query in hive view
> --
>
> Key: AMBARI-18496
> URL: https://issues.apache.org/jira/browse/AMBARI-18496
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: trunk
>Reporter: Anita Gnanamalar Jebaraj
>Assignee: Anita Gnanamalar Jebaraj
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-18496-Oct3.patch, AMBARI-18496.patch,
> screenshot1.jpg, screenshot2.jpg
>
>
> An option to download the saved query can be included.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18187) AMS should work in SPNEGO enabled clusters.
[ https://issues.apache.org/jira/browse/AMBARI-18187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543818#comment-15543818 ] Hudson commented on AMBARI-18187: - ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #103 (See [https://builds.apache.org/job/Ambari-branch-2.5/103/]) AMBARI-18187 : AMS should work in SPNEGO enabled clusters. (avijayan) (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a9e9f01f5cdc2846ecb8da9c164b71b3f9ae0bbf]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py > AMS should work in SPNEGO enabled clusters. > --- > > Key: AMBARI-18187 > URL: https://issues.apache.org/jira/browse/AMBARI-18187 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18187.patch > > > AMS should work in SPNEGO enabled clusters, even if AMS does not natively > support SPNEGO. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18508) Provide a configurable option for "LLAP's headroom space for YARN container".
[
https://issues.apache.org/jira/browse/AMBARI-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543816#comment-15543816
]
Hudson commented on AMBARI-18508:
-
ABORTED: Integrated in Jenkins build Ambari-branch-2.5 #103 (See
[https://builds.apache.org/job/Ambari-branch-2.5/103/])
AMBARI-18508. Provide a configurable option for "LLAP's headroom space
(sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=46268ad37181626059f645e9b3b66aab59e00776])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-env.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
> Provide a configurable option for "LLAP's headroom space for YARN container".
> -
>
> Key: AMBARI-18508
> URL: https://issues.apache.org/jira/browse/AMBARI-18508
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-18508.patch
>
>
> *Issue:* LLAP daemons can be killed by the YARN Memory Monitor
> The following messages in the AM log of LLAP YARN Application.
> {quote}
> is running beyond physical memory limits. Current usage: of
> GB physical memory used.
> {quote}
> *Fix:* Increase the headroom space for heap from 1G (existing) to 6G. This
> option gets used while calculating heap size.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18487) Test and refine Collector writes w.r.t sharing and timeouts
[ https://issues.apache.org/jira/browse/AMBARI-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18487: --- Attachment: AMBARI-18487-trunk.patch > Test and refine Collector writes w.r.t sharing and timeouts > --- > > Key: AMBARI-18487 > URL: https://issues.apache.org/jira/browse/AMBARI-18487 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18487-trunk.patch > > > Change metric monitor sharding strategy to hostname based. > Fix issues in AbstractTimelineMetricSink > Change Sink Zk retry policy to BoundedExponentialBackoffRetry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18487) Test and refine Collector writes w.r.t sharing and timeouts
[ https://issues.apache.org/jira/browse/AMBARI-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18487: --- Status: Patch Available (was: Open) > Test and refine Collector writes w.r.t sharing and timeouts > --- > > Key: AMBARI-18487 > URL: https://issues.apache.org/jira/browse/AMBARI-18487 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18487-trunk.patch > > > Change metric monitor sharding strategy to hostname based. > Fix issues in AbstractTimelineMetricSink > Change Sink Zk retry policy to BoundedExponentialBackoffRetry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18496) Include an option to download the saved query in hive view
[ https://issues.apache.org/jira/browse/AMBARI-18496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18496: -- Attachment: (was: AMBARI-18496-Oct3.patch) > Include an option to download the saved query in hive view > -- > > Key: AMBARI-18496 > URL: https://issues.apache.org/jira/browse/AMBARI-18496 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18496-Oct3.patch, AMBARI-18496.patch, > screenshot1.jpg, screenshot2.jpg > > > An option to download the saved query can be included. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18487) Test and refine Collector writes w.r.t sharing and timeouts
[ https://issues.apache.org/jira/browse/AMBARI-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18487: --- Status: Open (was: Patch Available) > Test and refine Collector writes w.r.t sharing and timeouts > --- > > Key: AMBARI-18487 > URL: https://issues.apache.org/jira/browse/AMBARI-18487 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > > Change metric monitor sharding strategy to hostname based. > Fix issues in AbstractTimelineMetricSink > Change Sink Zk retry policy to BoundedExponentialBackoffRetry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18487) Test and refine Collector writes w.r.t sharing and timeouts
[ https://issues.apache.org/jira/browse/AMBARI-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18487: --- Attachment: (was: AMBARI-18487-3.patch) > Test and refine Collector writes w.r.t sharing and timeouts > --- > > Key: AMBARI-18487 > URL: https://issues.apache.org/jira/browse/AMBARI-18487 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > > Change metric monitor sharding strategy to hostname based. > Fix issues in AbstractTimelineMetricSink > Change Sink Zk retry policy to BoundedExponentialBackoffRetry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18496) Include an option to download the saved query in hive view
[ https://issues.apache.org/jira/browse/AMBARI-18496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18496: -- Status: Open (was: Patch Available) > Include an option to download the saved query in hive view > -- > > Key: AMBARI-18496 > URL: https://issues.apache.org/jira/browse/AMBARI-18496 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18496-Oct3.patch, AMBARI-18496.patch, > screenshot1.jpg, screenshot2.jpg > > > An option to download the saved query can be included. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18496) Include an option to download the saved query in hive view
[ https://issues.apache.org/jira/browse/AMBARI-18496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18496: -- Attachment: AMBARI-18496-Oct3.patch > Include an option to download the saved query in hive view > -- > > Key: AMBARI-18496 > URL: https://issues.apache.org/jira/browse/AMBARI-18496 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18496-Oct3.patch, AMBARI-18496.patch, > screenshot1.jpg, screenshot2.jpg > > > An option to download the saved query can be included. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18496) Include an option to download the saved query in hive view
[ https://issues.apache.org/jira/browse/AMBARI-18496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18496: -- Status: Patch Available (was: Open) > Include an option to download the saved query in hive view > -- > > Key: AMBARI-18496 > URL: https://issues.apache.org/jira/browse/AMBARI-18496 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18496-Oct3.patch, AMBARI-18496.patch, > screenshot1.jpg, screenshot2.jpg > > > An option to download the saved query can be included. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18496) Include an option to download the saved query in hive view
[ https://issues.apache.org/jira/browse/AMBARI-18496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18496: -- Attachment: (was: AMBARI-18496-Oct3.patch) > Include an option to download the saved query in hive view > -- > > Key: AMBARI-18496 > URL: https://issues.apache.org/jira/browse/AMBARI-18496 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18496-Oct3.patch, AMBARI-18496.patch, > screenshot1.jpg, screenshot2.jpg > > > An option to download the saved query can be included. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18496) Include an option to download the saved query in hive view
[ https://issues.apache.org/jira/browse/AMBARI-18496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18496: -- Attachment: AMBARI-18496-Oct3.patch > Include an option to download the saved query in hive view > -- > > Key: AMBARI-18496 > URL: https://issues.apache.org/jira/browse/AMBARI-18496 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18496-Oct3.patch, AMBARI-18496.patch, > screenshot1.jpg, screenshot2.jpg > > > An option to download the saved query can be included. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18519) Enable Add/Remove JournalNode on NNHA Wizard Step 2
[ https://issues.apache.org/jira/browse/AMBARI-18519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-18519: -- Attachment: AMBARI-18519.patch > Enable Add/Remove JournalNode on NNHA Wizard Step 2 > --- > > Key: AMBARI-18519 > URL: https://issues.apache.org/jira/browse/AMBARI-18519 > 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-18519.patch > > > Enable Add/Remove JournalNode on NNHA Wizard Step 2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18519) Enable Add/Remove JournalNode on NNHA Wizard Step 2
[ https://issues.apache.org/jira/browse/AMBARI-18519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-18519: -- Status: Patch Available (was: Open) > Enable Add/Remove JournalNode on NNHA Wizard Step 2 > --- > > Key: AMBARI-18519 > URL: https://issues.apache.org/jira/browse/AMBARI-18519 > 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-18519.patch > > > Enable Add/Remove JournalNode on NNHA Wizard Step 2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18519) Enable Add/Remove JournalNode on NNHA Wizard Step 2
Richard Zang created AMBARI-18519: - Summary: Enable Add/Remove JournalNode on NNHA Wizard Step 2 Key: AMBARI-18519 URL: https://issues.apache.org/jira/browse/AMBARI-18519 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Richard Zang Assignee: Richard Zang Fix For: 2.5.0 Enable Add/Remove JournalNode on NNHA Wizard Step 2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18517) Changes in upgrade path for Kafka metrics collector hosts config
[
https://issues.apache.org/jira/browse/AMBARI-18517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543665#comment-15543665
]
Hadoop QA commented on AMBARI-18517:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831386/AMBARI-18517.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/8792//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8792//console
This message is automatically generated.
> Changes in upgrade path for Kafka metrics collector hosts config
>
>
> Key: AMBARI-18517
> URL: https://issues.apache.org/jira/browse/AMBARI-18517
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 3.0.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
> Fix For: 3.0.0
>
> Attachments: AMBARI-18517.patch, Screen Shot 2016-08-22 at 11.00.37
> AM.png
>
>
> Config change for Kafka was added through AMBARI-18170 (Seen in attached
> screensot). This jira is used to track Upgrade path changes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18501) If ambari-server fails to start, appropriate error message should be displayed.
[ https://issues.apache.org/jira/browse/AMBARI-18501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18501: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > If ambari-server fails to start, appropriate error message should be > displayed. > --- > > Key: AMBARI-18501 > URL: https://issues.apache.org/jira/browse/AMBARI-18501 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi > Fix For: 3.0.0 > > Attachments: AMBARI-18501.patch > > > If due to some error, ambari-server JAR exits with -1, we still display > “Ambari Server ‘start’ completed successfully” > In AmbariServer.java::main(), if an exception occurs, the program exits with > -1. Howerver, the caller ambari-server.py::main() displays the status message > as "Ambari Server 'start' completed successfully". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18518) Sinks should not try to read collector hosts from Zk if AMS is in embedded mode
[
https://issues.apache.org/jira/browse/AMBARI-18518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18518:
---
Attachment: AMBARI-18518.patch
> Sinks should not try to read collector hosts from Zk if AMS is in embedded
> mode
> ---
>
> Key: AMBARI-18518
> URL: https://issues.apache.org/jira/browse/AMBARI-18518
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 3.0.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18518.patch
>
>
> Currently, an exception is constantly being thrown in sink logs.
> {code}
> 2016-10-03 21:01:06,537 WARN availability.MetricCollectorHAHelper
> (MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(91)) - Unable
> to connect to z
> ookeeper.
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException$ConnectionLossException:
> KeeperErrorCode = ConnectionLoss for /ambari-metrics-cluster
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException.create(KeeperException.java:99)
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException.create(KeeperException.java:51)
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.ZooKeeper.exists(ZooKeeper.java:1045)
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.ZooKeeper.exists(ZooKeeper.java:1073)
> at
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper.findLiveCollectorHostsFromZNode(MetricCollectorHAHelper.java:78)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:344)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.emitMetrics(AbstractTimelineMetricsSink.java:216)
> at
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.putMetrics(HadoopTimelineMetricsSink.java:345)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:186)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
> at
> org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:134)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
> {code}
> After the change
> {code}
> 2016-10-03 21:08:31,494 INFO availability.MetricCollectorHAHelper
> (MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(80)) -
> /ambari-metrics-cluster znode does not exist. Skipping requesting live
> instances from zookeeper
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18518) Sinks should not try to read collector hosts from Zk if AMS is in embedded mode
[
https://issues.apache.org/jira/browse/AMBARI-18518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18518:
---
Status: Patch Available (was: Open)
> Sinks should not try to read collector hosts from Zk if AMS is in embedded
> mode
> ---
>
> Key: AMBARI-18518
> URL: https://issues.apache.org/jira/browse/AMBARI-18518
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 3.0.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-18518.patch
>
>
> Currently, an exception is constantly being thrown in sink logs.
> {code}
> 2016-10-03 21:01:06,537 WARN availability.MetricCollectorHAHelper
> (MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(91)) - Unable
> to connect to z
> ookeeper.
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException$ConnectionLossException:
> KeeperErrorCode = ConnectionLoss for /ambari-metrics-cluster
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException.create(KeeperException.java:99)
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException.create(KeeperException.java:51)
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.ZooKeeper.exists(ZooKeeper.java:1045)
> at
> org.apache.hadoop.metrics2.sink.relocated.zookeeper.ZooKeeper.exists(ZooKeeper.java:1073)
> at
> org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper.findLiveCollectorHostsFromZNode(MetricCollectorHAHelper.java:78)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:344)
> at
> org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.emitMetrics(AbstractTimelineMetricsSink.java:216)
> at
> org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.putMetrics(HadoopTimelineMetricsSink.java:345)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:186)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
> at
> org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:134)
> at
> org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
> {code}
> After the change
> {code}
> 2016-10-03 21:08:31,494 INFO availability.MetricCollectorHAHelper
> (MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(80)) -
> /ambari-metrics-cluster znode does not exist. Skipping requesting live
> instances from zookeeper
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18245) Upgrade node to version 4.x
[ https://issues.apache.org/jira/browse/AMBARI-18245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18245: Status: Patch Available (was: Open) > Upgrade node to version 4.x > --- > > Key: AMBARI-18245 > URL: https://issues.apache.org/jira/browse/AMBARI-18245 > Project: Ambari > Issue Type: Task > Components: ambari-admin, ambari-views, ambari-web >Affects Versions: trunk >Reporter: Yusaku Sako >Assignee: Zhe (Joe) Wang > Fix For: trunk > > Attachments: AMBARI-18245.v0.patch > > > We are currently using 0.10, which is very old and going EOL 2016-10-01: > https://github.com/nodejs/LTS > We should look into upgrading to Node 4.x: > * Upgrade Node on Ambari Web > * Upgrade Node on Ambari Admin > * Upgrade Node on contrib/views/* modules -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18245) Upgrade node to version 4.x
[ https://issues.apache.org/jira/browse/AMBARI-18245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18245: Attachment: AMBARI-18245.v0.patch Local test passed. Manual testing done. > Upgrade node to version 4.x > --- > > Key: AMBARI-18245 > URL: https://issues.apache.org/jira/browse/AMBARI-18245 > Project: Ambari > Issue Type: Task > Components: ambari-admin, ambari-views, ambari-web >Affects Versions: trunk >Reporter: Yusaku Sako >Assignee: Zhe (Joe) Wang > Fix For: trunk > > Attachments: AMBARI-18245.v0.patch > > > We are currently using 0.10, which is very old and going EOL 2016-10-01: > https://github.com/nodejs/LTS > We should look into upgrading to Node 4.x: > * Upgrade Node on Ambari Web > * Upgrade Node on Ambari Admin > * Upgrade Node on contrib/views/* modules -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-14439) Categorize unit tests so can run mvn test -P $PROFILE
[ https://issues.apache.org/jira/browse/AMBARI-14439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543629#comment-15543629 ] Hudson commented on AMBARI-14439: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5754 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5754/]) AMBARI-14439. Categorize unit tests so can run mvn test -P $PROFILE (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ee02ad9c984b5a15eea13a175e212c0e1f6ff1c2]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosIdentityDescriptorTest.java * (add) utility/src/main/java/category/AlertTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosConfigurationDescriptorTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/alerts/InitialAlertEventTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/stack/OSFamilyTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosComponentDescriptorTest.java * (add) utility/pom.xml * (add) utility/src/main/java/category/MetricsTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosDescriptorUpdateHelperTest.java * (edit) ambari-logsearch/pom.xml * (edit) pom.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/stack/UpgradePackTest.java * (edit) ambari-metrics/pom.xml * (edit) ambari-server/pom.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/VariableReplacementHelperTest.java * (add) utility/src/main/java/category/FastTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertEventPublisherTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/stack/ConfigUpgradeValidityTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AggregateAlertListenerTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertDefinitionEqualityTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosKeytabDescriptorTest.java * (add) utility/src/main/java/category/AmbariUpgradeTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertDefinitionHashTest.java * (add) utility/src/main/java/category/StackUpgradeTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertReceivedListenerTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosDescriptorTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosPrincipalDescriptorTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/stack/ConfigUpgradePackTest.java * (add) utility/src/main/java/category/SlowTest.java * (edit) ambari-metrics/ambari-metrics-timelineservice/pom.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/kerberos/KerberosServiceDescriptorTest.java * (add) utility/src/main/java/category/BlueprintTest.java * (add) utility/src/main/java/category/KerberosTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/state/alerts/AlertStateChangedEventTest.java > Categorize unit tests so can run mvn test -P $PROFILE > - > > Key: AMBARI-14439 > URL: https://issues.apache.org/jira/browse/AMBARI-14439 > Project: Ambari > Issue Type: Story > Components: ambari-server >Affects Versions: 2.3.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-14439.branch-2.5.patch, AMBARI-14439.trunk.patch > > > Categorize the unit tests so we that "mvn test -P $PROFILE" command can run > only the desired category in order to run the tests faster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18508) Provide a configurable option for "LLAP's headroom space for YARN container".
[
https://issues.apache.org/jira/browse/AMBARI-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543628#comment-15543628
]
Hudson commented on AMBARI-18508:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5754 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5754/])
AMBARI-18508. Provide a configurable option for "LLAP's headroom space
(sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7ac93f3a8aeeedb71d0feecc1f4ff99972f717f7])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/hive-interactive-env.xml
> Provide a configurable option for "LLAP's headroom space for YARN container".
> -
>
> Key: AMBARI-18508
> URL: https://issues.apache.org/jira/browse/AMBARI-18508
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-18508.patch
>
>
> *Issue:* LLAP daemons can be killed by the YARN Memory Monitor
> The following messages in the AM log of LLAP YARN Application.
> {quote}
> is running beyond physical memory limits. Current usage: of
> GB physical memory used.
> {quote}
> *Fix:* Increase the headroom space for heap from 1G (existing) to 6G. This
> option gets used while calculating heap size.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18518) Sinks should not try to read collector hosts from Zk if AMS is in embedded mode
[
https://issues.apache.org/jira/browse/AMBARI-18518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-18518:
---
Description:
Currently, an exception is constantly being thrown in sink logs.
{code}
2016-10-03 21:01:06,537 WARN availability.MetricCollectorHAHelper
(MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(91)) - Unable to
connect to z
ookeeper.
org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException$ConnectionLossException:
KeeperErrorCode = ConnectionLoss for /ambari-metrics-cluster
at
org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException.create(KeeperException.java:99)
at
org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException.create(KeeperException.java:51)
at
org.apache.hadoop.metrics2.sink.relocated.zookeeper.ZooKeeper.exists(ZooKeeper.java:1045)
at
org.apache.hadoop.metrics2.sink.relocated.zookeeper.ZooKeeper.exists(ZooKeeper.java:1073)
at
org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper.findLiveCollectorHostsFromZNode(MetricCollectorHAHelper.java:78)
at
org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:344)
at
org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.emitMetrics(AbstractTimelineMetricsSink.java:216)
at
org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.putMetrics(HadoopTimelineMetricsSink.java:345)
at
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:186)
at
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
at
org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
at
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:134)
at
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
{code}
After the change
{code}
2016-10-03 21:08:31,494 INFO availability.MetricCollectorHAHelper
(MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(80)) -
/ambari-metrics-cluster znode does not exist. Skipping requesting live
instances from zookeeper
{code}
was:
Currently, an exception is constantly being thrown in sink logs.
{code}
2016-10-03 21:01:06,537 WARN availability.MetricCollectorHAHelper
(MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(91)) - Unable to
connect to z
ookeeper.
org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException$ConnectionLossException:
KeeperErrorCode = ConnectionLoss for /ambari-metrics-cluster
at
org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException.create(KeeperException.java:99)
at
org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException.create(KeeperException.java:51)
at
org.apache.hadoop.metrics2.sink.relocated.zookeeper.ZooKeeper.exists(ZooKeeper.java:1045)
at
org.apache.hadoop.metrics2.sink.relocated.zookeeper.ZooKeeper.exists(ZooKeeper.java:1073)
at
org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper.findLiveCollectorHostsFromZNode(MetricCollectorHAHelper.java:78)
at
org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:344)
at
org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.emitMetrics(AbstractTimelineMetricsSink.java:216)
at
org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.putMetrics(HadoopTimelineMetricsSink.java:345)
at
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:186)
at
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
at
org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
at
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:134)
at
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
{code}
After the change
{code}
2016-10-03 21:08:31,494 INFO availability.MetricCollectorHAHelper
(MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(80)) -
/ambari-metrics-cluster Znode does not exist. Skipping requesting live instances
{code}
> Sinks should not try to read collector hosts from Zk if AMS is in embedded
> mode
> ---
>
> Key: AMBARI-18518
> URL: https://issues.apache.org/jira/browse/AMBARI-18518
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 3.0.0
>Reporter: Aravindan Vijayan
>Assignee: Arav
[jira] [Created] (AMBARI-18518) Sinks should not try to read collector hosts from Zk if AMS is in embedded mode
Aravindan Vijayan created AMBARI-18518:
--
Summary: Sinks should not try to read collector hosts from Zk if
AMS is in embedded mode
Key: AMBARI-18518
URL: https://issues.apache.org/jira/browse/AMBARI-18518
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: 3.0.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Priority: Critical
Fix For: 3.0.0
Currently, an exception is constantly being thrown in sink logs.
{code}
2016-10-03 21:01:06,537 WARN availability.MetricCollectorHAHelper
(MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(91)) - Unable to
connect to z
ookeeper.
org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException$ConnectionLossException:
KeeperErrorCode = ConnectionLoss for /ambari-metrics-cluster
at
org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException.create(KeeperException.java:99)
at
org.apache.hadoop.metrics2.sink.relocated.zookeeper.KeeperException.create(KeeperException.java:51)
at
org.apache.hadoop.metrics2.sink.relocated.zookeeper.ZooKeeper.exists(ZooKeeper.java:1045)
at
org.apache.hadoop.metrics2.sink.relocated.zookeeper.ZooKeeper.exists(ZooKeeper.java:1073)
at
org.apache.hadoop.metrics2.sink.timeline.availability.MetricCollectorHAHelper.findLiveCollectorHostsFromZNode(MetricCollectorHAHelper.java:78)
at
org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.findPreferredCollectHost(AbstractTimelineMetricsSink.java:344)
at
org.apache.hadoop.metrics2.sink.timeline.AbstractTimelineMetricsSink.emitMetrics(AbstractTimelineMetricsSink.java:216)
at
org.apache.hadoop.metrics2.sink.timeline.HadoopTimelineMetricsSink.putMetrics(HadoopTimelineMetricsSink.java:345)
at
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:186)
at
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.consume(MetricsSinkAdapter.java:43)
at
org.apache.hadoop.metrics2.impl.SinkQueue.consumeAll(SinkQueue.java:87)
at
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter.publishMetricsFromQueue(MetricsSinkAdapter.java:134)
at
org.apache.hadoop.metrics2.impl.MetricsSinkAdapter$1.run(MetricsSinkAdapter.java:88)
{code}
After the change
{code}
2016-10-03 21:08:31,494 INFO availability.MetricCollectorHAHelper
(MetricCollectorHAHelper.java:findLiveCollectorHostsFromZNode(80)) -
/ambari-metrics-cluster Znode does not exist. Skipping requesting live instances
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-14439) Categorize unit tests so can run mvn test -P $PROFILE
[ https://issues.apache.org/jira/browse/AMBARI-14439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez resolved AMBARI-14439. -- Resolution: Fixed Pushed to trunk, commit ee02ad9c984b5a15eea13a175e212c0e1f6ff1c2 branch-2.5, commit 21e36a04311fd427dc8a02d9852ef8b38b8e76aa > Categorize unit tests so can run mvn test -P $PROFILE > - > > Key: AMBARI-14439 > URL: https://issues.apache.org/jira/browse/AMBARI-14439 > Project: Ambari > Issue Type: Story > Components: ambari-server >Affects Versions: 2.3.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-14439.branch-2.5.patch, AMBARI-14439.trunk.patch > > > Categorize the unit tests so we that "mvn test -P $PROFILE" command can run > only the desired category in order to run the tests faster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18508) Provide a configurable option for "LLAP's headroom space for YARN container".
[
https://issues.apache.org/jira/browse/AMBARI-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-18508:
-
Description:
*Issue:* LLAP daemons can be killed by the YARN Memory Monitor
The following messages in the AM log of LLAP YARN Application.
{quote}
is running beyond physical memory limits. Current usage: of
GB physical memory used.
{quote}
*Fix:* Increase the headroom space for heap from 1G (existing) to 6G. This
option gets used while calculating heap size.
was:
*Issue:* LLAP daemons can be killed by the YARN Memory Monitor
The following messages in the AM log of LLAP YARN Application.
{quote}
is running beyond physical memory limits. Current usage: of
GB physical memory used.
{quote}
*Fix:* Increase the headroom space for heap from 1G (existing) to 6G.
> Provide a configurable option for "LLAP's headroom space for YARN container".
> -
>
> Key: AMBARI-18508
> URL: https://issues.apache.org/jira/browse/AMBARI-18508
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-18508.patch
>
>
> *Issue:* LLAP daemons can be killed by the YARN Memory Monitor
> The following messages in the AM log of LLAP YARN Application.
> {quote}
> is running beyond physical memory limits. Current usage: of
> GB physical memory used.
> {quote}
> *Fix:* Increase the headroom space for heap from 1G (existing) to 6G. This
> option gets used while calculating heap size.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18508) Provide a configurable option for "LLAP's headroom space for YARN container".
[
https://issues.apache.org/jira/browse/AMBARI-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-18508:
-
Summary: Provide a configurable option for "LLAP's headroom space for YARN
container". (was: Increasing headroom on heap size is from 1G to 6G for LLAP.)
> Provide a configurable option for "LLAP's headroom space for YARN container".
> -
>
> Key: AMBARI-18508
> URL: https://issues.apache.org/jira/browse/AMBARI-18508
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-18508.patch
>
>
> *Issue:* LLAP daemons can be killed by the YARN Memory Monitor
> The following messages in the AM log of LLAP YARN Application.
> {quote}
> is running beyond physical memory limits. Current usage: of
> GB physical memory used.
> {quote}
> *Fix:* Increase the headroom space for heap from 1G (existing) to 6G.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18508) Provide a configurable option for "LLAP's headroom space for YARN container".
[
https://issues.apache.org/jira/browse/AMBARI-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-18508:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Provide a configurable option for "LLAP's headroom space for YARN container".
> -
>
> Key: AMBARI-18508
> URL: https://issues.apache.org/jira/browse/AMBARI-18508
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-18508.patch
>
>
> *Issue:* LLAP daemons can be killed by the YARN Memory Monitor
> The following messages in the AM log of LLAP YARN Application.
> {quote}
> is running beyond physical memory limits. Current usage: of
> GB physical memory used.
> {quote}
> *Fix:* Increase the headroom space for heap from 1G (existing) to 6G. This
> option gets used while calculating heap size.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18517) Changes in upgrade path for Kafka metrics collector hosts config
[ https://issues.apache.org/jira/browse/AMBARI-18517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18517: --- Status: Patch Available (was: Open) > Changes in upgrade path for Kafka metrics collector hosts config > > > Key: AMBARI-18517 > URL: https://issues.apache.org/jira/browse/AMBARI-18517 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 3.0.0 > > Attachments: AMBARI-18517.patch, Screen Shot 2016-08-22 at 11.00.37 > AM.png > > > Config change for Kafka was added through AMBARI-18170 (Seen in attached > screensot). This jira is used to track Upgrade path changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18517) Changes in upgrade path for Kafka metrics collector hosts config
[ https://issues.apache.org/jira/browse/AMBARI-18517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18517: --- Attachment: AMBARI-18517.patch > Changes in upgrade path for Kafka metrics collector hosts config > > > Key: AMBARI-18517 > URL: https://issues.apache.org/jira/browse/AMBARI-18517 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 3.0.0 > > Attachments: AMBARI-18517.patch, Screen Shot 2016-08-22 at 11.00.37 > AM.png > > > Config change for Kafka was added through AMBARI-18170 (Seen in attached > screensot). This jira is used to track Upgrade path changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18517) Changes in upgrade path for Kafka metrics collector hosts config
[ https://issues.apache.org/jira/browse/AMBARI-18517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18517: --- Attachment: Screen Shot 2016-08-22 at 11.00.37 AM.png > Changes in upgrade path for Kafka metrics collector hosts config > > > Key: AMBARI-18517 > URL: https://issues.apache.org/jira/browse/AMBARI-18517 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 3.0.0 > > Attachments: Screen Shot 2016-08-22 at 11.00.37 AM.png > > > Config change for Kafka was added through AMBARI-18170 (Seen in attached > screensot). This jira is used to track Upgrade path changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18517) Changes in upgrade path for Kafka metrics collector hosts config
Aravindan Vijayan created AMBARI-18517: -- Summary: Changes in upgrade path for Kafka metrics collector hosts config Key: AMBARI-18517 URL: https://issues.apache.org/jira/browse/AMBARI-18517 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 3.0.0 Reporter: Aravindan Vijayan Assignee: Aravindan Vijayan Fix For: 3.0.0 Config change for Kafka was added through AMBARI-18170 (Seen in attached screensot). This jira is used to track Upgrade path changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18508) Increasing headroom on heap size is from 1G to 6G for LLAP.
[
https://issues.apache.org/jira/browse/AMBARI-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-18508:
-
Attachment: AMBARI-18508.patch
> Increasing headroom on heap size is from 1G to 6G for LLAP.
> ---
>
> Key: AMBARI-18508
> URL: https://issues.apache.org/jira/browse/AMBARI-18508
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-18508.patch
>
>
> *Issue:* LLAP daemons can be killed by the YARN Memory Monitor
> The following messages in the AM log of LLAP YARN Application.
> {quote}
> is running beyond physical memory limits. Current usage: of
> GB physical memory used.
> {quote}
> *Fix:* Increase the headroom space for heap from 1G (existing) to 6G.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18508) Increasing headroom on heap size is from 1G to 6G for LLAP.
[
https://issues.apache.org/jira/browse/AMBARI-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-18508:
-
Status: Patch Available (was: Open)
> Increasing headroom on heap size is from 1G to 6G for LLAP.
> ---
>
> Key: AMBARI-18508
> URL: https://issues.apache.org/jira/browse/AMBARI-18508
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-18508.patch
>
>
> *Issue:* LLAP daemons can be killed by the YARN Memory Monitor
> The following messages in the AM log of LLAP YARN Application.
> {quote}
> is running beyond physical memory limits. Current usage: of
> GB physical memory used.
> {quote}
> *Fix:* Increase the headroom space for heap from 1G (existing) to 6G.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18508) Increasing headroom on heap size is from 1G to 6G for LLAP.
[
https://issues.apache.org/jira/browse/AMBARI-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-18508:
-
Status: Open (was: Patch Available)
> Increasing headroom on heap size is from 1G to 6G for LLAP.
> ---
>
> Key: AMBARI-18508
> URL: https://issues.apache.org/jira/browse/AMBARI-18508
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0, 2.4.2
>
>
> *Issue:* LLAP daemons can be killed by the YARN Memory Monitor
> The following messages in the AM log of LLAP YARN Application.
> {quote}
> is running beyond physical memory limits. Current usage: of
> GB physical memory used.
> {quote}
> *Fix:* Increase the headroom space for heap from 1G (existing) to 6G.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18508) Increasing headroom on heap size is from 1G to 6G for LLAP.
[
https://issues.apache.org/jira/browse/AMBARI-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-18508:
-
Attachment: (was: AMBARI-18508.patch)
> Increasing headroom on heap size is from 1G to 6G for LLAP.
> ---
>
> Key: AMBARI-18508
> URL: https://issues.apache.org/jira/browse/AMBARI-18508
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.1
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 2.5.0, 2.4.2
>
>
> *Issue:* LLAP daemons can be killed by the YARN Memory Monitor
> The following messages in the AM log of LLAP YARN Application.
> {quote}
> is running beyond physical memory limits. Current usage: of
> GB physical memory used.
> {quote}
> *Fix:* Increase the headroom space for heap from 1G (existing) to 6G.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18187) AMS should work in SPNEGO enabled clusters.
[ https://issues.apache.org/jira/browse/AMBARI-18187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18187: --- Fix Version/s: (was: trunk) 2.4.2 > AMS should work in SPNEGO enabled clusters. > --- > > Key: AMBARI-18187 > URL: https://issues.apache.org/jira/browse/AMBARI-18187 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18187.patch > > > AMS should work in SPNEGO enabled clusters, even if AMS does not natively > support SPNEGO. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18187) AMS should work in SPNEGO enabled clusters.
[ https://issues.apache.org/jira/browse/AMBARI-18187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543186#comment-15543186 ] Aravindan Vijayan commented on AMBARI-18187: Pushed to branches 2.4 and 2.5. > AMS should work in SPNEGO enabled clusters. > --- > > Key: AMBARI-18187 > URL: https://issues.apache.org/jira/browse/AMBARI-18187 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18187.patch > > > AMS should work in SPNEGO enabled clusters, even if AMS does not natively > support SPNEGO. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18187) AMS should work in SPNEGO enabled clusters.
[ https://issues.apache.org/jira/browse/AMBARI-18187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18187: --- Affects Version/s: (was: trunk) 2.4.2 > AMS should work in SPNEGO enabled clusters. > --- > > Key: AMBARI-18187 > URL: https://issues.apache.org/jira/browse/AMBARI-18187 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18187.patch > > > AMS should work in SPNEGO enabled clusters, even if AMS does not natively > support SPNEGO. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18514) Graph details popup: file formats dropdown isn't collapsed on text link click
[ https://issues.apache.org/jira/browse/AMBARI-18514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543183#comment-15543183 ] Hudson commented on AMBARI-18514: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5753 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5753/]) AMBARI-18514. Graph details popup: file formats dropdown isn't collapsed (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f2bcbbe70008303afdefd7c218b4954127ebe978]) * (edit) ambari-web/app/views/common/chart/linear_time.js > Graph details popup: file formats dropdown isn't collapsed on text link click > - > > Key: AMBARI-18514 > URL: https://issues.apache.org/jira/browse/AMBARI-18514 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.0 > > Attachments: AMBARI-18514.patch, graph-details.jpg > > > In graph popup details, dropdown menu with exported file formats should be > toggled with click on 'Export' link or download icon.Expansion works fine, > unlike collapse. > See [screenshot attached|^graph-details.jpg]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18516) Add ability to have services declare itself as tech-preview or mandatory
[
https://issues.apache.org/jira/browse/AMBARI-18516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543169#comment-15543169
]
Hadoop QA commented on AMBARI-18516:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831336/AMBARI-18516.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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/8790//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8790//console
This message is automatically generated.
> Add ability to have services declare itself as tech-preview or mandatory
>
>
> Key: AMBARI-18516
> URL: https://issues.apache.org/jira/browse/AMBARI-18516
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18516.patch
>
>
> When a service is added to a stack, it should be identified as:
> default/regular - service is optional on the cluster, UI usually shows it as
> tech-preview - service may be deployed, UI will not auto-select these
> services and mark them as TechPreview
> mandatory - service need to be deployed and all deployment should fail is the
> service is not selected during deployment
> Lets create a proposal of what changes are needed in the services'
> metainfo.xml? Note that a service can change its attribute between stack
> versions - e.g. move from "tech-preview" to "mandatory".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18514) Graph details popup: file formats dropdown isn't collapsed on text link click
[ https://issues.apache.org/jira/browse/AMBARI-18514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543159#comment-15543159 ] Hudson commented on AMBARI-18514: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #102 (See [https://builds.apache.org/job/Ambari-branch-2.5/102/]) AMBARI-18514. Graph details popup: file formats dropdown isn't collapsed (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=13b9f11561dfc55742718e91960a93ac94205207]) * (edit) ambari-web/app/views/common/chart/linear_time.js > Graph details popup: file formats dropdown isn't collapsed on text link click > - > > Key: AMBARI-18514 > URL: https://issues.apache.org/jira/browse/AMBARI-18514 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.0 > > Attachments: AMBARI-18514.patch, graph-details.jpg > > > In graph popup details, dropdown menu with exported file formats should be > toggled with click on 'Export' link or download icon.Expansion works fine, > unlike collapse. > See [screenshot attached|^graph-details.jpg]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18487) Test and refine Collector writes w.r.t sharing and timeouts
[ https://issues.apache.org/jira/browse/AMBARI-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18487: --- Status: Patch Available (was: Open) > Test and refine Collector writes w.r.t sharing and timeouts > --- > > Key: AMBARI-18487 > URL: https://issues.apache.org/jira/browse/AMBARI-18487 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18487-3.patch > > > Change metric monitor sharding strategy to hostname based. > Fix issues in AbstractTimelineMetricSink > Change Sink Zk retry policy to BoundedExponentialBackoffRetry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18496) Include an option to download the saved query in hive view
[ https://issues.apache.org/jira/browse/AMBARI-18496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18496: -- Attachment: AMBARI-18496-Oct3.patch > Include an option to download the saved query in hive view > -- > > Key: AMBARI-18496 > URL: https://issues.apache.org/jira/browse/AMBARI-18496 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18496-Oct3.patch, AMBARI-18496.patch, > screenshot1.jpg, screenshot2.jpg > > > An option to download the saved query can be included. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18487) Test and refine Collector writes w.r.t sharing and timeouts
[ https://issues.apache.org/jira/browse/AMBARI-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18487: --- Attachment: AMBARI-18487-3.patch > Test and refine Collector writes w.r.t sharing and timeouts > --- > > Key: AMBARI-18487 > URL: https://issues.apache.org/jira/browse/AMBARI-18487 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18487-3.patch > > > Change metric monitor sharding strategy to hostname based. > Fix issues in AbstractTimelineMetricSink > Change Sink Zk retry policy to BoundedExponentialBackoffRetry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18487) Test and refine Collector writes w.r.t sharing and timeouts
[ https://issues.apache.org/jira/browse/AMBARI-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18487: --- Attachment: (was: AMBARI-18487-3.patch) > Test and refine Collector writes w.r.t sharing and timeouts > --- > > Key: AMBARI-18487 > URL: https://issues.apache.org/jira/browse/AMBARI-18487 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18487-3.patch > > > Change metric monitor sharding strategy to hostname based. > Fix issues in AbstractTimelineMetricSink > Change Sink Zk retry policy to BoundedExponentialBackoffRetry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18487) Test and refine Collector writes w.r.t sharing and timeouts
[ https://issues.apache.org/jira/browse/AMBARI-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18487: --- Status: Open (was: Patch Available) > Test and refine Collector writes w.r.t sharing and timeouts > --- > > Key: AMBARI-18487 > URL: https://issues.apache.org/jira/browse/AMBARI-18487 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18487-3.patch > > > Change metric monitor sharding strategy to hostname based. > Fix issues in AbstractTimelineMetricSink > Change Sink Zk retry policy to BoundedExponentialBackoffRetry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18487) Test and refine Collector writes w.r.t sharing and timeouts
[ https://issues.apache.org/jira/browse/AMBARI-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18487: --- Attachment: AMBARI-18487-3.patch > Test and refine Collector writes w.r.t sharing and timeouts > --- > > Key: AMBARI-18487 > URL: https://issues.apache.org/jira/browse/AMBARI-18487 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18487-3.patch > > > Change metric monitor sharding strategy to hostname based. > Fix issues in AbstractTimelineMetricSink > Change Sink Zk retry policy to BoundedExponentialBackoffRetry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18487) Test and refine Collector writes w.r.t sharing and timeouts
[ https://issues.apache.org/jira/browse/AMBARI-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18487: --- Attachment: (was: AMBARI-18487-2.patch) > Test and refine Collector writes w.r.t sharing and timeouts > --- > > Key: AMBARI-18487 > URL: https://issues.apache.org/jira/browse/AMBARI-18487 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18487-3.patch > > > Change metric monitor sharding strategy to hostname based. > Fix issues in AbstractTimelineMetricSink > Change Sink Zk retry policy to BoundedExponentialBackoffRetry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18487) Test and refine Collector writes w.r.t sharing and timeouts
[ https://issues.apache.org/jira/browse/AMBARI-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18487: --- Status: Patch Available (was: Open) > Test and refine Collector writes w.r.t sharing and timeouts > --- > > Key: AMBARI-18487 > URL: https://issues.apache.org/jira/browse/AMBARI-18487 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18487-3.patch > > > Change metric monitor sharding strategy to hostname based. > Fix issues in AbstractTimelineMetricSink > Change Sink Zk retry policy to BoundedExponentialBackoffRetry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18487) Test and refine Collector writes w.r.t sharing and timeouts
[ https://issues.apache.org/jira/browse/AMBARI-18487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-18487: --- Status: Open (was: Patch Available) > Test and refine Collector writes w.r.t sharing and timeouts > --- > > Key: AMBARI-18487 > URL: https://issues.apache.org/jira/browse/AMBARI-18487 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18487-2.patch > > > Change metric monitor sharding strategy to hostname based. > Fix issues in AbstractTimelineMetricSink > Change Sink Zk retry policy to BoundedExponentialBackoffRetry. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18456) Refactor Unnecessary In-Memory Locks Around Business Objects
[
https://issues.apache.org/jira/browse/AMBARI-18456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-18456:
-
Labels: branch-feature-AMBARI-18456 (was: )
> Refactor Unnecessary In-Memory Locks Around Business Objects
>
>
> Key: AMBARI-18456
> URL: https://issues.apache.org/jira/browse/AMBARI-18456
> Project: Ambari
> Issue Type: Epic
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Labels: branch-feature-AMBARI-18456
>
> The top 4 business objects in Ambari:
> - ClusterImpl
> - ServiceImpl
> - ServiceComponentImpl
> - ServiceComponentHostImpl
> All use {{ReadWriteLock}} implementations to prevent dirty reads and
> concurrent writes. However, {{ClusterImpl}} exposes a "global"
> {{ReadWriteLock}} which the other business objects share. This causes
> tremendous problems with deadlocks, especially on slow databases.
> Consider the case where you have 3 threads:
> # thread-1 acquires {{ClusterReadLock}}
> # thread-2 acquires {{ServiceComponenWriteLock}}
> # thread-3 tries to get {{ClusterWriteLock}} and is blocked by {{thread-1}}
> # thread-2 tries to get {{ClusterReadLock}} and is blocked by {{thread-3}}
> # thread-1 tries to get {{ServiceComponentReadLock}} and is blocked by
> {{thread-2}}
> Essentially, the exposure of the "cluster global lock" causes problems since
> multiple threads can acquire other internal locks and be blocked waiting on
> the global lock.
> In general, I don't believe that the read locks help at all. Ambari usually
> encounters these locks while try to display web page information. Once
> displayed, the locks are removed and the information is already stale if
> there were write threads waiting.
> These locks should be investigated and, for the most part, except in some
> cases involving concurrent writes, removed.
> Part of the problem revolves around our assumption about how the
> ReadWriteLock works. The issue in the above scenario is that the
> clusterWriteLock request is pending. This actually blocks all subsequent
> readers even though the lock is not fair.
> FYI, this code shows that a reader, in unfair mode, will wait when there is a
> waiting writer:
> {noformat:title=Output}
> Waiting for a read lock...
> Read lock acquired!
> Waiting for a write lock...
> Trying to acquire a second read lock...
> {noformat}
> {code}
> import java.util.concurrent.locks.ReentrantReadWriteLock;
> public class Test {
> private static ReentrantReadWriteLock lock = new
> ReentrantReadWriteLock(false);
> public static void main(String[] args) throws InterruptedException {
> // A reader which takes too long to finish
> new Thread() {
> @Override
> public void run() {
> System.out.println("Waiting for a read lock...");
> lock.readLock().lock();
> System.out.println("Read lock acquired!");
> try {
> try {
> Thread.sleep(1000 * 60 * 60);
> } catch (InterruptedException e) {
> }
> } finally {
> lock.readLock().unlock();
> }
> }
> }.start();
> Thread.sleep(3000);
> // A writer which will be waiting
> new Thread() {
> @Override
> public void run() {
> System.out.println("Waiting for a write lock...");
> lock.writeLock().lock();
> System.out.println("Write lock acquired!");
> lock.writeLock().unlock();
> }
> }.start();
> Thread.sleep(3000);
> // Another reader
> new Thread() {
> @Override
> public void run() {
> System.out.println("Trying to acquire a second read lock...");
> lock.readLock().lock();
> try {
> System.out.println("Second read lock acquired successfully!!");
> } finally {
> lock.readLock().unlock();
> }
> }
> }.start();
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-18475) Remove Global Cluster Lock Shared Between Business Objects
[
https://issues.apache.org/jira/browse/AMBARI-18475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley resolved AMBARI-18475.
--
Resolution: Fixed
> Remove Global Cluster Lock Shared Between Business Objects
> --
>
> Key: AMBARI-18475
> URL: https://issues.apache.org/jira/browse/AMBARI-18475
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
>
> Remove shared instances of the shared {{ReadWriteLock}} found in
> {{ClusterImpl}}. For now, the lock can remain private and full encapsulated
> inside of {{ClusterImpl}}, but it's use and reference across the rest of
> Ambari should be removed.
> This is part of the effort to refactor/remove the (mostly) unnecessary locks
> in memory. The shared instance of this lock is the number one reason that
> Ambari "deadlocks" when under load.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18495) Remove Unnecessary Locks Inside Of Cluster Business Object Implementations
[
https://issues.apache.org/jira/browse/AMBARI-18495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-18495:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Remove Unnecessary Locks Inside Of Cluster Business Object Implementations
> --
>
> Key: AMBARI-18495
> URL: https://issues.apache.org/jira/browse/AMBARI-18495
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18495.patch
>
>
> Many of the business object implementations include needless locks which
> simply add the overhead and contention in larger clusters. Some examples of
> these are :
> - HostImpl
> -- get/set DisksInfo()
> -- get/set TotalMemBytes()
> - ServiceComponentHostImpl
> -- get/set MaintenanceState()
> -- get/set LastOpLastUpdateTime()
> These types of methods are found on other business classes as well, like
> {{ClusterImpl}} and {{ServiceImpl}}. Additionally, methods like
> {{convertToResponse()}} and {{debugDump()}} need not acquire locks since they
> are used mostly for serialization of data to the web client where the data
> will then immediately become stale anyway.
> The {{Clusters}} and {{Cluster}} business objects should have the following
> work performed:
> - Remove locking around areas where its no longer required
> - Replace collections with thread-safe concurrent versions
> - Remove some reliance on state-full business objects (caches)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18495) Remove Unnecessary Locks Inside Of Cluster Business Object Implementations
[
https://issues.apache.org/jira/browse/AMBARI-18495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-18495:
-
Attachment: AMBARI-18495.patch
> Remove Unnecessary Locks Inside Of Cluster Business Object Implementations
> --
>
> Key: AMBARI-18495
> URL: https://issues.apache.org/jira/browse/AMBARI-18495
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18495.patch
>
>
> Many of the business object implementations include needless locks which
> simply add the overhead and contention in larger clusters. Some examples of
> these are :
> - HostImpl
> -- get/set DisksInfo()
> -- get/set TotalMemBytes()
> - ServiceComponentHostImpl
> -- get/set MaintenanceState()
> -- get/set LastOpLastUpdateTime()
> These types of methods are found on other business classes as well, like
> {{ClusterImpl}} and {{ServiceImpl}}. Additionally, methods like
> {{convertToResponse()}} and {{debugDump()}} need not acquire locks since they
> are used mostly for serialization of data to the web client where the data
> will then immediately become stale anyway.
> The {{Clusters}} and {{Cluster}} business objects should have the following
> work performed:
> - Remove locking around areas where its no longer required
> - Replace collections with thread-safe concurrent versions
> - Remove some reliance on state-full business objects (caches)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18495) Remove Unnecessary Locks Inside Of Cluster Business Object Implementations
[
https://issues.apache.org/jira/browse/AMBARI-18495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-18495:
-
Status: Patch Available (was: Open)
> Remove Unnecessary Locks Inside Of Cluster Business Object Implementations
> --
>
> Key: AMBARI-18495
> URL: https://issues.apache.org/jira/browse/AMBARI-18495
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
>
> Many of the business object implementations include needless locks which
> simply add the overhead and contention in larger clusters. Some examples of
> these are :
> - HostImpl
> -- get/set DisksInfo()
> -- get/set TotalMemBytes()
> - ServiceComponentHostImpl
> -- get/set MaintenanceState()
> -- get/set LastOpLastUpdateTime()
> These types of methods are found on other business classes as well, like
> {{ClusterImpl}} and {{ServiceImpl}}. Additionally, methods like
> {{convertToResponse()}} and {{debugDump()}} need not acquire locks since they
> are used mostly for serialization of data to the web client where the data
> will then immediately become stale anyway.
> The {{Clusters}} and {{Cluster}} business objects should have the following
> work performed:
> - Remove locking around areas where its no longer required
> - Replace collections with thread-safe concurrent versions
> - Remove some reliance on state-full business objects (caches)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18476) Ambari UI changes to support PAM authentication
[
https://issues.apache.org/jira/browse/AMBARI-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542922#comment-15542922
]
Hadoop QA commented on AMBARI-18476:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831340/AMBARI-18476.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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-admin.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8789//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8789//console
This message is automatically generated.
> Ambari UI changes to support PAM authentication
> ---
>
> Key: AMBARI-18476
> URL: https://issues.apache.org/jira/browse/AMBARI-18476
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: trunk
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
> Attachments: AMBARI-18476.patch
>
>
> AMBARI-12263 adds support for PAM as authentication mechanism for accessing
> Ambari UI/REST.
> Since a new column group_type has been added for groups, the UI will display
> labels for group type and enable/disable group delete/add member
> functionality based on the group_type instead of the ldap_group flag.
> The user_type will be used to determine if the user can be deleted or if the
> user's password can be changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18514) Graph details popup: file formats dropdown isn't collapsed on text link click
[ https://issues.apache.org/jira/browse/AMBARI-18514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-18514: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and 2.5 > Graph details popup: file formats dropdown isn't collapsed on text link click > - > > Key: AMBARI-18514 > URL: https://issues.apache.org/jira/browse/AMBARI-18514 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.0 > > Attachments: AMBARI-18514.patch, graph-details.jpg > > > In graph popup details, dropdown menu with exported file formats should be > toggled with click on 'Export' link or download icon.Expansion works fine, > unlike collapse. > See [screenshot attached|^graph-details.jpg]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18499) Ability to remove broken symbolic links via HostCleanup.py
[ https://issues.apache.org/jira/browse/AMBARI-18499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542894#comment-15542894 ] Hudson commented on AMBARI-18499: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5752 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5752/]) AMBARI-18499 Ability to remove broken symbolic links via HostCleanup.py (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7b15e388c37cd2cabf224568760ab127d07412ca]) * (edit) ambari-agent/src/main/python/ambari_agent/HostCleanup.py > Ability to remove broken symbolic links via HostCleanup.py > -- > > Key: AMBARI-18499 > URL: https://issues.apache.org/jira/browse/AMBARI-18499 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18499.patch > > > This is to add the ability to remove broken symbolic links via > HostCleanup.py. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18515) Write unittests for configs.py
[
https://issues.apache.org/jira/browse/AMBARI-18515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542883#comment-15542883
]
Hadoop QA commented on AMBARI-18515:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831324/AMBARI-18515.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/8788//console
This message is automatically generated.
> Write unittests for configs.py
> --
>
> Key: AMBARI-18515
> URL: https://issues.apache.org/jira/browse/AMBARI-18515
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-18515.patch
>
>
> Write/update unittests for configs.py script.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18514) Graph details popup: file formats dropdown isn't collapsed on text link click
[
https://issues.apache.org/jira/browse/AMBARI-18514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542881#comment-15542881
]
Hadoop QA commented on AMBARI-18514:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831318/AMBARI-18514.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8787//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8787//console
This message is automatically generated.
> Graph details popup: file formats dropdown isn't collapsed on text link click
> -
>
> Key: AMBARI-18514
> URL: https://issues.apache.org/jira/browse/AMBARI-18514
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.5.0
>
> Attachments: AMBARI-18514.patch, graph-details.jpg
>
>
> In graph popup details, dropdown menu with exported file formats should be
> toggled with click on 'Export' link or download icon.Expansion works fine,
> unlike collapse.
> See [screenshot attached|^graph-details.jpg].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18513) Analyze and Optimize Ambari Server Unit Tests - Group 7
[
https://issues.apache.org/jira/browse/AMBARI-18513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542825#comment-15542825
]
Hadoop QA commented on AMBARI-18513:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831310/AMBARI-18513.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/8786//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8786//console
This message is automatically generated.
> Analyze and Optimize Ambari Server Unit Tests - Group 7
> ---
>
> Key: AMBARI-18513
> URL: https://issues.apache.org/jira/browse/AMBARI-18513
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-18513.patch
>
>
> Test Count Time (s)
> org.apache.ambari.server.agent.TestHeartbeatHandler
> 24
> 63.327
> org.apache.ambari.server.state.alerts.AlertReceivedListenerTest
> 17
> 48.005
> org.apache.ambari.server.controller.internal.JMXHostProviderTest
> 10
> 35.514
> org.apache.ambari.server.configuration.RecoveryConfigHelperTest
> 8
> 30.128
> org.apache.ambari.server.state.cluster.ClustersDeadlockTest
> 3
> 68.167
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18476) Ambari UI changes to support PAM authentication
[ https://issues.apache.org/jira/browse/AMBARI-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18476: Status: Patch Available (was: Open) > Ambari UI changes to support PAM authentication > --- > > Key: AMBARI-18476 > URL: https://issues.apache.org/jira/browse/AMBARI-18476 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Attachments: AMBARI-18476.patch > > > AMBARI-12263 adds support for PAM as authentication mechanism for accessing > Ambari UI/REST. > Since a new column group_type has been added for groups, the UI will display > labels for group type and enable/disable group delete/add member > functionality based on the group_type instead of the ldap_group flag. > The user_type will be used to determine if the user can be deleted or if the > user's password can be changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18476) Ambari UI changes to support PAM authentication
[ https://issues.apache.org/jira/browse/AMBARI-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18476: Status: Open (was: Patch Available) > Ambari UI changes to support PAM authentication > --- > > Key: AMBARI-18476 > URL: https://issues.apache.org/jira/browse/AMBARI-18476 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Attachments: AMBARI-18476.patch > > > AMBARI-12263 adds support for PAM as authentication mechanism for accessing > Ambari UI/REST. > Since a new column group_type has been added for groups, the UI will display > labels for group type and enable/disable group delete/add member > functionality based on the group_type instead of the ldap_group flag. > The user_type will be used to determine if the user can be deleted or if the > user's password can be changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18476) Ambari UI changes to support PAM authentication
[ https://issues.apache.org/jira/browse/AMBARI-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18476: Attachment: (was: AMBARI-18476.patch) > Ambari UI changes to support PAM authentication > --- > > Key: AMBARI-18476 > URL: https://issues.apache.org/jira/browse/AMBARI-18476 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > > AMBARI-12263 adds support for PAM as authentication mechanism for accessing > Ambari UI/REST. > Since a new column group_type has been added for groups, the UI will display > labels for group type and enable/disable group delete/add member > functionality based on the group_type instead of the ldap_group flag. > The user_type will be used to determine if the user can be deleted or if the > user's password can be changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18476) Ambari UI changes to support PAM authentication
[ https://issues.apache.org/jira/browse/AMBARI-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-18476: Attachment: AMBARI-18476.patch Updated patch that includes new file that was added as part of these changes. > Ambari UI changes to support PAM authentication > --- > > Key: AMBARI-18476 > URL: https://issues.apache.org/jira/browse/AMBARI-18476 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran > Attachments: AMBARI-18476.patch > > > AMBARI-12263 adds support for PAM as authentication mechanism for accessing > Ambari UI/REST. > Since a new column group_type has been added for groups, the UI will display > labels for group type and enable/disable group delete/add member > functionality based on the group_type instead of the ldap_group flag. > The user_type will be used to determine if the user can be deleted or if the > user's password can be changed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18499) Ability to remove broken symbolic links via HostCleanup.py
[ https://issues.apache.org/jira/browse/AMBARI-18499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-18499: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Ability to remove broken symbolic links via HostCleanup.py > -- > > Key: AMBARI-18499 > URL: https://issues.apache.org/jira/browse/AMBARI-18499 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18499.patch > > > This is to add the ability to remove broken symbolic links via > HostCleanup.py. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18499) Ability to remove broken symbolic links via HostCleanup.py
[ https://issues.apache.org/jira/browse/AMBARI-18499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542706#comment-15542706 ] Di Li commented on AMBARI-18499: pushed to trunk as https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=7b15e388c37cd2cabf224568760ab127d07412ca > Ability to remove broken symbolic links via HostCleanup.py > -- > > Key: AMBARI-18499 > URL: https://issues.apache.org/jira/browse/AMBARI-18499 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-18499.patch > > > This is to add the ability to remove broken symbolic links via > HostCleanup.py. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18516) Add ability to have services declare itself as tech-preview or mandatory
[ https://issues.apache.org/jira/browse/AMBARI-18516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18516: --- Attachment: AMBARI-18516.patch > Add ability to have services declare itself as tech-preview or mandatory > > > Key: AMBARI-18516 > URL: https://issues.apache.org/jira/browse/AMBARI-18516 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18516.patch > > > When a service is added to a stack, it should be identified as: > default/regular - service is optional on the cluster, UI usually shows it as > tech-preview - service may be deployed, UI will not auto-select these > services and mark them as TechPreview > mandatory - service need to be deployed and all deployment should fail is the > service is not selected during deployment > Lets create a proposal of what changes are needed in the services' > metainfo.xml? Note that a service can change its attribute between stack > versions - e.g. move from "tech-preview" to "mandatory". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18516) Add ability to have services declare itself as tech-preview or mandatory
[ https://issues.apache.org/jira/browse/AMBARI-18516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-18516: --- Status: Patch Available (was: Open) > Add ability to have services declare itself as tech-preview or mandatory > > > Key: AMBARI-18516 > URL: https://issues.apache.org/jira/browse/AMBARI-18516 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18516.patch > > > When a service is added to a stack, it should be identified as: > default/regular - service is optional on the cluster, UI usually shows it as > tech-preview - service may be deployed, UI will not auto-select these > services and mark them as TechPreview > mandatory - service need to be deployed and all deployment should fail is the > service is not selected during deployment > Lets create a proposal of what changes are needed in the services' > metainfo.xml? Note that a service can change its attribute between stack > versions - e.g. move from "tech-preview" to "mandatory". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18516) Add ability to have services declare itself as tech-preview or mandatory
Vitaly Brodetskyi created AMBARI-18516: -- Summary: Add ability to have services declare itself as tech-preview or mandatory Key: AMBARI-18516 URL: https://issues.apache.org/jira/browse/AMBARI-18516 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Vitaly Brodetskyi Assignee: Vitaly Brodetskyi Priority: Critical Fix For: 2.5.0 When a service is added to a stack, it should be identified as: default/regular - service is optional on the cluster, UI usually shows it as tech-preview - service may be deployed, UI will not auto-select these services and mark them as TechPreview mandatory - service need to be deployed and all deployment should fail is the service is not selected during deployment Lets create a proposal of what changes are needed in the services' metainfo.xml? Note that a service can change its attribute between stack versions - e.g. move from "tech-preview" to "mandatory". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18512) Ambari-Server restart causes all host components to go in Heartbeat Lost state indefinitely.
[ https://issues.apache.org/jira/browse/AMBARI-18512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542641#comment-15542641 ] Sumit Mohanty commented on AMBARI-18512: Thanks [~echekanskiy]. How does it surface on an ambari restart only? > Ambari-Server restart causes all host components to go in Heartbeat Lost > state indefinitely. > > > Key: AMBARI-18512 > URL: https://issues.apache.org/jira/browse/AMBARI-18512 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-18512.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18512) Ambari-Server restart causes all host components to go in Heartbeat Lost state indefinitely.
[
https://issues.apache.org/jira/browse/AMBARI-18512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542614#comment-15542614
]
Hadoop QA commented on AMBARI-18512:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831306/AMBARI-18512.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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/8785//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8785//console
This message is automatically generated.
> Ambari-Server restart causes all host components to go in Heartbeat Lost
> state indefinitely.
>
>
> Key: AMBARI-18512
> URL: https://issues.apache.org/jira/browse/AMBARI-18512
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-18512.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18512) Ambari-Server restart causes all host components to go in Heartbeat Lost state indefinitely.
[ https://issues.apache.org/jira/browse/AMBARI-18512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542615#comment-15542615 ] Eugene Chekanskiy commented on AMBARI-18512: [~sumitmohanty], [~aonishuk], some old python versions have problems with sslv3, so we patching python ssl module to use other protocol version. But we caught problems with this patching during status commands execution. ssl module was patched in status command code, but module that contains patched function removed from python after status command execution and patched function remains, that causing this patched function have broken context(all imports are None). In patch we moved patching to common code and added check if ssl module already patched. > Ambari-Server restart causes all host components to go in Heartbeat Lost > state indefinitely. > > > Key: AMBARI-18512 > URL: https://issues.apache.org/jira/browse/AMBARI-18512 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-18512.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18512) Ambari-Server restart causes all host components to go in Heartbeat Lost state indefinitely.
[ https://issues.apache.org/jira/browse/AMBARI-18512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18512: - Description: If there is a status command that takes > 10 seconds to complete, this blocks up sending heartbeats, and results in hearbeat lost. To prevent this we have to blacklist status commands, which take above given timeout. (was: If there is a status command that takes > 10 seconds to complete, this blocks up sending heartbeats, and results in hearbeat lost. To prevent this we have to blacklist commands, which take above given timeout.) > Ambari-Server restart causes all host components to go in Heartbeat Lost > state indefinitely. > > > Key: AMBARI-18512 > URL: https://issues.apache.org/jira/browse/AMBARI-18512 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-18512.patch > > > If there is a status command that takes > 10 seconds to complete, this blocks > up sending heartbeats, and results in hearbeat lost. To prevent this we have > to blacklist status commands, which take above given timeout. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18488) Delete group button always shows tooltip "Cannot Delete Group"
[ https://issues.apache.org/jira/browse/AMBARI-18488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542594#comment-15542594 ] Hudson commented on AMBARI-18488: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5751 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5751/]) AMBARI-18488. Delete group button always shows tooltip "Cannot Delete (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=30eadbf07fe601931e9029c4a7007218b62194ad]) * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/groups/edit.html > Delete group button always shows tooltip "Cannot Delete Group" > --- > > Key: AMBARI-18488 > URL: https://issues.apache.org/jira/browse/AMBARI-18488 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-18488.patch, Delete Group Tooltip.jpg > > > 1. Navigate to Ambari Admin view. > 2. Click on Groups and click on a group that can be deleted (local group for > e.g.). > 3. The Delete Group button is enabled. Hover over the button and the tooltip > "Cannot Delete Group" is seen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-18512) Ambari-Server restart causes all host components to go in Heartbeat Lost state indefinitely.
[ https://issues.apache.org/jira/browse/AMBARI-18512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542580#comment-15542580 ] Andrew Onischuk edited comment on AMBARI-18512 at 10/3/16 2:46 PM: --- cc [~echekanskiy] was (Author: aonishuk): [~echekanskiy] can you please answer > Ambari-Server restart causes all host components to go in Heartbeat Lost > state indefinitely. > > > Key: AMBARI-18512 > URL: https://issues.apache.org/jira/browse/AMBARI-18512 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-18512.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18512) Ambari-Server restart causes all host components to go in Heartbeat Lost state indefinitely.
[ https://issues.apache.org/jira/browse/AMBARI-18512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18512: - Description: (was: If there is a status command that takes > 10 seconds to complete, this blocks up sending heartbeats, and results in hearbeat lost. To prevent this we have to blacklist status commands, which take above given timeout.) > Ambari-Server restart causes all host components to go in Heartbeat Lost > state indefinitely. > > > Key: AMBARI-18512 > URL: https://issues.apache.org/jira/browse/AMBARI-18512 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-18512.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18512) Ambari-Server restart causes all host components to go in Heartbeat Lost state indefinitely.
[ https://issues.apache.org/jira/browse/AMBARI-18512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542580#comment-15542580 ] Andrew Onischuk commented on AMBARI-18512: -- [~echekanskiy] can you please answer > Ambari-Server restart causes all host components to go in Heartbeat Lost > state indefinitely. > > > Key: AMBARI-18512 > URL: https://issues.apache.org/jira/browse/AMBARI-18512 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-18512.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18512) Ambari-Server restart causes all host components to go in Heartbeat Lost state indefinitely.
[ https://issues.apache.org/jira/browse/AMBARI-18512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18512: - Description: If there is a status command that takes > 10 seconds to complete, this blocks up sending heartbeats, and results in hearbeat lost. To prevent this we have to blacklist commands, which take above given timeout. (was: Steps * Deploy cluster using Ambari trunk version. * Restart Ambari Server. * All host components show up as Heartbeat lost after that. FYI, Agent restart fixes the issue. ) > Ambari-Server restart causes all host components to go in Heartbeat Lost > state indefinitely. > > > Key: AMBARI-18512 > URL: https://issues.apache.org/jira/browse/AMBARI-18512 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-18512.patch > > > If there is a status command that takes > 10 seconds to complete, this blocks > up sending heartbeats, and results in hearbeat lost. To prevent this we have > to blacklist commands, which take above given timeout. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18512) Ambari-Server restart causes all host components to go in Heartbeat Lost state indefinitely.
[ https://issues.apache.org/jira/browse/AMBARI-18512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542559#comment-15542559 ] Sumit Mohanty commented on AMBARI-18512: [~aonishuk] can you add some explanation on what the bug is? > Ambari-Server restart causes all host components to go in Heartbeat Lost > state indefinitely. > > > Key: AMBARI-18512 > URL: https://issues.apache.org/jira/browse/AMBARI-18512 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-18512.patch > > > Steps > * Deploy cluster using Ambari trunk version. > * Restart Ambari Server. > * All host components show up as Heartbeat lost after that. > FYI, Agent restart fixes the issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18506) Ambari should present message if stack upgrade path is not available
[
https://issues.apache.org/jira/browse/AMBARI-18506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542556#comment-15542556
]
Hadoop QA commented on AMBARI-18506:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831110/AMBARI-18506.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 4 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-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8784//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8784//console
This message is automatically generated.
> Ambari should present message if stack upgrade path is not available
>
>
> Key: AMBARI-18506
> URL: https://issues.apache.org/jira/browse/AMBARI-18506
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.4.2
>
> Attachments: AMBARI-18506.patch
>
>
> After adding a new stack version to Ambari and selecting it to be installed
> on a specific cluster, the UI changes to the cluster versions page. If the
> upgrade path (aka the upgrade pack) is not available for the transition from
> the current stack version to the new stack version then the selected version
> is not seen on that next screen. This transition is silent leaving the user
> confused as to where the version went.
> For example: Adding HDP 2.5 to a cluster where the current stack is HDP 2.2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18305) (2.5.0 fix) Ambari server upgrade script deletes all .pyc files
[
https://issues.apache.org/jira/browse/AMBARI-18305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542521#comment-15542521
]
Hudson commented on AMBARI-18305:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #101 (See
[https://builds.apache.org/job/Ambari-branch-2.5/101/])
AMBARI-18305. (2.5.0 fix) Ambari server upgrade script deletes all .pyc
(dlysnichenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6d5b0d1bb1dcf247d76b23329bdfd51e0e5b459f])
* (edit) ambari-server/conf/unix/install-helper.sh
* (edit) ambari-agent/conf/unix/install-helper.sh
> (2.5.0 fix) Ambari server upgrade script deletes all .pyc files
> ---
>
> Key: AMBARI-18305
> URL: https://issues.apache.org/jira/browse/AMBARI-18305
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: trunk
>
> Attachments: AMBARI-18305.patch
>
>
> From customer case:
> We are trying upgrade Ambari from 2.2.2 to Ambari 2.4 with the latest
> packages (1226).
> https://issues.apache.org/jira/browse/AMBARI-15947 - "Upgrading Ambari should
> delete any pyc files"
> The patch contains the following two lines
> {code}
> AMBARI_SERVER="${ROOT}/usr/lib/python2.6/site-packages/ambari_server"
> find $AMBARI_SEVER/ -name *.pyc -exec rm {} \;
> {code}
> The AMBARI_SEVER typo basically executes "find / -name *.pyc -exec rm {} \;"
> on the root directory and deletes ALL pyc files from the ambari server
> machine.
> This looks like a bug in the latest Ambari package we released yesterday.
> Considering the command has both "rm" and "*" in the same line, lets see if
> we can use a safer strategy such as changing the CWD and then deleting files.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18463) Regression: krb5JAASLogin.conf is not updated during secure BP install
[
https://issues.apache.org/jira/browse/AMBARI-18463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542509#comment-15542509
]
Hadoop QA commented on AMBARI-18463:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831156/AMBARI-18463_trunk_02.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/8783//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8783//console
This message is automatically generated.
> Regression: krb5JAASLogin.conf is not updated during secure BP install
> --
>
> Key: AMBARI-18463
> URL: https://issues.apache.org/jira/browse/AMBARI-18463
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
> Labels: blueprints, kerberos
> Fix For: 2.5.0
>
> Attachments: AMBARI-18463_branch-2.5_01.patch,
> AMBARI-18463_branch-2.5_02.patch, AMBARI-18463_trunk_01.patch,
> AMBARI-18463_trunk_02.patch
>
>
> When installing a secure cluster using Blueprints, Ambari's
> {{/etc/ambari-server/conf/krb5JAASLogin.conf}} is not updated to reflect the
> details of the Ambari Kerberos identity.
> This was introduced by the patch for AMBARI-18406.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18515) Write unittests for configs.py
Andrew Onischuk created AMBARI-18515: Summary: Write unittests for configs.py Key: AMBARI-18515 URL: https://issues.apache.org/jira/browse/AMBARI-18515 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.5.0 Attachments: AMBARI-18515.patch Write/update unittests for configs.py script. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18515) Write unittests for configs.py
[ https://issues.apache.org/jira/browse/AMBARI-18515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-18515: - Status: Patch Available (was: Open) > Write unittests for configs.py > -- > > Key: AMBARI-18515 > URL: https://issues.apache.org/jira/browse/AMBARI-18515 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.0 > > Attachments: AMBARI-18515.patch > > > Write/update unittests for configs.py script. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
