[jira] [Commented] (AMBARI-18868) Stage and Request status should be persisted in the database
[
https://issues.apache.org/jira/browse/AMBARI-18868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869347#comment-15869347
]
Hadoop QA commented on AMBARI-18868:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852941/AMBARI-18868.5.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 10 new
or modified test files.
{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/10605//console
This message is automatically generated.
> Stage and Request status should be persisted in the database
>
>
> Key: AMBARI-18868
> URL: https://issues.apache.org/jira/browse/AMBARI-18868
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Jaimin Jetly
>Assignee: Jaimin Jetly
> Fix For: 3.0.0
>
> Attachments: AMBARI-18868.2.patch, AMBARI-18868.3.patch,
> AMBARI-18868.4.patch, AMBARI-18868.5.patch, AMBARI-18868.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20031) Adopt optimal default config values for HBase
[ https://issues.apache.org/jira/browse/AMBARI-20031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869332#comment-15869332 ] Hudson commented on AMBARI-20031: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1011 (See [https://builds.apache.org/job/Ambari-branch-2.5/1011/]) AMBARI-20031. Adopt optimal default config values for HBase (Ted Yu via (smohanty: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f81f7ab6eae0032ccecec82e76dd95e5099f0fb5]) * (add) ambari-server/src/main/resources/stacks/HDP/2.6/services/HBASE/configuration/hbase-site.xml > Adopt optimal default config values for HBase > - > > Key: AMBARI-20031 > URL: https://issues.apache.org/jira/browse/AMBARI-20031 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu > Fix For: 2.5.0 > > Attachments: AMBARI-20031.v1.patch, AMBARI-20031.v2.patch > > > The following hbase config parameters have sub-optimal default values: > hbase.regionserver.executor.openregion.threads > hbase.master.namespace.init.timeout > hbase.master.wait.on.regionservers.timeout > This issue is to assign best known values for them -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20035) Duration in BGoperation window should display durations in proper time units
[ https://issues.apache.org/jira/browse/AMBARI-20035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869331#comment-15869331 ] Denys Buzhor commented on AMBARI-20035: --- +1 for patch > Duration in BGoperation window should display durations in proper time units > > > Key: AMBARI-20035 > URL: https://issues.apache.org/jira/browse/AMBARI-20035 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-20035.patch, Screen Shot 2017-01-30 at 5.08.27 > PM.png > > > Duration of BG operations which took more than 1 hour is displayed in > incorrect time formats. > For. E.g 1.71 hours > It should display the duration in appropriate time units like 2.11 hours or > 111 mins > Attaching screenshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20035) Duration in BGoperation window should display durations in proper time units
[
https://issues.apache.org/jira/browse/AMBARI-20035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869329#comment-15869329
]
Hadoop QA commented on AMBARI-20035:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852964/AMBARI-20035.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 7 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/10604//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10604//console
This message is automatically generated.
> Duration in BGoperation window should display durations in proper time units
>
>
> Key: AMBARI-20035
> URL: https://issues.apache.org/jira/browse/AMBARI-20035
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-20035.patch, Screen Shot 2017-01-30 at 5.08.27
> PM.png
>
>
> Duration of BG operations which took more than 1 hour is displayed in
> incorrect time formats.
> For. E.g 1.71 hours
> It should display the duration in appropriate time units like 2.11 hours or
> 111 mins
> Attaching screenshot
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19823) If by any case Migration Is hampered Then No message is shown in UI Hue-Ambari Migration view
[ https://issues.apache.org/jira/browse/AMBARI-19823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869288#comment-15869288 ] Hudson commented on AMBARI-19823: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1010 (See [https://builds.apache.org/job/Ambari-branch-2.5/1010/]) AMBARI-19823. If by any case Migration Is hampered Then No message is (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0255354df9f5b9a8959bd42b5e38026ae466b143]) * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/hive/historyquery/HiveHistoryMigrationUtility.java * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/pig/pigudf/PigUdfMigrationImplementation.java * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/hive/savedquery/HiveSavedQueryMigrationImplementation.java * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/routes/home-page/hive-saved-query.js * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/routes/home-page/pig-script.js * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/routes/home-page/pig-udf.js * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/templates/home-page/pig-job.hbs * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/pig/pigjob/PigJobMigrationImplementation.java * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/resources/scripts/models/MigrationResponse.java * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/templates/home-page/hive-saved-query.hbs * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/pig/pigjob/PigJobMigrationUtility.java * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/pig/pigudf/PigUdfMigrationUtility.java * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/pig/pigscript/PigScriptMigrationUtility.java * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/templates/home-page/pig-script.hbs * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/models/checkprogress.js * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/routes/home-page/pig-job.js * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/templates/home-page/pig-udf.hbs * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/pig/pigscript/PigScriptMigrationImplementation.java * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/routes/home-page/hive-history.js * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/hive/historyquery/HiveHistoryQueryMigrationImplementation.java * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/hive/savedquery/HiveSavedQueryMigrationUtility.java * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/templates/home-page/hive-history.hbs > If by any case Migration Is hampered Then No message is shown in UI > Hue-Ambari Migration view > - > > Key: AMBARI-19823 > URL: https://issues.apache.org/jira/browse/AMBARI-19823 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: 2.5.0 > > Attachments: AMBARI-19823.patch > > > Steps to reproduce. > 1. Create a successful Hue To Ambari migration view by giving all the > parameters in view creation page. > 2. Run The initial check > 3. After reaching the home-screen of the view. Stop The Database Service(hue > db/ambari db). > 4. After clicking on the Submit Button. The progress freezes. > 5. In the Logs message is displayed "Database connection refused" > Hence the desired behavior should be, if by any reason migration is hampered > the appropriate message should be displayed in UI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20031) Adopt optimal default config values for HBase
[
https://issues.apache.org/jira/browse/AMBARI-20031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869287#comment-15869287
]
Hadoop QA commented on AMBARI-20031:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852971/AMBARI-20031.v2.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/10603//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10603//console
This message is automatically generated.
> Adopt optimal default config values for HBase
> -
>
> Key: AMBARI-20031
> URL: https://issues.apache.org/jira/browse/AMBARI-20031
> Project: Ambari
> Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Ted Yu
> Fix For: 2.5.0
>
> Attachments: AMBARI-20031.v1.patch, AMBARI-20031.v2.patch
>
>
> The following hbase config parameters have sub-optimal default values:
> hbase.regionserver.executor.openregion.threads
> hbase.master.namespace.init.timeout
> hbase.master.wait.on.regionservers.timeout
> This issue is to assign best known values for them
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19979) Issue while resetting the coordinator
[ https://issues.apache.org/jira/browse/AMBARI-19979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Belliraj HB updated AMBARI-19979: - Description: User is not able to reset the coordinator. Steps to reproduce : 1) Import the attached coordinator. 2) Import the same coordinator in different window 3) Try to preview the xml or reset the coordinator. The UI is getting hung. was: User is not able to reset the coordinator. Steps to reproduce : 1) Import the attached coordinator. 2) Now try to reset the coordinator. 3) Content is not reset even after completing reset flow. > Issue while resetting the coordinator > - > > Key: AMBARI-19979 > URL: https://issues.apache.org/jira/browse/AMBARI-19979 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Supreeth Sharma >Assignee: venkat >Priority: Critical > Labels: WFD, WFM > Fix For: 2.5.0 > > Attachments: AMBARI-19979.branch-2.5.patch > > > User is not able to reset the coordinator. > Steps to reproduce : > 1) Import the attached coordinator. > 2) Import the same coordinator in different window > 3) Try to preview the xml or reset the coordinator. The UI is getting hung. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19823) If by any case Migration Is hampered Then No message is shown in UI Hue-Ambari Migration view
[ https://issues.apache.org/jira/browse/AMBARI-19823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869284#comment-15869284 ] Hudson commented on AMBARI-19823: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6756 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6756/]) AMBARI-19823. If by any case Migration Is hampered Then No message is (grvngr: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4aa0f6234e42b2328e2b0b3f435a1b13d27412a9]) * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/hive/savedquery/HiveSavedQueryMigrationImplementation.java * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/routes/home-page/hive-saved-query.js * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/routes/home-page/pig-udf.js * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/pig/pigjob/PigJobMigrationUtility.java * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/hive/historyquery/HiveHistoryMigrationUtility.java * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/pig/pigscript/PigScriptMigrationImplementation.java * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/pig/pigudf/PigUdfMigrationImplementation.java * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/templates/home-page/hive-saved-query.hbs * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/hive/historyquery/HiveHistoryQueryMigrationImplementation.java * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/resources/scripts/models/MigrationResponse.java * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/routes/home-page/hive-history.js * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/hive/savedquery/HiveSavedQueryMigrationUtility.java * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/templates/home-page/pig-job.hbs * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/routes/home-page/pig-script.js * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/pig/pigudf/PigUdfMigrationUtility.java * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/pig/pigjob/PigJobMigrationImplementation.java * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/templates/home-page/hive-history.hbs * (edit) contrib/views/hueambarimigration/src/main/java/org/apache/ambari/view/huetoambarimigration/migration/pig/pigscript/PigScriptMigrationUtility.java * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/templates/home-page/pig-script.hbs * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/models/checkprogress.js * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/routes/home-page/pig-job.js * (edit) contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/app/templates/home-page/pig-udf.hbs > If by any case Migration Is hampered Then No message is shown in UI > Hue-Ambari Migration view > - > > Key: AMBARI-19823 > URL: https://issues.apache.org/jira/browse/AMBARI-19823 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: 2.5.0 > > Attachments: AMBARI-19823.patch > > > Steps to reproduce. > 1. Create a successful Hue To Ambari migration view by giving all the > parameters in view creation page. > 2. Run The initial check > 3. After reaching the home-screen of the view. Stop The Database Service(hue > db/ambari db). > 4. After clicking on the Submit Button. The progress freezes. > 5. In the Logs message is displayed "Database connection refused" > Hence the desired behavior should be, if by any reason migration is hampered > the appropriate message should be displayed in UI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20031) Adopt optimal default config values for HBase
[ https://issues.apache.org/jira/browse/AMBARI-20031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20031: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 > Adopt optimal default config values for HBase > - > > Key: AMBARI-20031 > URL: https://issues.apache.org/jira/browse/AMBARI-20031 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu > Fix For: 2.5.0 > > Attachments: AMBARI-20031.v1.patch, AMBARI-20031.v2.patch > > > The following hbase config parameters have sub-optimal default values: > hbase.regionserver.executor.openregion.threads > hbase.master.namespace.init.timeout > hbase.master.wait.on.regionservers.timeout > This issue is to assign best known values for them -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20030) Zeppelin and Atlas Service Checks Are Missing During Express Upgrades
[ https://issues.apache.org/jira/browse/AMBARI-20030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869255#comment-15869255 ] Hudson commented on AMBARI-20030: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1009 (See [https://builds.apache.org/job/Ambari-branch-2.5/1009/]) AMBARI-20030 - Zeppelin and Atlas Service Checks Are Missing During (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1b6d1937a0c45bbad8c999ea016c463b2b1b9005]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.5.xml > Zeppelin and Atlas Service Checks Are Missing During Express Upgrades > - > > Key: AMBARI-20030 > URL: https://issues.apache.org/jira/browse/AMBARI-20030 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20030.patch > > > Both Atlas and Zeppelin participate in HDP upgrades from HDP 2.5 onward, but > neither of them have service checks after they have upgraded. > This issue is isolated to the express upgrade orchestration since rolling > upgrades schedules all installed services while express orchestration only > runs those specified in the pack. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20030) Zeppelin and Atlas Service Checks Are Missing During Express Upgrades
[ https://issues.apache.org/jira/browse/AMBARI-20030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15869243#comment-15869243 ] Hudson commented on AMBARI-20030: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6755 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6755/]) AMBARI-20030 - Zeppelin and Atlas Service Checks Are Missing During (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d4c1ace80b46deb7982b1da28025927f00a4123e]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.5.xml > Zeppelin and Atlas Service Checks Are Missing During Express Upgrades > - > > Key: AMBARI-20030 > URL: https://issues.apache.org/jira/browse/AMBARI-20030 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20030.patch > > > Both Atlas and Zeppelin participate in HDP upgrades from HDP 2.5 onward, but > neither of them have service checks after they have upgraded. > This issue is isolated to the express upgrade orchestration since rolling > upgrades schedules all installed services while express orchestration only > runs those specified in the pack. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19823) If by any case Migration Is hampered Then No message is shown in UI Hue-Ambari Migration view
[ https://issues.apache.org/jira/browse/AMBARI-19823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-19823: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.5 and trunk. > If by any case Migration Is hampered Then No message is shown in UI > Hue-Ambari Migration view > - > > Key: AMBARI-19823 > URL: https://issues.apache.org/jira/browse/AMBARI-19823 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk > > Attachments: AMBARI-19823.patch > > > Steps to reproduce. > 1. Create a successful Hue To Ambari migration view by giving all the > parameters in view creation page. > 2. Run The initial check > 3. After reaching the home-screen of the view. Stop The Database Service(hue > db/ambari db). > 4. After clicking on the Submit Button. The progress freezes. > 5. In the Logs message is displayed "Database connection refused" > Hence the desired behavior should be, if by any reason migration is hampered > the appropriate message should be displayed in UI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19823) If by any case Migration Is hampered Then No message is shown in UI Hue-Ambari Migration view
[ https://issues.apache.org/jira/browse/AMBARI-19823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Nagar updated AMBARI-19823: -- Fix Version/s: (was: trunk) 2.5.0 > If by any case Migration Is hampered Then No message is shown in UI > Hue-Ambari Migration view > - > > Key: AMBARI-19823 > URL: https://issues.apache.org/jira/browse/AMBARI-19823 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: 2.5.0 > > Attachments: AMBARI-19823.patch > > > Steps to reproduce. > 1. Create a successful Hue To Ambari migration view by giving all the > parameters in view creation page. > 2. Run The initial check > 3. After reaching the home-screen of the view. Stop The Database Service(hue > db/ambari db). > 4. After clicking on the Submit Button. The progress freezes. > 5. In the Logs message is displayed "Database connection refused" > Hence the desired behavior should be, if by any reason migration is hampered > the appropriate message should be displayed in UI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20030) Zeppelin and Atlas Service Checks Are Missing During Express Upgrades
[ https://issues.apache.org/jira/browse/AMBARI-20030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley updated AMBARI-20030: - Resolution: Fixed Status: Resolved (was: Patch Available) > Zeppelin and Atlas Service Checks Are Missing During Express Upgrades > - > > Key: AMBARI-20030 > URL: https://issues.apache.org/jira/browse/AMBARI-20030 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20030.patch > > > Both Atlas and Zeppelin participate in HDP upgrades from HDP 2.5 onward, but > neither of them have service checks after they have upgraded. > This issue is isolated to the express upgrade orchestration since rolling > upgrades schedules all installed services while express orchestration only > runs those specified in the pack. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20031) Adopt optimal default config values for HBase
[ https://issues.apache.org/jira/browse/AMBARI-20031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-20031: Attachment: AMBARI-20031.v2.patch > Adopt optimal default config values for HBase > - > > Key: AMBARI-20031 > URL: https://issues.apache.org/jira/browse/AMBARI-20031 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu > Fix For: 2.5.0 > > Attachments: AMBARI-20031.v1.patch, AMBARI-20031.v2.patch > > > The following hbase config parameters have sub-optimal default values: > hbase.regionserver.executor.openregion.threads > hbase.master.namespace.init.timeout > hbase.master.wait.on.regionservers.timeout > This issue is to assign best known values for them -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20031) Adopt optimal default config values for HBase
[ https://issues.apache.org/jira/browse/AMBARI-20031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated AMBARI-20031: --- Fix Version/s: 2.5.0 > Adopt optimal default config values for HBase > - > > Key: AMBARI-20031 > URL: https://issues.apache.org/jira/browse/AMBARI-20031 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu > Fix For: 2.5.0 > > Attachments: AMBARI-20031.v1.patch > > > The following hbase config parameters have sub-optimal default values: > hbase.regionserver.executor.openregion.threads > hbase.master.namespace.init.timeout > hbase.master.wait.on.regionservers.timeout > This issue is to assign best known values for them -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20035) Duration in BGoperation window should display durations in proper time units
[ https://issues.apache.org/jira/browse/AMBARI-20035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-20035: - Attachment: AMBARI-20035.patch > Duration in BGoperation window should display durations in proper time units > > > Key: AMBARI-20035 > URL: https://issues.apache.org/jira/browse/AMBARI-20035 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-20035.patch, Screen Shot 2017-01-30 at 5.08.27 > PM.png > > > Duration of BG operations which took more than 1 hour is displayed in > incorrect time formats. > For. E.g 1.71 hours > It should display the duration in appropriate time units like 2.11 hours or > 111 mins > Attaching screenshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20035) Duration in BGoperation window should display durations in proper time units
[ https://issues.apache.org/jira/browse/AMBARI-20035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-20035: - Status: Patch Available (was: Open) > Duration in BGoperation window should display durations in proper time units > > > Key: AMBARI-20035 > URL: https://issues.apache.org/jira/browse/AMBARI-20035 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-20035.patch, Screen Shot 2017-01-30 at 5.08.27 > PM.png > > > Duration of BG operations which took more than 1 hour is displayed in > incorrect time formats. > For. E.g 1.71 hours > It should display the duration in appropriate time units like 2.11 hours or > 111 mins > Attaching screenshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19999) Hive View 2.0 upload table issues
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-1: --- Resolution: Fixed Status: Resolved (was: Patch Available) committed to branch-2.5 and trunk > Hive View 2.0 upload table issues > - > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.0 > > Attachments: AMBARI-1_branch-2.5.patch > > > following bugs in upload table feature: > 1. does not support to specify endlines in input file's fields > 2. if column datatype is char or varchar it gives error. > 3. temporary table does not get deleted if error occurs in table upload. > Options -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20036) UX: design new Services Actions
[ https://issues.apache.org/jira/browse/AMBARI-20036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-20036: - Attachment: AMBARI-20036.patch > UX: design new Services Actions > > > Key: AMBARI-20036 > URL: https://issues.apache.org/jira/browse/AMBARI-20036 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-20036.patch > > > Now we have a button "Actions" with dropdown on the old service menu to > trigger actions to all services. > Need a new design and location of them. > Maybe on the new Side Nav or "Services" page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20036) UX: design new Services Actions
Xi Wang created AMBARI-20036: Summary: UX: design new Services Actions Key: AMBARI-20036 URL: https://issues.apache.org/jira/browse/AMBARI-20036 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Xi Wang Assignee: Xi Wang Fix For: 3.0.0 Now we have a button "Actions" with dropdown on the old service menu to trigger actions to all services. Need a new design and location of them. Maybe on the new Side Nav or "Services" page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-18868) Stage and Request status should be persisted in the database
[ https://issues.apache.org/jira/browse/AMBARI-18868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-18868: -- Attachment: AMBARI-18868.5.patch > Stage and Request status should be persisted in the database > > > Key: AMBARI-18868 > URL: https://issues.apache.org/jira/browse/AMBARI-18868 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 3.0.0 > > Attachments: AMBARI-18868.2.patch, AMBARI-18868.3.patch, > AMBARI-18868.4.patch, AMBARI-18868.5.patch, AMBARI-18868.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-18868) Stage and Request status should be persisted in the database
[ https://issues.apache.org/jira/browse/AMBARI-18868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-18868: -- Attachment: (was: AMBARI-18868.5.patch) > Stage and Request status should be persisted in the database > > > Key: AMBARI-18868 > URL: https://issues.apache.org/jira/browse/AMBARI-18868 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 3.0.0 > > Attachments: AMBARI-18868.2.patch, AMBARI-18868.3.patch, > AMBARI-18868.4.patch, AMBARI-18868.5.patch, AMBARI-18868.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-18868) Stage and Request status should be persisted in the database
[ https://issues.apache.org/jira/browse/AMBARI-18868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaimin Jetly updated AMBARI-18868: -- Attachment: AMBARI-18868.5.patch > Stage and Request status should be persisted in the database > > > Key: AMBARI-18868 > URL: https://issues.apache.org/jira/browse/AMBARI-18868 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly > Fix For: 3.0.0 > > Attachments: AMBARI-18868.2.patch, AMBARI-18868.3.patch, > AMBARI-18868.4.patch, AMBARI-18868.5.patch, AMBARI-18868.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20017) PixieDust - Decrease Service Check running time under 3 mins
[
https://issues.apache.org/jira/browse/AMBARI-20017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868828#comment-15868828
]
Hadoop QA commented on AMBARI-20017:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852896/AMBARI-20017.2.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/10602//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10602//console
This message is automatically generated.
> PixieDust - Decrease Service Check running time under 3 mins
>
>
> Key: AMBARI-20017
> URL: https://issues.apache.org/jira/browse/AMBARI-20017
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-20017.2.patch, AMBARI-20017.patch
>
>
> Right now, Ambari has a timeout of 5-10 mins for Service Checks.
> We need to ensure service checks pass in less than 3 mins for all services.
> This means we need to potentially use a different configuration property if
> one doesn't exist already so that QE can set it during the Ambari devdeploy
> tests (in order to speed up the tests).
> This will likely result in bugs in either the Ambari python scripts or the
> actual services, for which we will create Jiras and assign to the appropriate
> stack team.
> This patch implements cluster_env/strict_service_check_type property.
> Possible values are minimal (handled inside service check, runs shorter
> service check action) and full (default action). If value is minimal, I also
> reduce service check timeout when generating command on server in 2 times.
> This way we adapt to service check timeouts that may be different for
> different services. If service check takes 9 minutes of 10-minute timeout to
> pass on our non-busy cluster, then it will probably take more then 10 minutes
> on customers real cluster, and that is bad thing (bug)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20035) Duration in BGoperation window should display durations in proper time units
[ https://issues.apache.org/jira/browse/AMBARI-20035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-20035: - Attachment: Screen Shot 2017-01-30 at 5.08.27 PM.png > Duration in BGoperation window should display durations in proper time units > > > Key: AMBARI-20035 > URL: https://issues.apache.org/jira/browse/AMBARI-20035 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: Screen Shot 2017-01-30 at 5.08.27 PM.png > > > Duration of BG operations which took more than 1 hour is displayed in > incorrect time formats. > For. E.g 1.71 hours > It should display the duration in appropriate time units like 2.11 hours or > 111 mins > Attaching screenshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20035) Duration in BGoperation window should display durations in proper time units
Antonenko Alexander created AMBARI-20035: Summary: Duration in BGoperation window should display durations in proper time units Key: AMBARI-20035 URL: https://issues.apache.org/jira/browse/AMBARI-20035 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Fix For: 3.0.0 Duration of BG operations which took more than 1 hour is displayed in incorrect time formats. For. E.g 1.71 hours It should display the duration in appropriate time units like 2.11 hours or 111 mins Attaching screenshot -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20031) Adopt optimal default config values for HBase
[
https://issues.apache.org/jira/browse/AMBARI-20031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868778#comment-15868778
]
Hadoop QA commented on AMBARI-20031:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852899/AMBARI-20031.v1.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/10601//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10601//console
This message is automatically generated.
> Adopt optimal default config values for HBase
> -
>
> Key: AMBARI-20031
> URL: https://issues.apache.org/jira/browse/AMBARI-20031
> Project: Ambari
> Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: Ted Yu
> Attachments: AMBARI-20031.v1.patch
>
>
> The following hbase config parameters have sub-optimal default values:
> hbase.regionserver.executor.openregion.threads
> hbase.master.namespace.init.timeout
> hbase.master.wait.on.regionservers.timeout
> This issue is to assign best known values for them
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20033) Typecasting to 'long' from earlier 'float', before setting them the following configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency' max value
[
https://issues.apache.org/jira/browse/AMBARI-20033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868711#comment-15868711
]
Hadoop QA commented on AMBARI-20033:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852909/AMBARI-20033.trunk.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/10600//console
This message is automatically generated.
> Typecasting to 'long' from earlier 'float', before setting them the following
> configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency'
> max value and (3). 'hive.llap.daemon.num.executors' max value.
> --
>
> Key: AMBARI-20033
> URL: https://issues.apache.org/jira/browse/AMBARI-20033
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20033.patch, AMBARI-20033.trunk.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19965) Kerberos properties for druid-superset are not set properly
[
https://issues.apache.org/jira/browse/AMBARI-19965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868695#comment-15868695
]
Hudson commented on AMBARI-19965:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6754 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6754/])
AMBARI-19965. Move kerberos properties for superset to correct level in
(sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=11618bb6f65b9723c7198b6f59ef25515499739e])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/services/DRUID/kerberos.json
> Kerberos properties for druid-superset are not set properly
> ---
>
> Key: AMBARI-19965
> URL: https://issues.apache.org/jira/browse/AMBARI-19965
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-19965.patch
>
>
> When enabling kerberos following properties are not set for druid-superset -
> {code}
> "ENABLE_KERBEROS_AUTHENTICATION": "True",
> "KERBEROS_REINIT_TIME_SEC": "3600"
> {code}
> Found that they are specified at wrong level in the kerberos.json file for
> Druid.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19965) Kerberos properties for druid-superset are not set properly
[
https://issues.apache.org/jira/browse/AMBARI-19965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868646#comment-15868646
]
Hudson commented on AMBARI-19965:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1008 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1008/])
AMBARI-19965. Move kerberos properties for superset to correct level in
(sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d7b068a175ae934b5dd8a76161bd294877644986])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/services/DRUID/kerberos.json
> Kerberos properties for druid-superset are not set properly
> ---
>
> Key: AMBARI-19965
> URL: https://issues.apache.org/jira/browse/AMBARI-19965
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-19965.patch
>
>
> When enabling kerberos following properties are not set for druid-superset -
> {code}
> "ENABLE_KERBEROS_AUTHENTICATION": "True",
> "KERBEROS_REINIT_TIME_SEC": "3600"
> {code}
> Found that they are specified at wrong level in the kerberos.json file for
> Druid.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20033) Typecasting to 'long' from earlier 'float', before setting them the following configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency' max value
[ https://issues.apache.org/jira/browse/AMBARI-20033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868647#comment-15868647 ] Hudson commented on AMBARI-20033: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1008 (See [https://builds.apache.org/job/Ambari-branch-2.5/1008/]) AMBARI-20033. Typecasting to 'long' from earlier 'float', before setting (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e8580c271483a47e944300b452fa58c62a73990b]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py > Typecasting to 'long' from earlier 'float', before setting them the following > configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency' > max value and (3). 'hive.llap.daemon.num.executors' max value. > -- > > Key: AMBARI-20033 > URL: https://issues.apache.org/jira/browse/AMBARI-20033 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20033.patch, AMBARI-20033.trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20028) Operations do not show up in the operations list without a refresh
[ https://issues.apache.org/jira/browse/AMBARI-20028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868635#comment-15868635 ] Hudson commented on AMBARI-20028: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6753 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6753/]) AMBARI-20028 Operations do not show up in the operations list without a (bdenys: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0952b8ff89d871962da19918c00357e8565625c1]) * (edit) ambari-web/app/controllers/main/service/info/configs.js * (edit) ambari-web/app/routes/main.js * (edit) ambari-web/app/mixins/common/track_request_mixin.js > Operations do not show up in the operations list without a refresh > -- > > Key: AMBARI-20028 > URL: https://issues.apache.org/jira/browse/AMBARI-20028 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Denys Buzhor >Assignee: Denys Buzhor >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20028_branch-2.5.patch, AMBARI-20028.patch > > > Restart attempted from the host page. > Ambari asks for a confirmation, shows the operations screen, but doesn't take > any action. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19965) Kerberos properties for druid-superset are not set properly
[
https://issues.apache.org/jira/browse/AMBARI-19965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-19965:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Kerberos properties for druid-superset are not set properly
> ---
>
> Key: AMBARI-19965
> URL: https://issues.apache.org/jira/browse/AMBARI-19965
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-19965.patch
>
>
> When enabling kerberos following properties are not set for druid-superset -
> {code}
> "ENABLE_KERBEROS_AUTHENTICATION": "True",
> "KERBEROS_REINIT_TIME_SEC": "3600"
> {code}
> Found that they are specified at wrong level in the kerberos.json file for
> Druid.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19965) Kerberos properties for druid-superset are not set properly
[
https://issues.apache.org/jira/browse/AMBARI-19965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868625#comment-15868625
]
Swapan Shridhar commented on AMBARI-19965:
--
commit
trunk:
{code}
commit 11618bb6f65b9723c7198b6f59ef25515499739e
Author: Swapan Shridhar
Date: Wed Feb 15 13:44:28 2017 -0800
AMBARI-19965. Move kerberos properties for superset to correct level in
kerberos.json. (Nishant Bangarwa via Swapan Shridhar)
{code}
branch-2.5:
{code}
commit d7b068a175ae934b5dd8a76161bd294877644986
Author: Swapan Shridhar
Date: Wed Feb 15 13:44:28 2017 -0800
AMBARI-19965. Move kerberos properties for superset to correct level in
kerberos.json. (Nishant Bangarwa via Swapan Shridhar)
{code}
> Kerberos properties for druid-superset are not set properly
> ---
>
> Key: AMBARI-19965
> URL: https://issues.apache.org/jira/browse/AMBARI-19965
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-19965.patch
>
>
> When enabling kerberos following properties are not set for druid-superset -
> {code}
> "ENABLE_KERBEROS_AUTHENTICATION": "True",
> "KERBEROS_REINIT_TIME_SEC": "3600"
> {code}
> Found that they are specified at wrong level in the kerberos.json file for
> Druid.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20033) Typecasting to 'long' from earlier 'float', before setting them the following configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency' max value an
[ https://issues.apache.org/jira/browse/AMBARI-20033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20033: - Status: Patch Available (was: Reopened) > Typecasting to 'long' from earlier 'float', before setting them the following > configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency' > max value and (3). 'hive.llap.daemon.num.executors' max value. > -- > > Key: AMBARI-20033 > URL: https://issues.apache.org/jira/browse/AMBARI-20033 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20033.patch, AMBARI-20033.trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20033) Typecasting to 'long' from earlier 'float', before setting them the following configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency' max value an
[ https://issues.apache.org/jira/browse/AMBARI-20033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20033: - Resolution: Fixed Status: Resolved (was: Patch Available) > Typecasting to 'long' from earlier 'float', before setting them the following > configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency' > max value and (3). 'hive.llap.daemon.num.executors' max value. > -- > > Key: AMBARI-20033 > URL: https://issues.apache.org/jira/browse/AMBARI-20033 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20033.patch, AMBARI-20033.trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (AMBARI-20033) Typecasting to 'long' from earlier 'float', before setting them the following configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency' max value a
[ https://issues.apache.org/jira/browse/AMBARI-20033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar reopened AMBARI-20033: -- > Typecasting to 'long' from earlier 'float', before setting them the following > configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency' > max value and (3). 'hive.llap.daemon.num.executors' max value. > -- > > Key: AMBARI-20033 > URL: https://issues.apache.org/jira/browse/AMBARI-20033 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20033.patch, AMBARI-20033.trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20033) Typecasting to 'long' from earlier 'float', before setting them the following configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency' max value
[
https://issues.apache.org/jira/browse/AMBARI-20033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868616#comment-15868616
]
Swapan Shridhar commented on AMBARI-20033:
--
commit
trunk
{code}
commit 90235286c8a4aebb1c5159be89509f6679a6e1da
Author: Swapan Shridhar
Date: Wed Feb 15 13:37:54 2017 -0800
AMBARI-20033. Typecasting to 'long' from earlier 'float', before setting
them the following configs for recommendation : (1). 'llap_concurrency', (2).
'llap_concurrency' max value and (3). 'hive.llap.daemon.num.executors' max
value.
{code}
branch-2.5:
{code}
commit e8580c271483a47e944300b452fa58c62a73990b
Author: Swapan Shridhar
Date: Wed Feb 15 13:39:29 2017 -0800
AMBARI-20033. Typecasting to 'long' from earlier 'float', before setting
them the following configs for recommendation : (1). 'llap_concurrency', (2).
'llap_concurrency' max value and (3). 'hive.llap.daemon.num.executors' max
value.
{code}
> Typecasting to 'long' from earlier 'float', before setting them the following
> configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency'
> max value and (3). 'hive.llap.daemon.num.executors' max value.
> --
>
> Key: AMBARI-20033
> URL: https://issues.apache.org/jira/browse/AMBARI-20033
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-20033.patch, AMBARI-20033.trunk.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20028) Operations do not show up in the operations list without a refresh
[ https://issues.apache.org/jira/browse/AMBARI-20028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868599#comment-15868599 ] Hudson commented on AMBARI-20028: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1007 (See [https://builds.apache.org/job/Ambari-branch-2.5/1007/]) AMBARI-20028 Operations do not show up in the operations list without a (bdenys: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d2de31ee161d3acd6c228ca9c21ee696fefee09a]) * (edit) ambari-web/app/controllers/main/service/info/configs.js * (edit) ambari-web/app/views/common/configs/config_category_container_view.js * (edit) ambari-web/app/mixins/common/track_request_mixin.js * (edit) ambari-web/app/routes/main.js > Operations do not show up in the operations list without a refresh > -- > > Key: AMBARI-20028 > URL: https://issues.apache.org/jira/browse/AMBARI-20028 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Denys Buzhor >Assignee: Denys Buzhor >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20028_branch-2.5.patch, AMBARI-20028.patch > > > Restart attempted from the host page. > Ambari asks for a confirmation, shows the operations screen, but doesn't take > any action. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20030) Zeppelin and Atlas Service Checks Are Missing During Express Upgrades
[
https://issues.apache.org/jira/browse/AMBARI-20030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868592#comment-15868592
]
Hadoop QA commented on AMBARI-20030:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852887/AMBARI-20030.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/10599//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10599//console
This message is automatically generated.
> Zeppelin and Atlas Service Checks Are Missing During Express Upgrades
> -
>
> Key: AMBARI-20030
> URL: https://issues.apache.org/jira/browse/AMBARI-20030
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20030.patch
>
>
> Both Atlas and Zeppelin participate in HDP upgrades from HDP 2.5 onward, but
> neither of them have service checks after they have upgraded.
> This issue is isolated to the express upgrade orchestration since rolling
> upgrades schedules all installed services while express orchestration only
> runs those specified in the pack.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20033) Typecasting to 'long' from earlier 'float', before setting them the following configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency' max value an
[ https://issues.apache.org/jira/browse/AMBARI-20033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20033: - Attachment: AMBARI-20033.trunk.patch > Typecasting to 'long' from earlier 'float', before setting them the following > configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency' > max value and (3). 'hive.llap.daemon.num.executors' max value. > -- > > Key: AMBARI-20033 > URL: https://issues.apache.org/jira/browse/AMBARI-20033 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20033.patch, AMBARI-20033.trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20028) Operations do not show up in the operations list without a refresh
[ https://issues.apache.org/jira/browse/AMBARI-20028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Buzhor updated AMBARI-20028: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Operations do not show up in the operations list without a refresh > -- > > Key: AMBARI-20028 > URL: https://issues.apache.org/jira/browse/AMBARI-20028 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Denys Buzhor >Assignee: Denys Buzhor >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20028_branch-2.5.patch, AMBARI-20028.patch > > > Restart attempted from the host page. > Ambari asks for a confirmation, shows the operations screen, but doesn't take > any action. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20028) Operations do not show up in the operations list without a refresh
[ https://issues.apache.org/jira/browse/AMBARI-20028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868583#comment-15868583 ] Denys Buzhor commented on AMBARI-20028: --- committed to trunk and branch-2.5 > Operations do not show up in the operations list without a refresh > -- > > Key: AMBARI-20028 > URL: https://issues.apache.org/jira/browse/AMBARI-20028 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Denys Buzhor >Assignee: Denys Buzhor >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20028_branch-2.5.patch, AMBARI-20028.patch > > > Restart attempted from the host page. > Ambari asks for a confirmation, shows the operations screen, but doesn't take > any action. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20028) Operations do not show up in the operations list without a refresh
[ https://issues.apache.org/jira/browse/AMBARI-20028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Buzhor updated AMBARI-20028: -- Attachment: AMBARI-20028_branch-2.5.patch > Operations do not show up in the operations list without a refresh > -- > > Key: AMBARI-20028 > URL: https://issues.apache.org/jira/browse/AMBARI-20028 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Denys Buzhor >Assignee: Denys Buzhor >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20028_branch-2.5.patch, AMBARI-20028.patch > > > Restart attempted from the host page. > Ambari asks for a confirmation, shows the operations screen, but doesn't take > any action. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20028) Operations do not show up in the operations list without a refresh
[
https://issues.apache.org/jira/browse/AMBARI-20028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868547#comment-15868547
]
Hadoop QA commented on AMBARI-20028:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852880/AMBARI-20028.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/10598//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10598//console
This message is automatically generated.
> Operations do not show up in the operations list without a refresh
> --
>
> Key: AMBARI-20028
> URL: https://issues.apache.org/jira/browse/AMBARI-20028
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Denys Buzhor
>Assignee: Denys Buzhor
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20028.patch
>
>
> Restart attempted from the host page.
> Ambari asks for a confirmation, shows the operations screen, but doesn't take
> any action.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20034) USER to GROUP mapping (hdfs_user -> hadoop_group) should be stack driven
Madhuvanthi Radhakrishnan created AMBARI-20034: -- Summary: USER to GROUP mapping (hdfs_user -> hadoop_group) should be stack driven Key: AMBARI-20034 URL: https://issues.apache.org/jira/browse/AMBARI-20034 Project: Ambari Issue Type: Bug Reporter: Madhuvanthi Radhakrishnan Assignee: Madhuvanthi Radhakrishnan Fix For: 2.5.0 There is a hard coded logic to creating the user-group mapping for services. This presents an issue for custom services. Fix is to make it stack driven by connecting user to its groups within the configuration/stack definition itself -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20033) Typecasting to 'long' from earlier 'float', before setting them the following configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency' max value an
[ https://issues.apache.org/jira/browse/AMBARI-20033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20033: - Summary: Typecasting to 'long' from earlier 'float', before setting them the following configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency' max value and (3). 'hive.llap.daemon.num.executors' max value. (was: Typecasting to 'long' from earlier 'float', before setting them the following configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency' max value and (3). 'hive.llap.daemon.num.executors' max value to) > Typecasting to 'long' from earlier 'float', before setting them the following > configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency' > max value and (3). 'hive.llap.daemon.num.executors' max value. > -- > > Key: AMBARI-20033 > URL: https://issues.apache.org/jira/browse/AMBARI-20033 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: trunk, 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20033) Typecasting to 'long' from earlier 'float', before setting them the following configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency' max value an
[ https://issues.apache.org/jira/browse/AMBARI-20033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20033: - Summary: Typecasting to 'long' from earlier 'float', before setting them the following configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency' max value and (3). 'hive.llap.daemon.num.executors' max value to (was: Typecasting 'llap_concurrency', 'llap_concurrency' max value and 'hive.llap.daemon.num.executors' max value to 'long' from earlier 'float', before setting them for recommendation.) > Typecasting to 'long' from earlier 'float', before setting them the following > configs for recommendation : (1). 'llap_concurrency', (2). 'llap_concurrency' > max value and (3). 'hive.llap.daemon.num.executors' max value to > > > Key: AMBARI-20033 > URL: https://issues.apache.org/jira/browse/AMBARI-20033 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: trunk, 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20033) Typecasting 'llap_concurrency', 'llap_concurrency' max value and 'hive.llap.daemon.num.executors' max value to 'long' from earlier 'float', before setting them for reco
[ https://issues.apache.org/jira/browse/AMBARI-20033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20033: - Fix Version/s: trunk > Typecasting 'llap_concurrency', 'llap_concurrency' max value and > 'hive.llap.daemon.num.executors' max value to 'long' from earlier 'float', > before setting them for recommendation. > --- > > Key: AMBARI-20033 > URL: https://issues.apache.org/jira/browse/AMBARI-20033 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: trunk, 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20033) Typecasting 'llap_concurrency', 'llap_concurrency' max value and 'hive.llap.daemon.num.executors' max value to 'long' from earlier 'float', before setting them for reco
[ https://issues.apache.org/jira/browse/AMBARI-20033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20033: - Affects Version/s: trunk > Typecasting 'llap_concurrency', 'llap_concurrency' max value and > 'hive.llap.daemon.num.executors' max value to 'long' from earlier 'float', > before setting them for recommendation. > --- > > Key: AMBARI-20033 > URL: https://issues.apache.org/jira/browse/AMBARI-20033 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: trunk, 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20033) Typecasting 'llap_concurrency', 'llap_concurrency' max value and 'hive.llap.daemon.num.executors' max value to 'long' from earlier 'float', before setting them for reco
[ https://issues.apache.org/jira/browse/AMBARI-20033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20033: - Affects Version/s: 2.5.0 > Typecasting 'llap_concurrency', 'llap_concurrency' max value and > 'hive.llap.daemon.num.executors' max value to 'long' from earlier 'float', > before setting them for recommendation. > --- > > Key: AMBARI-20033 > URL: https://issues.apache.org/jira/browse/AMBARI-20033 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Swapan Shridhar > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20033) Typecasting 'llap_concurrency', 'llap_concurrency' max value and 'hive.llap.daemon.num.executors' max value to 'long' from earlier 'float', before setting them for reco
[ https://issues.apache.org/jira/browse/AMBARI-20033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20033: - Fix Version/s: 2.5.0 > Typecasting 'llap_concurrency', 'llap_concurrency' max value and > 'hive.llap.daemon.num.executors' max value to 'long' from earlier 'float', > before setting them for recommendation. > --- > > Key: AMBARI-20033 > URL: https://issues.apache.org/jira/browse/AMBARI-20033 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Swapan Shridhar > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20033) Typecasting 'llap_concurrency', 'llap_concurrency' max value and 'hive.llap.daemon.num.executors' max value to 'long' from earlier 'float', before setting them for reco
Swapan Shridhar created AMBARI-20033: Summary: Typecasting 'llap_concurrency', 'llap_concurrency' max value and 'hive.llap.daemon.num.executors' max value to 'long' from earlier 'float', before setting them for recommendation. Key: AMBARI-20033 URL: https://issues.apache.org/jira/browse/AMBARI-20033 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Swapan Shridhar -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20033) Typecasting 'llap_concurrency', 'llap_concurrency' max value and 'hive.llap.daemon.num.executors' max value to 'long' from earlier 'float', before setting them for rec
[ https://issues.apache.org/jira/browse/AMBARI-20033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar reassigned AMBARI-20033: Assignee: Swapan Shridhar > Typecasting 'llap_concurrency', 'llap_concurrency' max value and > 'hive.llap.daemon.num.executors' max value to 'long' from earlier 'float', > before setting them for recommendation. > --- > > Key: AMBARI-20033 > URL: https://issues.apache.org/jira/browse/AMBARI-20033 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20031) Adopt optimal default config values for HBase
[ https://issues.apache.org/jira/browse/AMBARI-20031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-20031: Attachment: (was: AMBARI-20031.v1.patch) > Adopt optimal default config values for HBase > - > > Key: AMBARI-20031 > URL: https://issues.apache.org/jira/browse/AMBARI-20031 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu > Attachments: AMBARI-20031.v1.patch > > > The following hbase config parameters have sub-optimal default values: > hbase.regionserver.executor.openregion.threads > hbase.master.namespace.init.timeout > hbase.master.wait.on.regionservers.timeout > This issue is to assign best known values for them -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20031) Adopt optimal default config values for HBase
[ https://issues.apache.org/jira/browse/AMBARI-20031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-20031: Attachment: AMBARI-20031.v1.patch > Adopt optimal default config values for HBase > - > > Key: AMBARI-20031 > URL: https://issues.apache.org/jira/browse/AMBARI-20031 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu > Attachments: AMBARI-20031.v1.patch > > > The following hbase config parameters have sub-optimal default values: > hbase.regionserver.executor.openregion.threads > hbase.master.namespace.init.timeout > hbase.master.wait.on.regionservers.timeout > This issue is to assign best known values for them -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20032) HDFS service check fails after Stopping one Namenode in HA cluster
Vivek Rathod created AMBARI-20032: - Summary: HDFS service check fails after Stopping one Namenode in HA cluster Key: AMBARI-20032 URL: https://issues.apache.org/jira/browse/AMBARI-20032 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: Vivek Rathod Fix For: 2.5.0 HDFS service check fails after Stopping one Namenode in HA cluster. Stop the active Namenode and run HDFS service check, it fails. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20017) PixieDust - Decrease Service Check running time under 3 mins
[ https://issues.apache.org/jira/browse/AMBARI-20017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-20017: Attachment: AMBARI-20017.2.patch > PixieDust - Decrease Service Check running time under 3 mins > > > Key: AMBARI-20017 > URL: https://issues.apache.org/jira/browse/AMBARI-20017 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-20017.2.patch, AMBARI-20017.patch > > > Right now, Ambari has a timeout of 5-10 mins for Service Checks. > We need to ensure service checks pass in less than 3 mins for all services. > This means we need to potentially use a different configuration property if > one doesn't exist already so that QE can set it during the Ambari devdeploy > tests (in order to speed up the tests). > This will likely result in bugs in either the Ambari python scripts or the > actual services, for which we will create Jiras and assign to the appropriate > stack team. > This patch implements cluster_env/strict_service_check_type property. > Possible values are minimal (handled inside service check, runs shorter > service check action) and full (default action). If value is minimal, I also > reduce service check timeout when generating command on server in 2 times. > This way we adapt to service check timeouts that may be different for > different services. If service check takes 9 minutes of 10-minute timeout to > pass on our non-busy cluster, then it will probably take more then 10 minutes > on customers real cluster, and that is bad thing (bug) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19965) Kerberos properties for druid-superset are not set properly
[
https://issues.apache.org/jira/browse/AMBARI-19965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868483#comment-15868483
]
Hadoop QA commented on AMBARI-19965:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852085/ambari-19965.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/10597//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10597//console
This message is automatically generated.
> Kerberos properties for druid-superset are not set properly
> ---
>
> Key: AMBARI-19965
> URL: https://issues.apache.org/jira/browse/AMBARI-19965
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-19965.patch
>
>
> When enabling kerberos following properties are not set for druid-superset -
> {code}
> "ENABLE_KERBEROS_AUTHENTICATION": "True",
> "KERBEROS_REINIT_TIME_SEC": "3600"
> {code}
> Found that they are specified at wrong level in the kerberos.json file for
> Druid.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19829) Several HDFS/YARN widgets on Heatmaps show N/A
[ https://issues.apache.org/jira/browse/AMBARI-19829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868463#comment-15868463 ] Hudson commented on AMBARI-19829: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6752 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6752/]) AMBARI-19829: Several HDFS/YARN widgets on Heatmaps show N/A. (Qin Liu (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=dd6fb57d1ab26dad7f13a371f187e7330c2f6450]) * (edit) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/widgets.json * (edit) ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/YARN_widgets.json * (edit) ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/widgets.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/YARN/YARN_widgets.json * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/HDFS/widgets.json * (edit) ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/YARN_widgets.json > Several HDFS/YARN widgets on Heatmaps show N/A > -- > > Key: AMBARI-19829 > URL: https://issues.apache.org/jira/browse/AMBARI-19829 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-19829.patch > > > The following HDFS/YARN widgets on Heatmaps show N/A: > 1. HDFS - HDFS Bytes Written, HDFS Bytes Read, DataNode Process Disk I/O > Utilization, and DataNode Process Network I/O Utilization > 2. YARN - Container Failures > The issue was introduced by AMBARI-15835 "Rate metrics requesting widgets do > not show up on Ambari" which introduced rate metrics and applied rate metrics > to several HBASE/HDFS/YARN widgets on Summary pages as well as Heatmap > pages. Rate metrics work fine on Summary pages but they don't work on Heatmap > pages because current Heatmap design can only show point-in-time metrics and > rate metrics need a time range. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19953) AMS HBase RegionServer process is still alive after switching AMS to embedded mode
[ https://issues.apache.org/jira/browse/AMBARI-19953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868462#comment-15868462 ] Hudson commented on AMBARI-19953: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6752 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6752/]) AMBARI-19953: AMS HBase RegionServer process is still alive after (avijayan: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2db72cdf667a174d43eb7fa3c45166b1734948ae]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams_service.py * (edit) ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_collector.py > AMS HBase RegionServer process is still alive after switching AMS to embedded > mode > -- > > Key: AMBARI-19953 > URL: https://issues.apache.org/jira/browse/AMBARI-19953 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.2 > Environment: >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-19953.patch > > > After switching AMS to embedded mode, AMS HBase region server process from > previous AMS configs is still alive. > Steps to reproduce: > 1. install a cluster with AMS distributed mode > 2. ps -elf | grep ams > 3. switch AMS to embedded mode > 4. restart AMS > 5. ps -elf | grep ams and will see AMS HBase regionserver process from > previous AMS distributed configs is still alive -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20031) Adopt optimal default config values for HBase
[ https://issues.apache.org/jira/browse/AMBARI-20031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-20031: Status: Patch Available (was: Open) > Adopt optimal default config values for HBase > - > > Key: AMBARI-20031 > URL: https://issues.apache.org/jira/browse/AMBARI-20031 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu > Attachments: AMBARI-20031.v1.patch > > > The following hbase config parameters have sub-optimal default values: > hbase.regionserver.executor.openregion.threads > hbase.master.namespace.init.timeout > hbase.master.wait.on.regionservers.timeout > This issue is to assign best known values for them -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20031) Adopt optimal default config values for HBase
[ https://issues.apache.org/jira/browse/AMBARI-20031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-20031: Attachment: AMBARI-20031.v1.patch > Adopt optimal default config values for HBase > - > > Key: AMBARI-20031 > URL: https://issues.apache.org/jira/browse/AMBARI-20031 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu >Assignee: Ted Yu > Attachments: AMBARI-20031.v1.patch > > > The following hbase config parameters have sub-optimal default values: > hbase.regionserver.executor.openregion.threads > hbase.master.namespace.init.timeout > hbase.master.wait.on.regionservers.timeout > This issue is to assign best known values for them -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20031) Adopt optimal default config values for HBase
Ted Yu created AMBARI-20031: --- Summary: Adopt optimal default config values for HBase Key: AMBARI-20031 URL: https://issues.apache.org/jira/browse/AMBARI-20031 Project: Ambari Issue Type: Improvement Reporter: Ted Yu Assignee: Ted Yu The following hbase config parameters have sub-optimal default values: hbase.regionserver.executor.openregion.threads hbase.master.namespace.init.timeout hbase.master.wait.on.regionservers.timeout This issue is to assign best known values for them -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20027) Override property popup: Redundant scrollbars in config groups list
[ https://issues.apache.org/jira/browse/AMBARI-20027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868378#comment-15868378 ] Hudson commented on AMBARI-20027: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6751 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6751/]) AMBARI-20027 Override property popup: Redundant scrollbars in config (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b36f00e2bafa4c65a20bfde57c0a60ff37a68cdb]) * (edit) ambari-web/app/styles/application.less > Override property popup: Redundant scrollbars in config groups list > --- > > Key: AMBARI-20027 > URL: https://issues.apache.org/jira/browse/AMBARI-20027 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-20027.patch > > > *STR* > # Create service config group > # Proceed with overriding any property > # Open existing config groups combobox in displayed popup. > *Result* > Displayed list has redundant horizontal and vertical scrollbars. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20030) Zeppelin and Atlas Service Checks Are Missing During Express Upgrades
Jonathan Hurley created AMBARI-20030: Summary: Zeppelin and Atlas Service Checks Are Missing During Express Upgrades Key: AMBARI-20030 URL: https://issues.apache.org/jira/browse/AMBARI-20030 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Jonathan Hurley Assignee: Jonathan Hurley Priority: Critical Fix For: 2.5.0 Both Atlas and Zeppelin participate in HDP upgrades from HDP 2.5 onward, but neither of them have service checks after they have upgraded. This issue is isolated to the express upgrade orchestration since rolling upgrades schedules all installed services while express orchestration only runs those specified in the pack. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20028) Operations do not show up in the operations list without a refresh
[ https://issues.apache.org/jira/browse/AMBARI-20028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Buzhor updated AMBARI-20028: -- Status: Patch Available (was: Open) > Operations do not show up in the operations list without a refresh > -- > > Key: AMBARI-20028 > URL: https://issues.apache.org/jira/browse/AMBARI-20028 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Denys Buzhor >Assignee: Denys Buzhor >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20028.patch > > > Restart attempted from the host page. > Ambari asks for a confirmation, shows the operations screen, but doesn't take > any action. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20028) Operations do not show up in the operations list without a refresh
[ https://issues.apache.org/jira/browse/AMBARI-20028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Buzhor updated AMBARI-20028: -- Attachment: AMBARI-20028.patch > Operations do not show up in the operations list without a refresh > -- > > Key: AMBARI-20028 > URL: https://issues.apache.org/jira/browse/AMBARI-20028 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Denys Buzhor >Assignee: Denys Buzhor >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20028.patch > > > Restart attempted from the host page. > Ambari asks for a confirmation, shows the operations screen, but doesn't take > any action. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19829) Several HDFS/YARN widgets on Heatmaps show N/A
[ https://issues.apache.org/jira/browse/AMBARI-19829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868302#comment-15868302 ] Qin Liu commented on AMBARI-19829: -- Thank you so much Aravindan! > Several HDFS/YARN widgets on Heatmaps show N/A > -- > > Key: AMBARI-19829 > URL: https://issues.apache.org/jira/browse/AMBARI-19829 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.2.2 >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > Attachments: AMBARI-19829.patch > > > The following HDFS/YARN widgets on Heatmaps show N/A: > 1. HDFS - HDFS Bytes Written, HDFS Bytes Read, DataNode Process Disk I/O > Utilization, and DataNode Process Network I/O Utilization > 2. YARN - Container Failures > The issue was introduced by AMBARI-15835 "Rate metrics requesting widgets do > not show up on Ambari" which introduced rate metrics and applied rate metrics > to several HBASE/HDFS/YARN widgets on Summary pages as well as Heatmap > pages. Rate metrics work fine on Summary pages but they don't work on Heatmap > pages because current Heatmap design can only show point-in-time metrics and > rate metrics need a time range. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19953) AMS HBase RegionServer process is still alive after switching AMS to embedded mode
[ https://issues.apache.org/jira/browse/AMBARI-19953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868301#comment-15868301 ] Qin Liu commented on AMBARI-19953: -- Thank you so much Aravindan! > AMS HBase RegionServer process is still alive after switching AMS to embedded > mode > -- > > Key: AMBARI-19953 > URL: https://issues.apache.org/jira/browse/AMBARI-19953 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.4.2 > Environment: >Reporter: Qin Liu >Assignee: Qin Liu >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-19953.patch > > > After switching AMS to embedded mode, AMS HBase region server process from > previous AMS configs is still alive. > Steps to reproduce: > 1. install a cluster with AMS distributed mode > 2. ps -elf | grep ams > 3. switch AMS to embedded mode > 4. restart AMS > 5. ps -elf | grep ams and will see AMS HBase regionserver process from > previous AMS distributed configs is still alive -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20027) Override property popup: Redundant scrollbars in config groups list
[ https://issues.apache.org/jira/browse/AMBARI-20027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868299#comment-15868299 ] Andrii Babiichuk commented on AMBARI-20027: --- Committed to trunk > Override property popup: Redundant scrollbars in config groups list > --- > > Key: AMBARI-20027 > URL: https://issues.apache.org/jira/browse/AMBARI-20027 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-20027.patch > > > *STR* > # Create service config group > # Proceed with overriding any property > # Open existing config groups combobox in displayed popup. > *Result* > Displayed list has redundant horizontal and vertical scrollbars. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20027) Override property popup: Redundant scrollbars in config groups list
[
https://issues.apache.org/jira/browse/AMBARI-20027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868288#comment-15868288
]
Hadoop QA commented on AMBARI-20027:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852841/AMBARI-20027.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/10595//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10595//console
This message is automatically generated.
> Override property popup: Redundant scrollbars in config groups list
> ---
>
> Key: AMBARI-20027
> URL: https://issues.apache.org/jira/browse/AMBARI-20027
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-20027.patch
>
>
> *STR*
> # Create service config group
> # Proceed with overriding any property
> # Open existing config groups combobox in displayed popup.
> *Result*
> Displayed list has redundant horizontal and vertical scrollbars.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20026) Ambari server start returns prematurely before extracting views.
[ https://issues.apache.org/jira/browse/AMBARI-20026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868247#comment-15868247 ] Hudson commented on AMBARI-20026: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1006 (See [https://builds.apache.org/job/Ambari-branch-2.5/1006/]) AMBARI-20026 Ambari server start returns prematurely before extracting (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=dd33b239176fe05ccad5e59442d2a04e24cf15a1]) * (edit) ambari-server/src/main/python/ambari_server/utils.py * (edit) ambari-server/src/main/python/ambari_server/serverConfiguration.py * (edit) ambari-server/src/test/python/TestAmbariServer.py * (edit) ambari-server/src/main/python/ambari_server_main.py > Ambari server start returns prematurely before extracting views. > > > Key: AMBARI-20026 > URL: https://issues.apache.org/jira/browse/AMBARI-20026 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen > Fix For: 2.5.0 > > Attachments: AMBARI-20026.patch > > > When ambari-server start is issued, It returns prematurely before the view > extraction is complete. > because of this we have introduced sleep of 3mins before ambari-server stop > for the view extraction to complete. > Ambari server should report start completed only after view extraction is > completed -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20026) Ambari server start returns prematurely before extracting views.
[ https://issues.apache.org/jira/browse/AMBARI-20026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868242#comment-15868242 ] Hudson commented on AMBARI-20026: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6750 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6750/]) AMBARI-20026 Ambari server start returns prematurely before extracting (dsen: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e890f01d0f562b81489c44fea9596f3455d8d9bc]) * (edit) ambari-server/src/main/python/ambari_server_main.py > Ambari server start returns prematurely before extracting views. > > > Key: AMBARI-20026 > URL: https://issues.apache.org/jira/browse/AMBARI-20026 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen > Fix For: 2.5.0 > > Attachments: AMBARI-20026.patch > > > When ambari-server start is issued, It returns prematurely before the view > extraction is complete. > because of this we have introduced sleep of 3mins before ambari-server stop > for the view extraction to complete. > Ambari server should report start completed only after view extraction is > completed -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20024) Relax ranger config DB consistency check rules
[
https://issues.apache.org/jira/browse/AMBARI-20024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868240#comment-15868240
]
Hadoop QA commented on AMBARI-20024:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852832/AMBARI-20024.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/10593//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10593//console
This message is automatically generated.
> Relax ranger config DB consistency check rules
> --
>
> Key: AMBARI-20024
> URL: https://issues.apache.org/jira/browse/AMBARI-20024
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-20024.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20018) Document security issue related to setting security.agent.hostname.validate to false
[ https://issues.apache.org/jira/browse/AMBARI-20018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868204#comment-15868204 ] Hudson commented on AMBARI-20018: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1005 (See [https://builds.apache.org/job/Ambari-branch-2.5/1005/]) AMBARI-20018. Document security issue related to setting (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8b5883316f0e1348548e3a2cfcafa0c2a6d21048]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * (edit) ambari-server/docs/configuration/index.md > Document security issue related to setting security.agent.hostname.validate > to false > > > Key: AMBARI-20018 > URL: https://issues.apache.org/jira/browse/AMBARI-20018 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Robert Levas >Assignee: Robert Levas > Fix For: 2.5.0 > > Attachments: AMBARI-20018_branch-2.5_01.patch, > AMBARI-20018_branch-2.5_02.patch, AMBARI-20018_trunk_01.patch, > AMBARI-20018_trunk_02.patch > > > Document security issue related to setting security.agent.hostname.validate > to "false". > If set to "false", invalid hostnames may be used in OpenSSL commands used to > create the agent-side certificates when 2-way SSL is enabled. This could lead > to issues when executing OpenSSL as described in CVE-2014-3582. See > https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20018) Document security issue related to setting security.agent.hostname.validate to false
[ https://issues.apache.org/jira/browse/AMBARI-20018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868177#comment-15868177 ] Hudson commented on AMBARI-20018: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6749 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6749/]) AMBARI-20018. Document security issue related to setting (rlevas: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=45842645c546a176f1692d0d7be008e2d51c5086]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * (edit) ambari-server/docs/configuration/index.md > Document security issue related to setting security.agent.hostname.validate > to false > > > Key: AMBARI-20018 > URL: https://issues.apache.org/jira/browse/AMBARI-20018 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Robert Levas >Assignee: Robert Levas > Fix For: 2.5.0 > > Attachments: AMBARI-20018_branch-2.5_01.patch, > AMBARI-20018_branch-2.5_02.patch, AMBARI-20018_trunk_01.patch, > AMBARI-20018_trunk_02.patch > > > Document security issue related to setting security.agent.hostname.validate > to "false". > If set to "false", invalid hostnames may be used in OpenSSL commands used to > create the agent-side certificates when 2-way SSL is enabled. This could lead > to issues when executing OpenSSL as described in CVE-2014-3582. See > https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20025) Incorrect work of filters on Versions page of Admin View
[ https://issues.apache.org/jira/browse/AMBARI-20025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868178#comment-15868178 ] Hudson commented on AMBARI-20025: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6749 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6749/]) AMBARI-20025 Incorrect work of filters on Versions page of Admin View. (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d75756efa7bcecb09d0ee73db6c29b018ba964fc]) * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsListCtrl.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Stack.js * (edit) ambari-admin/src/main/resources/ui/admin-web/test/unit/controllers/stackVersions/StackversionsListCtrl_test.js > Incorrect work of filters on Versions page of Admin View > > > Key: AMBARI-20025 > URL: https://issues.apache.org/jira/browse/AMBARI-20025 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-20025.patch, _versions-filter.jpg > > > Filter by cluster name doesn't work (while being enabled, showing versions > that are not installed on cluster): [^_versions-filter.jpg] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19957) Implement new DB checks for Postgres to prevent cross-schema confusion
[
https://issues.apache.org/jira/browse/AMBARI-19957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868174#comment-15868174
]
Hadoop QA commented on AMBARI-19957:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852834/AMBARI-19957-DB-checks_25_v4.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/10592//console
This message is automatically generated.
> Implement new DB checks for Postgres to prevent cross-schema confusion
> --
>
> Key: AMBARI-19957
> URL: https://issues.apache.org/jira/browse/AMBARI-19957
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-19957-DB-checks_25_v4.patch,
> AMBARI-19957-DB-checks_trunk_v4.patch
>
>
> Postgres allows multiple schemas on a database user's search path, that is
> users can query from tables in different schemas without the need of
> prefixing the tables in the query.
> This can lead to confusion when after an unsuccessful upgrade DBA's restore
> the tables into a different schema (e.g. public) to Ambari's configured one.
> As a result, Ambari server may see corrupt data.
> New consistency checks on server startup should warn the user in such
> situations.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20026) Ambari server start returns prematurely before extracting views.
[
https://issues.apache.org/jira/browse/AMBARI-20026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868170#comment-15868170
]
Hadoop QA commented on AMBARI-20026:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852838/AMBARI-20026.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/10591//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10591//console
This message is automatically generated.
> Ambari server start returns prematurely before extracting views.
>
>
> Key: AMBARI-20026
> URL: https://issues.apache.org/jira/browse/AMBARI-20026
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.5.0
>
> Attachments: AMBARI-20026.patch
>
>
> When ambari-server start is issued, It returns prematurely before the view
> extraction is complete.
> because of this we have introduced sleep of 3mins before ambari-server stop
> for the view extraction to complete.
> Ambari server should report start completed only after view extraction is
> completed
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20008) Add "Manage alert notifications" authorization
[ https://issues.apache.org/jira/browse/AMBARI-20008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-20008: --- Attachment: AMBARI-20008.trunk-2.patch > Add "Manage alert notifications" authorization > --- > > Key: AMBARI-20008 > URL: https://issues.apache.org/jira/browse/AMBARI-20008 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 2.5.0 > > Attachments: AMBARI-20008.2.5-2.patch, AMBARI-20008.2.5.patch, > AMBARI-20008.trunk-2.patch, AMBARI-20008.trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20008) Add "Manage alert notifications" authorization
[ https://issues.apache.org/jira/browse/AMBARI-20008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-20008: --- Status: Patch Available (was: Open) > Add "Manage alert notifications" authorization > --- > > Key: AMBARI-20008 > URL: https://issues.apache.org/jira/browse/AMBARI-20008 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 2.5.0 > > Attachments: AMBARI-20008.2.5-2.patch, AMBARI-20008.2.5.patch, > AMBARI-20008.trunk-2.patch, AMBARI-20008.trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20008) Add "Manage alert notifications" authorization
[ https://issues.apache.org/jira/browse/AMBARI-20008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-20008: --- Attachment: AMBARI-20008.2.5-2.patch > Add "Manage alert notifications" authorization > --- > > Key: AMBARI-20008 > URL: https://issues.apache.org/jira/browse/AMBARI-20008 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 2.5.0 > > Attachments: AMBARI-20008.2.5-2.patch, AMBARI-20008.2.5.patch, > AMBARI-20008.trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19965) Kerberos properties for druid-superset are not set properly
[
https://issues.apache.org/jira/browse/AMBARI-19965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Bangarwa updated AMBARI-19965:
--
Status: Patch Available (was: Open)
> Kerberos properties for druid-superset are not set properly
> ---
>
> Key: AMBARI-19965
> URL: https://issues.apache.org/jira/browse/AMBARI-19965
> Project: Ambari
> Issue Type: Bug
>Reporter: Nishant Bangarwa
>Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: ambari-19965.patch
>
>
> When enabling kerberos following properties are not set for druid-superset -
> {code}
> "ENABLE_KERBEROS_AUTHENTICATION": "True",
> "KERBEROS_REINIT_TIME_SEC": "3600"
> {code}
> Found that they are specified at wrong level in the kerberos.json file for
> Druid.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19953) AMS HBase RegionServer process is still alive after switching AMS to embedded mode
[
https://issues.apache.org/jira/browse/AMBARI-19953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-19953:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to trunk.
{code}
commit ac8650be8367f4ed0d4897bbc17eaa835cbe150a
Author: Aravindan Vijayan
Date: Wed Feb 15 08:45:07 2017 -0800
AMBARI-19953: AMS HBase RegionServer process is still alive after switching
AMS to embedded mode. (Qin Liu via avijayan)
{code}
> AMS HBase RegionServer process is still alive after switching AMS to embedded
> mode
> --
>
> Key: AMBARI-19953
> URL: https://issues.apache.org/jira/browse/AMBARI-19953
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.2
> Environment:
>Reporter: Qin Liu
>Assignee: Qin Liu
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-19953.patch
>
>
> After switching AMS to embedded mode, AMS HBase region server process from
> previous AMS configs is still alive.
> Steps to reproduce:
> 1. install a cluster with AMS distributed mode
> 2. ps -elf | grep ams
> 3. switch AMS to embedded mode
> 4. restart AMS
> 5. ps -elf | grep ams and will see AMS HBase regionserver process from
> previous AMS distributed configs is still alive
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19829) Several HDFS/YARN widgets on Heatmaps show N/A
[
https://issues.apache.org/jira/browse/AMBARI-19829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-19829:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to trunk.
{code}
commit 2e1893b15d6217c08575124ffbafa5ff60f24d21
Author: Aravindan Vijayan
Date: Wed Feb 15 08:43:28 2017 -0800
AMBARI-19829: Several HDFS/YARN widgets on Heatmaps show N/A. (Qin Liu via
avijayan)
{code}
> Several HDFS/YARN widgets on Heatmaps show N/A
> --
>
> Key: AMBARI-19829
> URL: https://issues.apache.org/jira/browse/AMBARI-19829
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.2.2
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
> Attachments: AMBARI-19829.patch
>
>
> The following HDFS/YARN widgets on Heatmaps show N/A:
> 1. HDFS - HDFS Bytes Written, HDFS Bytes Read, DataNode Process Disk I/O
> Utilization, and DataNode Process Network I/O Utilization
> 2. YARN - Container Failures
> The issue was introduced by AMBARI-15835 "Rate metrics requesting widgets do
> not show up on Ambari" which introduced rate metrics and applied rate metrics
> to several HBASE/HDFS/YARN widgets on Summary pages as well as Heatmap
> pages. Rate metrics work fine on Summary pages but they don't work on Heatmap
> pages because current Heatmap design can only show point-in-time metrics and
> rate metrics need a time range.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20028) Operations do not show up in the operations list without a refresh
Denys Buzhor created AMBARI-20028: - Summary: Operations do not show up in the operations list without a refresh Key: AMBARI-20028 URL: https://issues.apache.org/jira/browse/AMBARI-20028 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Denys Buzhor Assignee: Denys Buzhor Priority: Critical Fix For: 2.5.0 Restart attempted from the host page. Ambari asks for a confirmation, shows the operations screen, but doesn't take any action. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20008) Add "Manage alert notifications" authorization
[ https://issues.apache.org/jira/browse/AMBARI-20008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-20008: --- Status: Open (was: Patch Available) > Add "Manage alert notifications" authorization > --- > > Key: AMBARI-20008 > URL: https://issues.apache.org/jira/browse/AMBARI-20008 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 2.5.0 > > Attachments: AMBARI-20008.2.5.patch, AMBARI-20008.trunk.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20025) Incorrect work of filters on Versions page of Admin View
[
https://issues.apache.org/jira/browse/AMBARI-20025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868119#comment-15868119
]
Hadoop QA commented on AMBARI-20025:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852837/AMBARI-20025.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-admin.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10590//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10590//console
This message is automatically generated.
> Incorrect work of filters on Versions page of Admin View
>
>
> Key: AMBARI-20025
> URL: https://issues.apache.org/jira/browse/AMBARI-20025
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-20025.patch, _versions-filter.jpg
>
>
> Filter by cluster name doesn't work (while being enabled, showing versions
> that are not installed on cluster): [^_versions-filter.jpg]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20025) Incorrect work of filters on Versions page of Admin View
[ https://issues.apache.org/jira/browse/AMBARI-20025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-20025: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Incorrect work of filters on Versions page of Admin View > > > Key: AMBARI-20025 > URL: https://issues.apache.org/jira/browse/AMBARI-20025 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-20025.patch, _versions-filter.jpg > > > Filter by cluster name doesn't work (while being enabled, showing versions > that are not installed on cluster): [^_versions-filter.jpg] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20018) Document security issue related to setting security.agent.hostname.validate to false
[
https://issues.apache.org/jira/browse/AMBARI-20018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-20018:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit 45842645c546a176f1692d0d7be008e2d51c5086
Author: Robert Levas
Date: Wed Feb 15 11:20:03 2017 -0500
{noformat}
Committed to branch-2.5
{noformat}
commit 8b5883316f0e1348548e3a2cfcafa0c2a6d21048
Author: Robert Levas
Date: Wed Feb 15 11:21:05 2017 -0500
{noformat}
> Document security issue related to setting security.agent.hostname.validate
> to false
>
>
> Key: AMBARI-20018
> URL: https://issues.apache.org/jira/browse/AMBARI-20018
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
> Fix For: 2.5.0
>
> Attachments: AMBARI-20018_branch-2.5_01.patch,
> AMBARI-20018_branch-2.5_02.patch, AMBARI-20018_trunk_01.patch,
> AMBARI-20018_trunk_02.patch
>
>
> Document security issue related to setting security.agent.hostname.validate
> to "false".
> If set to "false", invalid hostnames may be used in OpenSSL commands used to
> create the agent-side certificates when 2-way SSL is enabled. This could lead
> to issues when executing OpenSSL as described in CVE-2014-3582. See
> https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20027) Override property popup: Redundant scrollbars in config groups list
[ https://issues.apache.org/jira/browse/AMBARI-20027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-20027: -- Status: Patch Available (was: Open) > Override property popup: Redundant scrollbars in config groups list > --- > > Key: AMBARI-20027 > URL: https://issues.apache.org/jira/browse/AMBARI-20027 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-20027.patch > > > *STR* > # Create service config group > # Proceed with overriding any property > # Open existing config groups combobox in displayed popup. > *Result* > Displayed list has redundant horizontal and vertical scrollbars. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20027) Override property popup: Redundant scrollbars in config groups list
[ https://issues.apache.org/jira/browse/AMBARI-20027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-20027: -- Attachment: AMBARI-20027.patch > Override property popup: Redundant scrollbars in config groups list > --- > > Key: AMBARI-20027 > URL: https://issues.apache.org/jira/browse/AMBARI-20027 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-20027.patch > > > *STR* > # Create service config group > # Proceed with overriding any property > # Open existing config groups combobox in displayed popup. > *Result* > Displayed list has redundant horizontal and vertical scrollbars. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20027) Override property popup: Redundant scrollbars in config groups list
Andrii Babiichuk created AMBARI-20027: - Summary: Override property popup: Redundant scrollbars in config groups list Key: AMBARI-20027 URL: https://issues.apache.org/jira/browse/AMBARI-20027 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 3.0.0 *STR* # Create service config group # Proceed with overriding any property # Open existing config groups combobox in displayed popup. *Result* Displayed list has redundant horizontal and vertical scrollbars. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20024) Relax ranger config DB consistency check rules
[
https://issues.apache.org/jira/browse/AMBARI-20024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868080#comment-15868080
]
Hadoop QA commented on AMBARI-20024:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12852832/AMBARI-20024.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/10589//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10589//console
This message is automatically generated.
> Relax ranger config DB consistency check rules
> --
>
> Key: AMBARI-20024
> URL: https://issues.apache.org/jira/browse/AMBARI-20024
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-20024.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20016) Hosts page moving through pages gets progressively slower to the point of being unusable
[ https://issues.apache.org/jira/browse/AMBARI-20016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868040#comment-15868040 ] Hudson commented on AMBARI-20016: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1004 (See [https://builds.apache.org/job/Ambari-branch-2.5/1004/]) AMBARI-20016 Hosts page moving through pages gets progressively slower (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cb59ebdf7596ce2fb7d073ba98b8f8fe7b3ffdb5]) * (edit) ambari-web/app/mappers/widget_mapper.js * (edit) ambari-web/app/controllers/main/service/add_controller.js * (edit) ambari-web/app/mappers/alert_groups_mapper.js * (edit) ambari-web/app/mixins/main/service/groups_mapping.js * (edit) ambari-web/app/mappers/service_mapper.js * (edit) ambari-web/test/controllers/main/service/add_controller_test.js * (edit) ambari-web/test/models/rack_test.js * (edit) ambari-web/app/controllers/wizard/step7_controller.js * (edit) ambari-web/app/mappers/alert_definition_summary_mapper.js * (edit) ambari-web/test/mappers/alert_groups_mapper_test.js * (edit) ambari-web/test/controllers/main/admin_test.js * (edit) ambari-web/app/mappers/alert_definitions_mapper.js * (edit) ambari-web/app/mappers/quicklinks_mapper.js * (edit) ambari-web/app/utils/http_client.js * (edit) ambari-web/test/models/host_component_test.js * (edit) ambari-web/app/mappers/stack_upgrade_history_mapper.js * (edit) ambari-web/app/mappers/root_service_mapper.js * (edit) ambari-web/test/utils/http_client_test.js * (edit) ambari-web/test/controllers/main/host/details_test.js * (edit) ambari-web/app/mappers/configs/themes_mapper.js * (edit) ambari-web/app/controllers/main.js * (edit) ambari-web/app/mappers/service_metrics_mapper.js * (edit) ambari-web/app/mappers/stack_mapper.js * (edit) ambari-web/app/mappers/configs/service_config_version_mapper.js * (edit) ambari-web/app/mappers/configs/config_groups_mapper.js * (edit) ambari-web/app/mappers/stack_service_mapper.js * (edit) ambari-web/app/controllers/main/service/manage_config_groups_controller.js * (edit) ambari-web/app/mappers/target_cluster_mapper.js * (edit) ambari-web/app/mappers/alert_notification_mapper.js * (edit) ambari-web/app/mappers/stack_version_mapper.js * (edit) ambari-web/app/mixins/main/service/configs/config_overridable.js * (edit) ambari-web/app/mappers/users_mapper.js * (edit) ambari-web/test/models/stack_service_test.js * (edit) ambari-web/app/mappers/hosts_mapper.js * (edit) ambari-web/test/models/host_stack_version_test.js * (edit) ambari-web/app/mappers/server_data_mapper.js * (edit) ambari-web/test/controllers/main/service/item_test.js * (edit) ambari-web/app/mappers/alert_instances_mapper.js * (edit) ambari-web/app/mappers/components_state_mapper.js * (edit) ambari-web/app/mappers/repository_version_mapper.js * (edit) ambari-web/app/models/user.js * (edit) ambari-web/app/mappers/cluster_mapper.js > Hosts page moving through pages gets progressively slower to the point of > being unusable > > > Key: AMBARI-20016 > URL: https://issues.apache.org/jira/browse/AMBARI-20016 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20016_branch-2.5.patch, AMBARI-20016.patch > > > STR: > * On a 1000-node cluster, go to Hosts page > * Set the page size to 100 (shows hosts 1-100) > * Using the paging controls, go to the next page (shows hosts 101-200) - this > takes several seconds > * Using the paging controls, go to the next page (shows hosts 201-300) - this > takes longer > * Repeat showing the next set of hosts. This gets progressively slower. I > gave up when I hit 701-800 since the page got totally stuck after waiting for > 3 minutes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20026) Ambari server start returns prematurely before extracting views.
[ https://issues.apache.org/jira/browse/AMBARI-20026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-20026: Status: Patch Available (was: Open) > Ambari server start returns prematurely before extracting views. > > > Key: AMBARI-20026 > URL: https://issues.apache.org/jira/browse/AMBARI-20026 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen > Fix For: 2.5.0 > > Attachments: AMBARI-20026.patch > > > When ambari-server start is issued, It returns prematurely before the view > extraction is complete. > because of this we have introduced sleep of 3mins before ambari-server stop > for the view extraction to complete. > Ambari server should report start completed only after view extraction is > completed -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20026) Ambari server start returns prematurely before extracting views.
[ https://issues.apache.org/jira/browse/AMBARI-20026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-20026: Attachment: AMBARI-20026.patch > Ambari server start returns prematurely before extracting views. > > > Key: AMBARI-20026 > URL: https://issues.apache.org/jira/browse/AMBARI-20026 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen > Fix For: 2.5.0 > > Attachments: AMBARI-20026.patch > > > When ambari-server start is issued, It returns prematurely before the view > extraction is complete. > because of this we have introduced sleep of 3mins before ambari-server stop > for the view extraction to complete. > Ambari server should report start completed only after view extraction is > completed -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20025) Incorrect work of filters on Versions page of Admin View
[ https://issues.apache.org/jira/browse/AMBARI-20025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-20025: -- Status: Patch Available (was: Open) > Incorrect work of filters on Versions page of Admin View > > > Key: AMBARI-20025 > URL: https://issues.apache.org/jira/browse/AMBARI-20025 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-20025.patch, _versions-filter.jpg > > > Filter by cluster name doesn't work (while being enabled, showing versions > that are not installed on cluster): [^_versions-filter.jpg] -- This message was sent by Atlassian JIRA (v6.3.15#6346)
