[jira] [Resolved] (AMBARI-22770) Bring jenkins job build script under version control
[ https://issues.apache.org/jira/browse/AMBARI-22770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved AMBARI-22770. - Resolution: Won't Fix > Bring jenkins job build script under version control > > > Key: AMBARI-22770 > URL: https://issues.apache.org/jira/browse/AMBARI-22770 > Project: Ambari > Issue Type: Task >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMBARI-18511) Grafana dashboard shows "Cannot read property 'lastIndexOf' of undefined"
[
https://issues.apache.org/jira/browse/AMBARI-18511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian resolved AMBARI-18511.
-
Resolution: Invalid
Closing this due to no activity for a long time.
> Grafana dashboard shows "Cannot read property 'lastIndexOf' of undefined"
> -
>
> Key: AMBARI-18511
> URL: https://issues.apache.org/jira/browse/AMBARI-18511
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.4.1
> Environment: All
>Reporter: Jay SenSharma
>Assignee: Vivek Ratnavel Subramanian
>Priority: Major
> Attachments: Grafana_Error.png, Grafana_Error_After_Login.png
>
>
> - After upgrading ambari from 2.4.0.1 to ambari 2.4.1.0 it shows the
> following error while accessing the Grafana WebUI:
> {code}
> Message:
> Cannot read property 'lastIndexOf' of undefined
>
> Stack trace:
> TypeError: Cannot read property 'lastIndexOf' of
> undefined
> at AmbariMetricsDatasource.query
> (http://hdp25b:3000/public/app/plugins/datasource/ambari-metrics/datasource.js?bust=1475491283316:423:55)
> at issueMetricQuery
> (http://hdp25b:3000/public/app/app.ca0ab6f9.js:42:14189)
> at n.a.refreshData
> (http://hdp25b:3000/public/app/app.ca0ab6f9.js:48:18026)
> at http://hdp25b:3000/public/app/app.ca0ab6f9.js:42:11552
> at i (http://hdp25b:3000/public/app/app.ca0ab6f9.js:13:5845)
> at http://hdp25b:3000/public/app/app.ca0ab6f9.js:13:6017
> at n.$eval (http://hdp25b:3000/public/app/app.ca0ab6f9.js:13:13637)
> at n.$digest (http://hdp25b:3000/public/app/app.ca0ab6f9.js:13:12068)
> at n.$apply (http://hdp25b:3000/public/app/app.ca0ab6f9.js:13:13904)
> at http://hdp25b:3000/public/app/app.ca0ab6f9.js:13:21240
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (AMBARI-12542) Enabling full screen for ambari views iframe
[ https://issues.apache.org/jira/browse/AMBARI-12542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-12542: Resolution: Fixed Status: Resolved (was: Patch Available) > Enabling full screen for ambari views iframe > - > > Key: AMBARI-12542 > URL: https://issues.apache.org/jira/browse/AMBARI-12542 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.1.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Major > Fix For: 2.3.0 > > Attachments: AMBARI-12542.patch > > > The "allowfullscreen" attribute of iframe needs to be set to "true" for the > components in the iframe to toggle full screen. The "iframe" tag used in > ambari-web to display different views does not have this attribute enabled. > This is required for the visualization component of hive views to toggle full > screen. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (AMBARI-22770) Bring jenkins job build script under version control
[
https://issues.apache.org/jira/browse/AMBARI-22770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324882#comment-16324882
]
Vivek Ratnavel Subramanian commented on AMBARI-22770:
-
I think the rat check includes files under "node_modules" and reports very high
number of files.
It should be
{code:java}
[INFO] 2931 resources included (use -debug for more details)
{code}
But when we curl build-ambari.sh and use it, we get the following
{code:java}
[INFO] 6113 resources included (use -debug for more details)
{code}
Check build 88 for comparison -
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/88/console
> Bring jenkins job build script under version control
>
>
> Key: AMBARI-22770
> URL: https://issues.apache.org/jira/browse/AMBARI-22770
> Project: Ambari
> Issue Type: Task
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22770) Bring jenkins job build script under version control
[ https://issues.apache.org/jira/browse/AMBARI-22770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324874#comment-16324874 ] Vivek Ratnavel Subramanian commented on AMBARI-22770: - I have reverted the use of script. It produces rat error on too many files. https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/86/console We need to debug why this happens. Build 86 and all the builds that ran before it failed with rat check errors. Until, then I have replaced the jenkins script to use the whole script instead of ambari-build.sh. > Bring jenkins job build script under version control > > > Key: AMBARI-22770 > URL: https://issues.apache.org/jira/browse/AMBARI-22770 > Project: Ambari > Issue Type: Task >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22770) Bring jenkins job build script under version control
[ https://issues.apache.org/jira/browse/AMBARI-22770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324734#comment-16324734 ] Vivek Ratnavel Subramanian commented on AMBARI-22770: - [~adoroszlai] I have used the script you suggested. And the builds have started triggering. Thanks [~adoroszlai]! > Bring jenkins job build script under version control > > > Key: AMBARI-22770 > URL: https://issues.apache.org/jira/browse/AMBARI-22770 > Project: Ambari > Issue Type: Task >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22770) Bring jenkins job build script under version control
[ https://issues.apache.org/jira/browse/AMBARI-22770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324594#comment-16324594 ] Vivek Ratnavel Subramanian commented on AMBARI-22770: - That sounds like a good idea. Let me try that in some time. Thanks [~adoroszlai]! > Bring jenkins job build script under version control > > > Key: AMBARI-22770 > URL: https://issues.apache.org/jira/browse/AMBARI-22770 > Project: Ambari > Issue Type: Task >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22770) Bring jenkins job build script under version control
[
https://issues.apache.org/jira/browse/AMBARI-22770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324564#comment-16324564
]
Vivek Ratnavel Subramanian commented on AMBARI-22770:
-
I got the error above while trying with the following shell script in the
jenkins job:
{code:java}
cd dev-support/
./build-ambari.sh
{code}
I am thinking of doing a git clone of the repo to get a copy of latest trunk
and then following running the 'build-ambari.sh'. But, I do not know if
creating a new clone folder inside the workspace will cause the build to fail.
I don't know which other path we can safely use to clone the repo to trigger
the build. Any thoughts on this?
[~adoroszlai] [~u39kun]
> Bring jenkins job build script under version control
>
>
> Key: AMBARI-22770
> URL: https://issues.apache.org/jira/browse/AMBARI-22770
> Project: Ambari
> Issue Type: Task
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22770) Bring jenkins job build script under version control
[
https://issues.apache.org/jira/browse/AMBARI-22770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16324559#comment-16324559
]
Vivek Ratnavel Subramanian commented on AMBARI-22770:
-
The patch is now committed to trunk. But there is an issue we need to address.
The Ambari-Github-PullRequest-Builder
(https://builds.apache.org/view/A/view/Ambari/job/Ambari-Github-PullRequest-Builder/ws/dev-support/)
is capable of building a PR against any branch and this results in the
following exception while trying to build other branches.
{code:java}
/tmp/jenkins2838946866965171719.sh: line 4: ./build-ambari.sh: No such file or
directory
{code}
Here is the complete log -
https://builds.apache.org/view/A/view/Ambari/job/Ambari-Github-PullRequest-Builder/67/consoleText
> Bring jenkins job build script under version control
>
>
> Key: AMBARI-22770
> URL: https://issues.apache.org/jira/browse/AMBARI-22770
> Project: Ambari
> Issue Type: Task
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22770) Bring jenkins job build script under version control
Vivek Ratnavel Subramanian created AMBARI-22770: --- Summary: Bring jenkins job build script under version control Key: AMBARI-22770 URL: https://issues.apache.org/jira/browse/AMBARI-22770 Project: Ambari Issue Type: Task Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22749) Create Pull Request Template
[ https://issues.apache.org/jira/browse/AMBARI-22749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved AMBARI-22749. - Resolution: Fixed > Create Pull Request Template > > > Key: AMBARI-22749 > URL: https://issues.apache.org/jira/browse/AMBARI-22749 > Project: Ambari > Issue Type: Task >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > > Create a pull request template for github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22749) Create Pull Request Template
Vivek Ratnavel Subramanian created AMBARI-22749: --- Summary: Create Pull Request Template Key: AMBARI-22749 URL: https://issues.apache.org/jira/browse/AMBARI-22749 Project: Ambari Issue Type: Task Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Create a pull request template for github. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22646) hive.metastore.transactional.event.listeners is present during UI deploys and is empty
Vivek Ratnavel Subramanian created AMBARI-22646: --- Summary: hive.metastore.transactional.event.listeners is present during UI deploys and is empty Key: AMBARI-22646 URL: https://issues.apache.org/jira/browse/AMBARI-22646 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.6.1 Reporter: Vivek Ratnavel Subramanian Assignee: Jaimin Jetly Fix For: 3.0.0 Config added with empty value: hive.metastore.transactional.event.listeners hive.metastore.dml.events -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (AMBARI-22566) Upgrade Angular for Ambari Admin View
[ https://issues.apache.org/jira/browse/AMBARI-22566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian reopened AMBARI-22566: - Angular upgrade breaks all translations with variable assignment. Reverting the patch to fix the issue. > Upgrade Angular for Ambari Admin View > - > > Key: AMBARI-22566 > URL: https://issues.apache.org/jira/browse/AMBARI-22566 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22566.patch, AMBARI-22566_trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (AMBARI-22572) During cluster installation bower cannot resolve angularjs version
[ https://issues.apache.org/jira/browse/AMBARI-22572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian reopened AMBARI-22572: - Angular upgrade breaks all translations with variable assignment. Reverting the patch to fix the issue. > During cluster installation bower cannot resolve angularjs version > -- > > Key: AMBARI-22572 > URL: https://issues.apache.org/jira/browse/AMBARI-22572 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.6.1 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22572.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22445) Warn the user appropriately for default MySQL server install for Hive
[ https://issues.apache.org/jira/browse/AMBARI-22445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22445: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch 2.6 and trunk > Warn the user appropriately for default MySQL server install for Hive > - > > Key: AMBARI-22445 > URL: https://issues.apache.org/jira/browse/AMBARI-22445 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22445.v0.branch-2.6.patch, > AMBARI-22445.v2.branch-2.6.patch, AMBARI-22445.v2.trunk.patch > > > The mysql connector license is not compatible with Ambari's license and > Ambari no longer auto installs mysql-connector after AMBARI-22369. Warn the > user appropriately to install and setup mysql-connector to be used by Hive. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22445) Warn the user appropriately for default MySQL server install for Hive
[ https://issues.apache.org/jira/browse/AMBARI-22445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22445: Status: Patch Available (was: In Progress) > Warn the user appropriately for default MySQL server install for Hive > - > > Key: AMBARI-22445 > URL: https://issues.apache.org/jira/browse/AMBARI-22445 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22445.v0.branch-2.6.patch, > AMBARI-22445.v2.branch-2.6.patch, AMBARI-22445.v2.trunk.patch > > > The mysql connector license is not compatible with Ambari's license and > Ambari no longer auto installs mysql-connector after AMBARI-22369. Warn the > user appropriately to install and setup mysql-connector to be used by Hive. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22445) Warn the user appropriately for default MySQL server install for Hive
[ https://issues.apache.org/jira/browse/AMBARI-22445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22445: Attachment: AMBARI-22445.v2.trunk.patch > Warn the user appropriately for default MySQL server install for Hive > - > > Key: AMBARI-22445 > URL: https://issues.apache.org/jira/browse/AMBARI-22445 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22445.v0.branch-2.6.patch, > AMBARI-22445.v2.branch-2.6.patch, AMBARI-22445.v2.trunk.patch > > > The mysql connector license is not compatible with Ambari's license and > Ambari no longer auto installs mysql-connector after AMBARI-22369. Warn the > user appropriately to install and setup mysql-connector to be used by Hive. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22445) Warn the user appropriately for default MySQL server install for Hive
[ https://issues.apache.org/jira/browse/AMBARI-22445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22445: Attachment: AMBARI-22445.v2.branch-2.6.patch > Warn the user appropriately for default MySQL server install for Hive > - > > Key: AMBARI-22445 > URL: https://issues.apache.org/jira/browse/AMBARI-22445 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22445.v0.branch-2.6.patch, > AMBARI-22445.v2.branch-2.6.patch > > > The mysql connector license is not compatible with Ambari's license and > Ambari no longer auto installs mysql-connector after AMBARI-22369. Warn the > user appropriately to install and setup mysql-connector to be used by Hive. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22570) Repository Fields missing when register version is clicked
[ https://issues.apache.org/jira/browse/AMBARI-22570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22570: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.6 and trunk > Repository Fields missing when register version is clicked > -- > > Key: AMBARI-22570 > URL: https://issues.apache.org/jira/browse/AMBARI-22570 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.6.1 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22570.v0.branch-2.6.patch, > AMBARI-22570.v0.trunk.patch > > > Repository fields are missing when trying to register new version by clicking > "+ Register Version" button in Manage Versions page. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22570) Repository Fields missing when register version is clicked
[ https://issues.apache.org/jira/browse/AMBARI-22570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22570: Status: Patch Available (was: In Progress) > Repository Fields missing when register version is clicked > -- > > Key: AMBARI-22570 > URL: https://issues.apache.org/jira/browse/AMBARI-22570 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.6.1 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22570.v0.branch-2.6.patch, > AMBARI-22570.v0.trunk.patch > > > Repository fields are missing when trying to register new version by clicking > "+ Register Version" button in Manage Versions page. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22570) Repository Fields missing when register version is clicked
[ https://issues.apache.org/jira/browse/AMBARI-22570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22570: Attachment: AMBARI-22570.v0.trunk.patch > Repository Fields missing when register version is clicked > -- > > Key: AMBARI-22570 > URL: https://issues.apache.org/jira/browse/AMBARI-22570 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.6.1 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22570.v0.branch-2.6.patch, > AMBARI-22570.v0.trunk.patch > > > Repository fields are missing when trying to register new version by clicking > "+ Register Version" button in Manage Versions page. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22570) Repository Fields missing when register version is clicked
[ https://issues.apache.org/jira/browse/AMBARI-22570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22570: Attachment: AMBARI-22570.v0.branch-2.6.patch > Repository Fields missing when register version is clicked > -- > > Key: AMBARI-22570 > URL: https://issues.apache.org/jira/browse/AMBARI-22570 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.6.1 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22570.v0.branch-2.6.patch, > AMBARI-22570.v0.trunk.patch > > > Repository fields are missing when trying to register new version by clicking > "+ Register Version" button in Manage Versions page. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22570) Repository Fields missing when register version is clicked
Vivek Ratnavel Subramanian created AMBARI-22570: --- Summary: Repository Fields missing when register version is clicked Key: AMBARI-22570 URL: https://issues.apache.org/jira/browse/AMBARI-22570 Project: Ambari Issue Type: Bug Components: ambari-admin Affects Versions: 2.6.1 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Priority: Blocker Fix For: 2.6.1 Repository fields are missing when trying to register new version by clicking "+ Register Version" button in Manage Versions page. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22554) UI should pass repo_name for repository validation
[
https://issues.apache.org/jira/browse/AMBARI-22554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian updated AMBARI-22554:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to
branch-2.6 - 128c7fb5fde0afac80d3f4eb1e8884f1700dd64f
trunk - ca174fb32a0e34582776b0607b6a2d14dc72c20d
> UI should pass repo_name for repository validation
> --
>
> Key: AMBARI-22554
> URL: https://issues.apache.org/jira/browse/AMBARI-22554
> Project: Ambari
> Issue Type: Task
> Components: ambari-admin, ambari-web
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.6.1
>
> Attachments: AMBARI-22554.v0.branch-2.6.patch,
> AMBARI-22554.v0.trunk.patch
>
>
> UI should pass Repositories/repo_name property as part of validation request
> to API
> {code:java}
> /stacks/{stackName}/versions/{stackVersion}/operating_systems/{osType}/repositories/{repoId}
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22554) UI should pass repo_name for repository validation
[
https://issues.apache.org/jira/browse/AMBARI-22554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian updated AMBARI-22554:
Status: Patch Available (was: Open)
> UI should pass repo_name for repository validation
> --
>
> Key: AMBARI-22554
> URL: https://issues.apache.org/jira/browse/AMBARI-22554
> Project: Ambari
> Issue Type: Task
> Components: ambari-admin, ambari-web
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.6.1
>
> Attachments: AMBARI-22554.v0.branch-2.6.patch,
> AMBARI-22554.v0.trunk.patch
>
>
> UI should pass Repositories/repo_name property as part of validation request
> to API
> {code:java}
> /stacks/{stackName}/versions/{stackVersion}/operating_systems/{osType}/repositories/{repoId}
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22554) UI should pass repo_name for repository validation
[
https://issues.apache.org/jira/browse/AMBARI-22554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian updated AMBARI-22554:
Attachment: AMBARI-22554.v0.trunk.patch
> UI should pass repo_name for repository validation
> --
>
> Key: AMBARI-22554
> URL: https://issues.apache.org/jira/browse/AMBARI-22554
> Project: Ambari
> Issue Type: Task
> Components: ambari-admin, ambari-web
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.6.1
>
> Attachments: AMBARI-22554.v0.branch-2.6.patch,
> AMBARI-22554.v0.trunk.patch
>
>
> UI should pass Repositories/repo_name property as part of validation request
> to API
> {code:java}
> /stacks/{stackName}/versions/{stackVersion}/operating_systems/{osType}/repositories/{repoId}
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22554) UI should pass repo_name for repository validation
[
https://issues.apache.org/jira/browse/AMBARI-22554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian updated AMBARI-22554:
Attachment: AMBARI-22554.v0.branch-2.6.patch
> UI should pass repo_name for repository validation
> --
>
> Key: AMBARI-22554
> URL: https://issues.apache.org/jira/browse/AMBARI-22554
> Project: Ambari
> Issue Type: Task
> Components: ambari-admin, ambari-web
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 2.6.1
>
> Attachments: AMBARI-22554.v0.branch-2.6.patch
>
>
> UI should pass Repositories/repo_name property as part of validation request
> to API
> {code:java}
> /stacks/{stackName}/versions/{stackVersion}/operating_systems/{osType}/repositories/{repoId}
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22554) UI should pass repo_name for repository validation
Vivek Ratnavel Subramanian created AMBARI-22554:
---
Summary: UI should pass repo_name for repository validation
Key: AMBARI-22554
URL: https://issues.apache.org/jira/browse/AMBARI-22554
Project: Ambari
Issue Type: Task
Components: ambari-admin, ambari-web
Reporter: Vivek Ratnavel Subramanian
Assignee: Vivek Ratnavel Subramanian
Fix For: 2.6.1
UI should pass Repositories/repo_name property as part of validation request to
API
{code:java}
/stacks/{stackName}/versions/{stackVersion}/operating_systems/{osType}/repositories/{repoId}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22495) Installer - Select Version page should show HDP-GPL repo if necessary
[ https://issues.apache.org/jira/browse/AMBARI-22495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22495: Attachment: AMBARI-22495.v1.trunk.patch > Installer - Select Version page should show HDP-GPL repo if necessary > - > > Key: AMBARI-22495 > URL: https://issues.apache.org/jira/browse/AMBARI-22495 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.6.1 > > Attachments: AMBARI-22495.v0.br-feature.patch, > AMBARI-22495.v1.br-feature.patch, AMBARI-22495.v1.trunk.patch > > > Display HDP-GPL repo field under Repositories in Select Version step of > Installer only if user agrees to gpl license agreement -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22495) Installer - Select Version page should show HDP-GPL repo if necessary
[ https://issues.apache.org/jira/browse/AMBARI-22495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22495: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk - 6b17d0142266f714807bd06e3ce1afbe535a0a73 branch-feature-AMBARI-22457 - 8541829876ae3edcfbe96587270ecedad86f36e8 > Installer - Select Version page should show HDP-GPL repo if necessary > - > > Key: AMBARI-22495 > URL: https://issues.apache.org/jira/browse/AMBARI-22495 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.6.1 > > Attachments: AMBARI-22495.v0.br-feature.patch, > AMBARI-22495.v1.br-feature.patch > > > Display HDP-GPL repo field under Repositories in Select Version step of > Installer only if user agrees to gpl license agreement -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22496) Admin View - Manage Versions page should show HDP-GPL repo if necessary
[ https://issues.apache.org/jira/browse/AMBARI-22496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22496: Attachment: AMBARI-22496.v1.br-feature.patch AMBARI-22496.v1.trunk.patch > Admin View - Manage Versions page should show HDP-GPL repo if necessary > --- > > Key: AMBARI-22496 > URL: https://issues.apache.org/jira/browse/AMBARI-22496 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.6.1 > > Attachments: AMBARI-22496.v0.br-feature.patch, > AMBARI-22496.v1.br-feature.patch, AMBARI-22496.v1.trunk.patch > > > Display HDP-GPL repo field under Repositories in Manage Versions of Admin > View only if the user agreed to the GPL license agreement during > ambari-server setup -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22496) Admin View - Manage Versions page should show HDP-GPL repo if necessary
[ https://issues.apache.org/jira/browse/AMBARI-22496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22496: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk - 9fc7223df9a50fe69f4d8884939718b3f3bcf31b branch-feature-AMBARI-22457 - 059fadf460f2fc59ecb60403141c8b36a4c89668 > Admin View - Manage Versions page should show HDP-GPL repo if necessary > --- > > Key: AMBARI-22496 > URL: https://issues.apache.org/jira/browse/AMBARI-22496 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.6.1 > > Attachments: AMBARI-22496.v0.br-feature.patch, > AMBARI-22496.v1.br-feature.patch, AMBARI-22496.v1.trunk.patch > > > Display HDP-GPL repo field under Repositories in Manage Versions of Admin > View only if the user agreed to the GPL license agreement during > ambari-server setup -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22496) Admin View - Manage Versions page should show HDP-GPL repo if necessary
[ https://issues.apache.org/jira/browse/AMBARI-22496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22496: Component/s: (was: ambari-web) ambari-admin > Admin View - Manage Versions page should show HDP-GPL repo if necessary > --- > > Key: AMBARI-22496 > URL: https://issues.apache.org/jira/browse/AMBARI-22496 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.6.1 > > Attachments: AMBARI-22496.v0.br-feature.patch > > > Display HDP-GPL repo field under Repositories in Manage Versions of Admin > View only if the user agreed to the GPL license agreement during > ambari-server setup -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22496) Admin View - Manage Versions page should show HDP-GPL repo if necessary
[ https://issues.apache.org/jira/browse/AMBARI-22496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22496: Attachment: AMBARI-22496.v0.br-feature.patch > Admin View - Manage Versions page should show HDP-GPL repo if necessary > --- > > Key: AMBARI-22496 > URL: https://issues.apache.org/jira/browse/AMBARI-22496 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.6.1 > > Attachments: AMBARI-22496.v0.br-feature.patch > > > Display HDP-GPL repo field under Repositories in Manage Versions of Admin > View only if the user agreed to the GPL license agreement during > ambari-server setup -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22496) Admin View - Manage Versions page should show HDP-GPL repo if necessary
[ https://issues.apache.org/jira/browse/AMBARI-22496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22496: Status: Patch Available (was: In Progress) > Admin View - Manage Versions page should show HDP-GPL repo if necessary > --- > > Key: AMBARI-22496 > URL: https://issues.apache.org/jira/browse/AMBARI-22496 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.6.1 > > Attachments: AMBARI-22496.v0.br-feature.patch > > > Display HDP-GPL repo field under Repositories in Manage Versions of Admin > View only if the user agreed to the GPL license agreement during > ambari-server setup -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22495) Installer - Select Version page should show HDP-GPL repo if necessary
[ https://issues.apache.org/jira/browse/AMBARI-22495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22495: Attachment: AMBARI-22495.v1.br-feature.patch > Installer - Select Version page should show HDP-GPL repo if necessary > - > > Key: AMBARI-22495 > URL: https://issues.apache.org/jira/browse/AMBARI-22495 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.6.1 > > Attachments: AMBARI-22495.v0.br-feature.patch, > AMBARI-22495.v1.br-feature.patch > > > Display HDP-GPL repo field under Repositories in Select Version step of > Installer only if user agrees to gpl license agreement -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22495) Installer - Select Version page should show HDP-GPL repo if necessary
[ https://issues.apache.org/jira/browse/AMBARI-22495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22495: Status: Patch Available (was: In Progress) > Installer - Select Version page should show HDP-GPL repo if necessary > - > > Key: AMBARI-22495 > URL: https://issues.apache.org/jira/browse/AMBARI-22495 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.6.1 > > Attachments: AMBARI-22495.v0.br-feature.patch > > > Display HDP-GPL repo field under Repositories in Select Version step of > Installer only if user agrees to gpl license agreement -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22495) Installer - Select Version page should show HDP-GPL repo if necessary
[ https://issues.apache.org/jira/browse/AMBARI-22495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22495: Attachment: AMBARI-22495.v0.br-feature.patch > Installer - Select Version page should show HDP-GPL repo if necessary > - > > Key: AMBARI-22495 > URL: https://issues.apache.org/jira/browse/AMBARI-22495 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.6.1 > > Attachments: AMBARI-22495.v0.br-feature.patch > > > Display HDP-GPL repo field under Repositories in Select Version step of > Installer only if user agrees to gpl license agreement -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22495) Installer - Select Version page should show HDP-GPL repo if necessary
Vivek Ratnavel Subramanian created AMBARI-22495: --- Summary: Installer - Select Version page should show HDP-GPL repo if necessary Key: AMBARI-22495 URL: https://issues.apache.org/jira/browse/AMBARI-22495 Project: Ambari Issue Type: Task Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 2.6.1 Display HDP-GPL repo field under Repositories in Select Version step of Installer only if user agrees to gpl license agreement -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22495) Installer - Select Version page should show HDP-GPL repo if necessary
[ https://issues.apache.org/jira/browse/AMBARI-22495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22495: Component/s: ambari-web > Installer - Select Version page should show HDP-GPL repo if necessary > - > > Key: AMBARI-22495 > URL: https://issues.apache.org/jira/browse/AMBARI-22495 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.6.1 > > > Display HDP-GPL repo field under Repositories in Select Version step of > Installer only if user agrees to gpl license agreement -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22445) Warn the user appropriately for default MySQL server install for Hive
[ https://issues.apache.org/jira/browse/AMBARI-22445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22445: Resolution: Fixed Status: Resolved (was: Patch Available) > Warn the user appropriately for default MySQL server install for Hive > - > > Key: AMBARI-22445 > URL: https://issues.apache.org/jira/browse/AMBARI-22445 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22445.v0.branch-2.6.patch > > > The mysql connector license is not compatible with Ambari's license and > Ambari no longer auto installs mysql-connector after AMBARI-22369. Warn the > user appropriately to install and setup mysql-connector to be used by Hive. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22445) Warn the user appropriately for default MySQL server install for Hive
[ https://issues.apache.org/jira/browse/AMBARI-22445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254344#comment-16254344 ] Vivek Ratnavel Subramanian commented on AMBARI-22445: - Patch committed to: branch-2.6 - 822fe2d5aa02c6d7f1fafdf74b5c0e23cf657bbc trunk - 8fe6ac4bd03739202a35f8862270be7dcec95421 > Warn the user appropriately for default MySQL server install for Hive > - > > Key: AMBARI-22445 > URL: https://issues.apache.org/jira/browse/AMBARI-22445 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22445.v0.branch-2.6.patch > > > The mysql connector license is not compatible with Ambari's license and > Ambari no longer auto installs mysql-connector after AMBARI-22369. Warn the > user appropriately to install and setup mysql-connector to be used by Hive. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22445) Warn the user appropriately for default MySQL server install for Hive
[ https://issues.apache.org/jira/browse/AMBARI-22445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22445: Attachment: AMBARI-22445.v0.branch-2.6.patch > Warn the user appropriately for default MySQL server install for Hive > - > > Key: AMBARI-22445 > URL: https://issues.apache.org/jira/browse/AMBARI-22445 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22445.v0.branch-2.6.patch > > > The mysql connector license is not compatible with Ambari's license and > Ambari no longer auto installs mysql-connector after AMBARI-22369. Warn the > user appropriately to install and setup mysql-connector to be used by Hive. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22445) Warn the user appropriately for default MySQL server install for Hive
[ https://issues.apache.org/jira/browse/AMBARI-22445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-22445: Status: Patch Available (was: In Progress) > Warn the user appropriately for default MySQL server install for Hive > - > > Key: AMBARI-22445 > URL: https://issues.apache.org/jira/browse/AMBARI-22445 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22445.v0.branch-2.6.patch > > > The mysql connector license is not compatible with Ambari's license and > Ambari no longer auto installs mysql-connector after AMBARI-22369. Warn the > user appropriately to install and setup mysql-connector to be used by Hive. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22445) Warn the user appropriately for default MySQL server install for Hive
Vivek Ratnavel Subramanian created AMBARI-22445: --- Summary: Warn the user appropriately for default MySQL server install for Hive Key: AMBARI-22445 URL: https://issues.apache.org/jira/browse/AMBARI-22445 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Priority: Blocker Fix For: 2.6.1 The mysql connector license is not compatible with Ambari's license and Ambari no longer auto installs mysql-connector after AMBARI-22369. Warn the user appropriately to install and setup mysql-connector to be used by Hive. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21877) Spark Service check failure in Ambari with kerberos enabled
[ https://issues.apache.org/jira/browse/AMBARI-21877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16154086#comment-16154086 ] Vivek Ratnavel Subramanian commented on AMBARI-21877: - The patch only fixes the issue in SPARK2 service check. The same param needs to be added to SPARK1 as well - https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/SPARK/1.2.1/package/scripts/service_check.py > Spark Service check failure in Ambari with kerberos enabled > --- > > Key: AMBARI-21877 > URL: https://issues.apache.org/jira/browse/AMBARI-21877 > Project: Ambari > Issue Type: Bug >Reporter: Mingjie Tang >Assignee: Mingjie Tang > Attachments: AMBARI-21877.patch > > > Spark service_check.py file is missing user parameter in curl execution calls > which result in service check failures in Kerberized environments. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21290) Grafana Yarn Queue dashboard is not working.
[
https://issues.apache.org/jira/browse/AMBARI-21290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian updated AMBARI-21290:
Resolution: Fixed
Fix Version/s: 2.5.2
Status: Resolved (was: Patch Available)
Patch committed to branch-2.5 and trunk.
- branch-2.5: 4cbd9d7d012458cd742a189e76b89fca58781a8d
- trunk: 845eb86c24a5b4a7d4735d50715522bd8795eff4
> Grafana Yarn Queue dashboard is not working.
>
>
> Key: AMBARI-21290
> URL: https://issues.apache.org/jira/browse/AMBARI-21290
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: trunk, 2.5.1
>Reporter: JaySenSharma
>Assignee: JaySenSharma
> Fix For: 2.5.2
>
> Attachments: AMBARI-21290.patch, Grafana_Yarn_Queue_Error.png,
> startTime_ NaNundefined.png
>
>
> - On Amabri 2.5.1 when we access the "Yarn Queue"
> (http://$GRAFANA_HOST:3000/dashboard/db/yarn-queues) dashboard then we see
> that the Dashboard shows the error. This is because the URL to fetch the
> data has incorrect "*startTime*"
> .
> *Example:*
> {code:java}
> http://amb25101:3000/api/datasources/proxy/1/ws/v1/timeline/metrics?metricNames=yarn.QueueMetrics.Queue=root.AppsRunning._max=resourcemanager=NaNundefined1498007593=1498029193
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-20548) Grafana dashboard changes for some new llap daemon metrics
[ https://issues.apache.org/jira/browse/AMBARI-20548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957935#comment-15957935 ] Vivek Ratnavel Subramanian commented on AMBARI-20548: - Committed to trunk and branch-2.5 - 5d9d73248fb6cf1906372fa0a2c74530c29b67d9 > Grafana dashboard changes for some new llap daemon metrics > -- > > Key: AMBARI-20548 > URL: https://issues.apache.org/jira/browse/AMBARI-20548 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20548.v0.patch, AMBARI-20548.v1.patch > > > Few new metrics (Offheap memory metrics) got added to llap recently which > will be critical for debugging. Also some old metrics in dashboard are not > really useful which can be removed (Llap IO Metrics). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20548) Grafana dashboard changes for some new llap daemon metrics
[ https://issues.apache.org/jira/browse/AMBARI-20548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-20548: Resolution: Fixed Status: Resolved (was: Patch Available) > Grafana dashboard changes for some new llap daemon metrics > -- > > Key: AMBARI-20548 > URL: https://issues.apache.org/jira/browse/AMBARI-20548 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20548.v0.patch, AMBARI-20548.v1.patch > > > Few new metrics (Offheap memory metrics) got added to llap recently which > will be critical for debugging. Also some old metrics in dashboard are not > really useful which can be removed (Llap IO Metrics). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20429) Warn users about pending requests while trying to enable Interactive Query immediately after disabling it
[ https://issues.apache.org/jira/browse/AMBARI-20429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15957838#comment-15957838 ] Vivek Ratnavel Subramanian commented on AMBARI-20429: - Committed to branch-2.5 again - 09105035abd51ef0d820bcafa7ec38cebb079e2f > Warn users about pending requests while trying to enable Interactive Query > immediately after disabling it > - > > Key: AMBARI-20429 > URL: https://issues.apache.org/jira/browse/AMBARI-20429 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.1 > > Attachments: AMBARI-20429.v0.branch-2.5.patch > > > There is no warning or protection for the user to avoid enabling of > Interactive Query immediately after disabling it. Showing a popup to warn the > user about a pending batch request would be helpful here. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20429) Warn users about pending requests while trying to enable Interactive Query immediately after disabling it
[ https://issues.apache.org/jira/browse/AMBARI-20429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved AMBARI-20429. - Resolution: Fixed > Warn users about pending requests while trying to enable Interactive Query > immediately after disabling it > - > > Key: AMBARI-20429 > URL: https://issues.apache.org/jira/browse/AMBARI-20429 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.1 > > Attachments: AMBARI-20429.v0.branch-2.5.patch > > > There is no warning or protection for the user to avoid enabling of > Interactive Query immediately after disabling it. Showing a popup to warn the > user about a pending batch request would be helpful here. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20548) Grafana dashboard changes for some new llap daemon metrics
[ https://issues.apache.org/jira/browse/AMBARI-20548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15943871#comment-15943871 ] Vivek Ratnavel Subramanian commented on AMBARI-20548: - The error message posted by Hadoop QA is unrelated to the patch. > Grafana dashboard changes for some new llap daemon metrics > -- > > Key: AMBARI-20548 > URL: https://issues.apache.org/jira/browse/AMBARI-20548 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20548.v0.patch, AMBARI-20548.v1.patch > > > Few new metrics (Offheap memory metrics) got added to llap recently which > will be critical for debugging. Also some old metrics in dashboard are not > really useful which can be removed (Llap IO Metrics). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20548) Grafana dashboard changes for some new llap daemon metrics
[ https://issues.apache.org/jira/browse/AMBARI-20548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-20548: Attachment: AMBARI-20548.v1.patch > Grafana dashboard changes for some new llap daemon metrics > -- > > Key: AMBARI-20548 > URL: https://issues.apache.org/jira/browse/AMBARI-20548 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20548.v0.patch, AMBARI-20548.v1.patch > > > Few new metrics (Offheap memory metrics) got added to llap recently which > will be critical for debugging. Also some old metrics in dashboard are not > really useful which can be removed (Llap IO Metrics). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20548) Grafana dashboard changes for some new llap daemon metrics
[ https://issues.apache.org/jira/browse/AMBARI-20548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-20548: Status: Patch Available (was: In Progress) > Grafana dashboard changes for some new llap daemon metrics > -- > > Key: AMBARI-20548 > URL: https://issues.apache.org/jira/browse/AMBARI-20548 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20548.v0.patch > > > Few new metrics (Offheap memory metrics) got added to llap recently which > will be critical for debugging. Also some old metrics in dashboard are not > really useful which can be removed (Llap IO Metrics). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20548) Grafana dashboard changes for some new llap daemon metrics
[ https://issues.apache.org/jira/browse/AMBARI-20548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-20548: Attachment: AMBARI-20548.v0.patch > Grafana dashboard changes for some new llap daemon metrics > -- > > Key: AMBARI-20548 > URL: https://issues.apache.org/jira/browse/AMBARI-20548 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20548.v0.patch > > > Few new metrics (Offheap memory metrics) got added to llap recently which > will be critical for debugging. Also some old metrics in dashboard are not > really useful which can be removed (Llap IO Metrics). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20548) Grafana dashboard changes for some new llap daemon metrics
Vivek Ratnavel Subramanian created AMBARI-20548: --- Summary: Grafana dashboard changes for some new llap daemon metrics Key: AMBARI-20548 URL: https://issues.apache.org/jira/browse/AMBARI-20548 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.1 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Priority: Blocker Fix For: 2.5.1 Few new metrics (Offheap memory metrics) got added to llap recently which will be critical for debugging. Also some old metrics in dashboard are not really useful which can be removed (Llap IO Metrics). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20429) Warn users about pending requests while trying to enable Interactive Query immediately after disabling it
[ https://issues.apache.org/jira/browse/AMBARI-20429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-20429: Attachment: AMBARI-20429.v0.branch-2.5.patch > Warn users about pending requests while trying to enable Interactive Query > immediately after disabling it > - > > Key: AMBARI-20429 > URL: https://issues.apache.org/jira/browse/AMBARI-20429 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Attachments: AMBARI-20429.v0.branch-2.5.patch > > > There is no warning or protection for the user to avoid enabling of > Interactive Query immediately after disabling it. Showing a popup to warn the > user about a pending batch request would be helpful here. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20426) Hive Server interactive not removed from Hive summary page after HSI is disabled
[ https://issues.apache.org/jira/browse/AMBARI-20426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-20426: Status: Patch Available (was: In Progress) > Hive Server interactive not removed from Hive summary page after HSI is > disabled > > > Key: AMBARI-20426 > URL: https://issues.apache.org/jira/browse/AMBARI-20426 > Project: Ambari > Issue Type: Bug > Components: ambari-sever, ambari-web >Affects Versions: 2.5.0 >Reporter: Kishor Ramakrishnan >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20426.v0.patch > > > Hive Server interactive not removed from Hive summary page even after HSI is > disabled. > Strange Fact : HSI is started without any error when did a restart all stale > components even though HSI is disabled -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20429) Warn users about pending requests while trying to enable Interactive Query immediately after disabling it
Vivek Ratnavel Subramanian created AMBARI-20429: --- Summary: Warn users about pending requests while trying to enable Interactive Query immediately after disabling it Key: AMBARI-20429 URL: https://issues.apache.org/jira/browse/AMBARI-20429 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian There is no warning or protection for the user to avoid enabling of Interactive Query immediately after disabling it. Showing a popup to warn the user about a pending batch request would be helpful here. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20426) Hive Server interactive not removed from Hive summary page after HSI is disabled
[ https://issues.apache.org/jira/browse/AMBARI-20426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-20426: Attachment: AMBARI-20426.v0.patch > Hive Server interactive not removed from Hive summary page after HSI is > disabled > > > Key: AMBARI-20426 > URL: https://issues.apache.org/jira/browse/AMBARI-20426 > Project: Ambari > Issue Type: Bug > Components: ambari-sever, ambari-web >Affects Versions: 2.5.0 >Reporter: Kishor Ramakrishnan >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20426.v0.patch > > > Hive Server interactive not removed from Hive summary page even after HSI is > disabled. > Strange Fact : HSI is started without any error when did a restart all stale > components even though HSI is disabled -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20426) Hive Server interactive not removed from Hive summary page after HSI is disabled
[ https://issues.apache.org/jira/browse/AMBARI-20426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian reassigned AMBARI-20426: --- Assignee: Vivek Ratnavel Subramanian > Hive Server interactive not removed from Hive summary page after HSI is > disabled > > > Key: AMBARI-20426 > URL: https://issues.apache.org/jira/browse/AMBARI-20426 > Project: Ambari > Issue Type: Bug > Components: ambari-sever, ambari-web >Affects Versions: 2.5.0 >Reporter: Kishor Ramakrishnan >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > > Hive Server interactive not removed from Hive summary page even after HSI is > disabled. > Strange Fact : HSI is started without any error when did a restart all stale > components even though HSI is disabled -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20254) Service Alert Popup - Unexpected User Experience
[ https://issues.apache.org/jira/browse/AMBARI-20254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15902551#comment-15902551 ] Vivek Ratnavel Subramanian commented on AMBARI-20254: - The test failures reported are not related to this patch. > Service Alert Popup - Unexpected User Experience > > > Key: AMBARI-20254 > URL: https://issues.apache.org/jira/browse/AMBARI-20254 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20254.v0.branch-2.5.patch, > AMBARI-20254.v0.trunk.patch, AMBARI-20254.v1.branch-2.5.patch, tooltip2.png > > > AMBARI-19049 introduced some UI changes that causes regression in UX for the > Service Alert popup. > With the change, the user has to click on the expander to see any alert > context. And the expander UX is strange too. Clicking anywhere (including the > hyperlinked text as well as the background) in the header takes the user to > the alerts page. This is not the experience the user would expect based on > conventions. > The cases in which too much context is displayed and therefore needs special > handling is not the norm, so crippling UX for the special case is not the way > to go. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20254) Service Alert Popup - Unexpected User Experience
[ https://issues.apache.org/jira/browse/AMBARI-20254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-20254: Attachment: AMBARI-20254.v1.branch-2.5.patch > Service Alert Popup - Unexpected User Experience > > > Key: AMBARI-20254 > URL: https://issues.apache.org/jira/browse/AMBARI-20254 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20254.v0.branch-2.5.patch, > AMBARI-20254.v0.trunk.patch, AMBARI-20254.v1.branch-2.5.patch, tooltip2.png > > > AMBARI-19049 introduced some UI changes that causes regression in UX for the > Service Alert popup. > With the change, the user has to click on the expander to see any alert > context. And the expander UX is strange too. Clicking anywhere (including the > hyperlinked text as well as the background) in the header takes the user to > the alerts page. This is not the experience the user would expect based on > conventions. > The cases in which too much context is displayed and therefore needs special > handling is not the norm, so crippling UX for the special case is not the way > to go. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20254) Service Alert Popup - Unexpected User Experience
[ https://issues.apache.org/jira/browse/AMBARI-20254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-20254: Attachment: AMBARI-20254.v0.trunk.patch > Service Alert Popup - Unexpected User Experience > > > Key: AMBARI-20254 > URL: https://issues.apache.org/jira/browse/AMBARI-20254 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20254.v0.branch-2.5.patch, > AMBARI-20254.v0.trunk.patch, tooltip2.png > > > AMBARI-19049 introduced some UI changes that causes regression in UX for the > Service Alert popup. > With the change, the user has to click on the expander to see any alert > context. And the expander UX is strange too. Clicking anywhere (including the > hyperlinked text as well as the background) in the header takes the user to > the alerts page. This is not the experience the user would expect based on > conventions. > The cases in which too much context is displayed and therefore needs special > handling is not the norm, so crippling UX for the special case is not the way > to go. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20254) Service Alert Popup - Unexpected User Experience
[ https://issues.apache.org/jira/browse/AMBARI-20254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-20254: Status: Patch Available (was: In Progress) > Service Alert Popup - Unexpected User Experience > > > Key: AMBARI-20254 > URL: https://issues.apache.org/jira/browse/AMBARI-20254 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20254.v0.branch-2.5.patch, > AMBARI-20254.v0.trunk.patch, tooltip2.png > > > AMBARI-19049 introduced some UI changes that causes regression in UX for the > Service Alert popup. > With the change, the user has to click on the expander to see any alert > context. And the expander UX is strange too. Clicking anywhere (including the > hyperlinked text as well as the background) in the header takes the user to > the alerts page. This is not the experience the user would expect based on > conventions. > The cases in which too much context is displayed and therefore needs special > handling is not the norm, so crippling UX for the special case is not the way > to go. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20254) Service Alert Popup - Unexpected User Experience
[ https://issues.apache.org/jira/browse/AMBARI-20254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-20254: Attachment: AMBARI-20254.v0.branch-2.5.patch > Service Alert Popup - Unexpected User Experience > > > Key: AMBARI-20254 > URL: https://issues.apache.org/jira/browse/AMBARI-20254 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20254.v0.branch-2.5.patch, tooltip2.png > > > AMBARI-19049 introduced some UI changes that causes regression in UX for the > Service Alert popup. > With the change, the user has to click on the expander to see any alert > context. And the expander UX is strange too. Clicking anywhere (including the > hyperlinked text as well as the background) in the header takes the user to > the alerts page. This is not the experience the user would expect based on > conventions. > The cases in which too much context is displayed and therefore needs special > handling is not the norm, so crippling UX for the special case is not the way > to go. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20254) Service Alert Popup - Unexpected User Experience
[ https://issues.apache.org/jira/browse/AMBARI-20254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15890265#comment-15890265 ] Vivek Ratnavel Subramanian commented on AMBARI-20254: - I reverted AMBARI-19049 and shortened the alert definition text to 400 characters with ellipsis and also included a tooltip on hover to display the whole text. The result is as seen in the screen-shot tooltip2.png > Service Alert Popup - Unexpected User Experience > > > Key: AMBARI-20254 > URL: https://issues.apache.org/jira/browse/AMBARI-20254 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: tooltip2.png > > > AMBARI-19049 introduced some UI changes that causes regression in UX for the > Service Alert popup. > With the change, the user has to click on the expander to see any alert > context. And the expander UX is strange too. Clicking anywhere (including the > hyperlinked text as well as the background) in the header takes the user to > the alerts page. This is not the experience the user would expect based on > conventions. > The cases in which too much context is displayed and therefore needs special > handling is not the norm, so crippling UX for the special case is not the way > to go. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20254) Service Alert Popup - Unexpected User Experience
[ https://issues.apache.org/jira/browse/AMBARI-20254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-20254: Attachment: tooltip2.png > Service Alert Popup - Unexpected User Experience > > > Key: AMBARI-20254 > URL: https://issues.apache.org/jira/browse/AMBARI-20254 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: tooltip2.png > > > AMBARI-19049 introduced some UI changes that causes regression in UX for the > Service Alert popup. > With the change, the user has to click on the expander to see any alert > context. And the expander UX is strange too. Clicking anywhere (including the > hyperlinked text as well as the background) in the header takes the user to > the alerts page. This is not the experience the user would expect based on > conventions. > The cases in which too much context is displayed and therefore needs special > handling is not the norm, so crippling UX for the special case is not the way > to go. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20254) Service Alert Popup - Unexpected User Experience
Vivek Ratnavel Subramanian created AMBARI-20254: --- Summary: Service Alert Popup - Unexpected User Experience Key: AMBARI-20254 URL: https://issues.apache.org/jira/browse/AMBARI-20254 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Priority: Critical Fix For: 2.5.0 AMBARI-19049 introduced some UI changes that causes regression in UX for the Service Alert popup. With the change, the user has to click on the expander to see any alert context. And the expander UX is strange too. Clicking anywhere (including the hyperlinked text as well as the background) in the header takes the user to the alerts page. This is not the experience the user would expect based on conventions. The cases in which too much context is displayed and therefore needs special handling is not the norm, so crippling UX for the special case is not the way to go. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19907) On certain actions, there's no feedback from the UI when API takes a long time to respond - not reassuring and the user is encouraged to keep triggering the same heavy
[ https://issues.apache.org/jira/browse/AMBARI-19907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19907: Attachment: AMBARI-19907.v1.patch > On certain actions, there's no feedback from the UI when API takes a long > time to respond - not reassuring and the user is encouraged to keep > triggering the same heavy action to make the problem worse > > > Key: AMBARI-19907 > URL: https://issues.apache.org/jira/browse/AMBARI-19907 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19907.v0.branch-2.5.patch, AMBARI-19907.v1.patch > > > On a big cluster, it takes the server a long time to process the API request > for certain operations, like "Stop All", "Start All", etc. > On a small cluster, the "background operations" popup appears within a few > seconds to acknowledge to the user that the server is working on handling the > request. > However, when the cluster gets bigger and the request API takes the server > much longer (e.g., on a 1000-node cluster, it took ~35 seconds), there's no > indication on the UI that the server received the request. This is not > reassuring to the user and the user is tempted to keep re-triggering the > action and overwhelming the server. > This problem is not just for "Start All", "Stop All". This problem actually > happens for "Stop" and "Start" of a single service as well (and likely other > places, like Hosts / Host Detail pages.) On the 1000-node cluster, this > takes about 6-7 seconds, enough to make the user wonder if the request got to > the server or not. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19928) Solr grafana dashboards
[
https://issues.apache.org/jira/browse/AMBARI-19928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15858519#comment-15858519
]
Vivek Ratnavel Subramanian commented on AMBARI-19928:
-
Hi [~willy.solaligue] ,
I am pasting the change I would like to suggest for the first few lines in both
the json files.
{
"id": null,
"title": "Solr Cores Dashboard",
"originalTitle": "Solr Cores Dashboard",
"tags": ["solr"],
...
}
It will be easy to review and mark the proposed changes if you create a new
request in the review board (https://reviews.apache.org/) and add a link to the
JIRA.
> Solr grafana dashboards
> ---
>
> Key: AMBARI-19928
> URL: https://issues.apache.org/jira/browse/AMBARI-19928
> Project: Ambari
> Issue Type: New Feature
>Affects Versions: 2.5.0
>Reporter: Willy Solaligue
>Assignee: Willy Solaligue
>Priority: Minor
> Fix For: 2.5.0
>
> Attachments: AMBARI-19928-2.5.patch, AMBARI-19928-trunk.patch
>
>
> - Add solr grafana dashboards for the solr stack available here:
> https://github.com/lucidworks/solr-stack
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19907) On certain actions, there's no feedback from the UI when API takes a long time to respond - not reassuring and the user is encouraged to keep triggering the same heavy
[ https://issues.apache.org/jira/browse/AMBARI-19907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19907: Status: Patch Available (was: In Progress) > On certain actions, there's no feedback from the UI when API takes a long > time to respond - not reassuring and the user is encouraged to keep > triggering the same heavy action to make the problem worse > > > Key: AMBARI-19907 > URL: https://issues.apache.org/jira/browse/AMBARI-19907 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19907.v0.branch-2.5.patch > > > On a big cluster, it takes the server a long time to process the API request > for certain operations, like "Stop All", "Start All", etc. > On a small cluster, the "background operations" popup appears within a few > seconds to acknowledge to the user that the server is working on handling the > request. > However, when the cluster gets bigger and the request API takes the server > much longer (e.g., on a 1000-node cluster, it took ~35 seconds), there's no > indication on the UI that the server received the request. This is not > reassuring to the user and the user is tempted to keep re-triggering the > action and overwhelming the server. > This problem is not just for "Start All", "Stop All". This problem actually > happens for "Stop" and "Start" of a single service as well (and likely other > places, like Hosts / Host Detail pages.) On the 1000-node cluster, this > takes about 6-7 seconds, enough to make the user wonder if the request got to > the server or not. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19907) On certain actions, there's no feedback from the UI when API takes a long time to respond - not reassuring and the user is encouraged to keep triggering the same heavy
[ https://issues.apache.org/jira/browse/AMBARI-19907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19907: Attachment: AMBARI-19907.v0.branch-2.5.patch > On certain actions, there's no feedback from the UI when API takes a long > time to respond - not reassuring and the user is encouraged to keep > triggering the same heavy action to make the problem worse > > > Key: AMBARI-19907 > URL: https://issues.apache.org/jira/browse/AMBARI-19907 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19907.v0.branch-2.5.patch > > > On a big cluster, it takes the server a long time to process the API request > for certain operations, like "Stop All", "Start All", etc. > On a small cluster, the "background operations" popup appears within a few > seconds to acknowledge to the user that the server is working on handling the > request. > However, when the cluster gets bigger and the request API takes the server > much longer (e.g., on a 1000-node cluster, it took ~35 seconds), there's no > indication on the UI that the server received the request. This is not > reassuring to the user and the user is tempted to keep re-triggering the > action and overwhelming the server. > This problem is not just for "Start All", "Stop All". This problem actually > happens for "Stop" and "Start" of a single service as well (and likely other > places, like Hosts / Host Detail pages.) On the 1000-node cluster, this > takes about 6-7 seconds, enough to make the user wonder if the request got to > the server or not. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19907) On certain actions, there's no feedback from the UI when API takes a long time to respond - not reassuring and the user is encouraged to keep triggering the same heavy
Vivek Ratnavel Subramanian created AMBARI-19907: --- Summary: On certain actions, there's no feedback from the UI when API takes a long time to respond - not reassuring and the user is encouraged to keep triggering the same heavy action to make the problem worse Key: AMBARI-19907 URL: https://issues.apache.org/jira/browse/AMBARI-19907 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Priority: Critical Fix For: 2.5.0 On a big cluster, it takes the server a long time to process the API request for certain operations, like "Stop All", "Start All", etc. On a small cluster, the "background operations" popup appears within a few seconds to acknowledge to the user that the server is working on handling the request. However, when the cluster gets bigger and the request API takes the server much longer (e.g., on a 1000-node cluster, it took ~35 seconds), there's no indication on the UI that the server received the request. This is not reassuring to the user and the user is tempted to keep re-triggering the action and overwhelming the server. This problem is not just for "Start All", "Stop All". This problem actually happens for "Stop" and "Start" of a single service as well (and likely other places, like Hosts / Host Detail pages.) On the 1000-node cluster, this takes about 6-7 seconds, enough to make the user wonder if the request got to the server or not. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-19901) Ambari Kafka Grafana controller metrics should show sum instead of average
[ https://issues.apache.org/jira/browse/AMBARI-19901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian resolved AMBARI-19901. - Resolution: Duplicate Duplicates AMBARI-18468 > Ambari Kafka Grafana controller metrics should show sum instead of average > -- > > Key: AMBARI-19901 > URL: https://issues.apache.org/jira/browse/AMBARI-19901 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > > In Grafana , for Kafka metrics we are showing the Active Controller metric > and Leader Count metric as avg , it should instead be Sum. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19901) Ambari Kafka Grafana controller metrics should show sum instead of average
[ https://issues.apache.org/jira/browse/AMBARI-19901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19901: Affects Version/s: (was: 2.5.0) > Ambari Kafka Grafana controller metrics should show sum instead of average > -- > > Key: AMBARI-19901 > URL: https://issues.apache.org/jira/browse/AMBARI-19901 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > > In Grafana , for Kafka metrics we are showing the Active Controller metric > and Leader Count metric as avg , it should instead be Sum. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19901) Ambari Kafka Grafana controller metrics should show sum instead of average
Vivek Ratnavel Subramanian created AMBARI-19901: --- Summary: Ambari Kafka Grafana controller metrics should show sum instead of average Key: AMBARI-19901 URL: https://issues.apache.org/jira/browse/AMBARI-19901 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 2.5.0 In Grafana , for Kafka metrics we are showing the Active Controller metric and Leader Count metric as avg , it should instead be Sum. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19859) The user must be clearly communicated about YARN pre-emption requirements when Hive LLAP is enabled
[ https://issues.apache.org/jira/browse/AMBARI-19859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15852230#comment-15852230 ] Vivek Ratnavel Subramanian commented on AMBARI-19859: - The test failure is not related to this patch. > The user must be clearly communicated about YARN pre-emption requirements > when Hive LLAP is enabled > --- > > Key: AMBARI-19859 > URL: https://issues.apache.org/jira/browse/AMBARI-19859 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19859.v0.patch, AMBARI-19859.v1.patch, Ambari > c1.png, Screen Shot 2017-02-02 at 7.02.45 PM.png > > > Capacity Scheduler preemption is not enabled by default in HDP. Enabling it > affects the entire cluster. But it is strongly recommended to enable YARN > pre-emption before enabling Hive LLAP. The user needs to be warned about this > before enabling Interactive Query in Hive configs page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19859) The user must be clearly communicated about YARN pre-emption requirements when Hive LLAP is enabled
[ https://issues.apache.org/jira/browse/AMBARI-19859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19859: Attachment: AMBARI-19859.v1.patch > The user must be clearly communicated about YARN pre-emption requirements > when Hive LLAP is enabled > --- > > Key: AMBARI-19859 > URL: https://issues.apache.org/jira/browse/AMBARI-19859 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19859.v0.patch, AMBARI-19859.v1.patch, Ambari > c1.png, Screen Shot 2017-02-02 at 7.02.45 PM.png > > > Capacity Scheduler preemption is not enabled by default in HDP. Enabling it > affects the entire cluster. But it is strongly recommended to enable YARN > pre-emption before enabling Hive LLAP. The user needs to be warned about this > before enabling Interactive Query in Hive configs page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19859) The user must be clearly communicated about YARN pre-emption requirements when Hive LLAP is enabled
[ https://issues.apache.org/jira/browse/AMBARI-19859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19859: Attachment: Screen Shot 2017-02-02 at 7.02.45 PM.png Ambari c1.png > The user must be clearly communicated about YARN pre-emption requirements > when Hive LLAP is enabled > --- > > Key: AMBARI-19859 > URL: https://issues.apache.org/jira/browse/AMBARI-19859 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19859.v0.patch, Ambari c1.png, Screen Shot > 2017-02-02 at 7.02.45 PM.png > > > Capacity Scheduler preemption is not enabled by default in HDP. Enabling it > affects the entire cluster. But it is strongly recommended to enable YARN > pre-emption before enabling Hive LLAP. The user needs to be warned about this > before enabling Interactive Query in Hive configs page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19859) The user must be clearly communicated about YARN pre-emption requirements when Hive LLAP is enabled
[ https://issues.apache.org/jira/browse/AMBARI-19859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15851001#comment-15851001 ] Vivek Ratnavel Subramanian commented on AMBARI-19859: - Attached are the screen-shots after the patch. > The user must be clearly communicated about YARN pre-emption requirements > when Hive LLAP is enabled > --- > > Key: AMBARI-19859 > URL: https://issues.apache.org/jira/browse/AMBARI-19859 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19859.v0.patch, Ambari c1.png, Screen Shot > 2017-02-02 at 7.02.45 PM.png > > > Capacity Scheduler preemption is not enabled by default in HDP. Enabling it > affects the entire cluster. But it is strongly recommended to enable YARN > pre-emption before enabling Hive LLAP. The user needs to be warned about this > before enabling Interactive Query in Hive configs page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19859) The user must be clearly communicated about YARN pre-emption requirements when Hive LLAP is enabled
[ https://issues.apache.org/jira/browse/AMBARI-19859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19859: Attachment: AMBARI-19859.v0.patch > The user must be clearly communicated about YARN pre-emption requirements > when Hive LLAP is enabled > --- > > Key: AMBARI-19859 > URL: https://issues.apache.org/jira/browse/AMBARI-19859 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19859.v0.patch > > > Capacity Scheduler preemption is not enabled by default in HDP. Enabling it > affects the entire cluster. But it is strongly recommended to enable YARN > pre-emption before enabling Hive LLAP. The user needs to be warned about this > before enabling Interactive Query in Hive configs page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19859) The user must be clearly communicated about YARN pre-emption requirements when Hive LLAP is enabled
[ https://issues.apache.org/jira/browse/AMBARI-19859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19859: Status: Patch Available (was: In Progress) > The user must be clearly communicated about YARN pre-emption requirements > when Hive LLAP is enabled > --- > > Key: AMBARI-19859 > URL: https://issues.apache.org/jira/browse/AMBARI-19859 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19859.v0.patch > > > Capacity Scheduler preemption is not enabled by default in HDP. Enabling it > affects the entire cluster. But it is strongly recommended to enable YARN > pre-emption before enabling Hive LLAP. The user needs to be warned about this > before enabling Interactive Query in Hive configs page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19859) The user must be clearly communicated about YARN pre-emption requirements when Hive LLAP is enabled
Vivek Ratnavel Subramanian created AMBARI-19859: --- Summary: The user must be clearly communicated about YARN pre-emption requirements when Hive LLAP is enabled Key: AMBARI-19859 URL: https://issues.apache.org/jira/browse/AMBARI-19859 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 2.5.0 Capacity Scheduler preemption is not enabled by default in HDP. Enabling it affects the entire cluster. But it is strongly recommended to enable YARN pre-emption before enabling Hive LLAP. The user needs to be warned about this before enabling Interactive Query in Hive configs page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19828) UI changes to resolve discrepancies between what the stack vs Ambari reports as "live" for NodeManagers
[ https://issues.apache.org/jira/browse/AMBARI-19828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19828: Attachment: AMBARI-19828.v0.trunk.patch > UI changes to resolve discrepancies between what the stack vs Ambari reports > as "live" for NodeManagers > --- > > Key: AMBARI-19828 > URL: https://issues.apache.org/jira/browse/AMBARI-19828 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19828.v0.branch-2.5.patch, > AMBARI-19828.v0.trunk.patch > > > Looks like the changes in https://issues.apache.org/jira/browse/AMBARI-9418 > was meant to be applied to YARN summary / NodeManagers as well, but that is > not happening. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19828) UI changes to resolve discrepancies between what the stack vs Ambari reports as "live" for NodeManagers
[ https://issues.apache.org/jira/browse/AMBARI-19828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19828: Status: Patch Available (was: In Progress) > UI changes to resolve discrepancies between what the stack vs Ambari reports > as "live" for NodeManagers > --- > > Key: AMBARI-19828 > URL: https://issues.apache.org/jira/browse/AMBARI-19828 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19828.v0.branch-2.5.patch, > AMBARI-19828.v0.trunk.patch > > > Looks like the changes in https://issues.apache.org/jira/browse/AMBARI-9418 > was meant to be applied to YARN summary / NodeManagers as well, but that is > not happening. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19828) UI changes to resolve discrepancies between what the stack vs Ambari reports as "live" for NodeManagers
[ https://issues.apache.org/jira/browse/AMBARI-19828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19828: Attachment: AMBARI-19828.v0.branch-2.5.patch > UI changes to resolve discrepancies between what the stack vs Ambari reports > as "live" for NodeManagers > --- > > Key: AMBARI-19828 > URL: https://issues.apache.org/jira/browse/AMBARI-19828 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19828.v0.branch-2.5.patch > > > Looks like the changes in https://issues.apache.org/jira/browse/AMBARI-9418 > was meant to be applied to YARN summary / NodeManagers as well, but that is > not happening. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19828) UI changes to resolve discrepancies between what the stack vs Ambari reports as "live" for NodeManagers
Vivek Ratnavel Subramanian created AMBARI-19828: --- Summary: UI changes to resolve discrepancies between what the stack vs Ambari reports as "live" for NodeManagers Key: AMBARI-19828 URL: https://issues.apache.org/jira/browse/AMBARI-19828 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 2.5.0 Looks like the changes in https://issues.apache.org/jira/browse/AMBARI-9418 was meant to be applied to YARN summary / NodeManagers as well, but that is not happening. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AMBARI-19716) CS queue refresh happens before the user clicks on the restart button
Title: Message Title Vivek Ratnavel Subramanian updated an issue Ambari / AMBARI-19716 CS queue refresh happens before the user clicks on the restart button Change By: Vivek Ratnavel Subramanian Attachment: AMBARI-19716.v2.branch-2.5.patch Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] [Updated] (AMBARI-19716) CS queue refresh happens before the user clicks on the restart button
[ https://issues.apache.org/jira/browse/AMBARI-19716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19716: Attachment: AMBARI-19716.v1.branch-2.5.patch > CS queue refresh happens before the user clicks on the restart button > - > > Key: AMBARI-19716 > URL: https://issues.apache.org/jira/browse/AMBARI-19716 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19716.v0.branch-2.5.patch, > AMBARI-19716.v1.branch-2.5.patch > > > Build 2.6.0.0-644. > When the llap sliders are moved, and configuration is saved - a queue refresh > happens immediately if the CS config was affected. > It does not wait for the user to click the Restart Services button. > This can cause problems when the num nodes is being reduced, since the app is > still running - and the queue size is too small for it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19717) HDFS TopN Operations by User graph showing wrong data in grafana
[ https://issues.apache.org/jira/browse/AMBARI-19717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19717: Attachment: AMBARI-19717.v0.patch > HDFS TopN Operations by User graph showing wrong data in grafana > > > Key: AMBARI-19717 > URL: https://issues.apache.org/jira/browse/AMBARI-19717 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19717.v0.patch > > > The Operations by User (1min & 5min sliding window) graphs in Grafana HDFS > TopN dashboard is showing wrong data. > The total count range is much lesser than the ranges of all the other graphs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19717) HDFS TopN Operations by User graph showing wrong data in grafana
[ https://issues.apache.org/jira/browse/AMBARI-19717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19717: Status: Patch Available (was: Open) > HDFS TopN Operations by User graph showing wrong data in grafana > > > Key: AMBARI-19717 > URL: https://issues.apache.org/jira/browse/AMBARI-19717 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19717.v0.patch > > > The Operations by User (1min & 5min sliding window) graphs in Grafana HDFS > TopN dashboard is showing wrong data. > The total count range is much lesser than the ranges of all the other graphs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19717) HDFS TopN Operations by User graph showing wrong data in grafana
[ https://issues.apache.org/jira/browse/AMBARI-19717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19717: Description: The Operations by User (1min & 5min sliding window) graphs in Grafana HDFS TopN dashboard is showing wrong data. The total count range is much lesser than the ranges of all the other graphs. was: The Operations by User (1min & 5min sliding window) graphs in Grafana HDFS TopN dashboard is showing wrong data. The total count range is much lesser than the ranges of all the other graphs. I have a live cluster available at http://104.196.90.100:3000/dashboard/db/hdfs-topn > HDFS TopN Operations by User graph showing wrong data in grafana > > > Key: AMBARI-19717 > URL: https://issues.apache.org/jira/browse/AMBARI-19717 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > > The Operations by User (1min & 5min sliding window) graphs in Grafana HDFS > TopN dashboard is showing wrong data. > The total count range is much lesser than the ranges of all the other graphs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19717) HDFS TopN Operations by User graph showing wrong data in grafana
Vivek Ratnavel Subramanian created AMBARI-19717: --- Summary: HDFS TopN Operations by User graph showing wrong data in grafana Key: AMBARI-19717 URL: https://issues.apache.org/jira/browse/AMBARI-19717 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 2.5.0 The Operations by User (1min & 5min sliding window) graphs in Grafana HDFS TopN dashboard is showing wrong data. The total count range is much lesser than the ranges of all the other graphs. I have a live cluster available at http://104.196.90.100:3000/dashboard/db/hdfs-topn -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19716) CS queue refresh happens before the user clicks on the restart button
[ https://issues.apache.org/jira/browse/AMBARI-19716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19716: Status: Patch Available (was: In Progress) > CS queue refresh happens before the user clicks on the restart button > - > > Key: AMBARI-19716 > URL: https://issues.apache.org/jira/browse/AMBARI-19716 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19716.v0.branch-2.5.patch > > > Build 2.6.0.0-644. > When the llap sliders are moved, and configuration is saved - a queue refresh > happens immediately if the CS config was affected. > It does not wait for the user to click the Restart Services button. > This can cause problems when the num nodes is being reduced, since the app is > still running - and the queue size is too small for it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19716) CS queue refresh happens before the user clicks on the restart button
[ https://issues.apache.org/jira/browse/AMBARI-19716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19716: Attachment: AMBARI-19716.v0.branch-2.5.patch > CS queue refresh happens before the user clicks on the restart button > - > > Key: AMBARI-19716 > URL: https://issues.apache.org/jira/browse/AMBARI-19716 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-19716.v0.branch-2.5.patch > > > Build 2.6.0.0-644. > When the llap sliders are moved, and configuration is saved - a queue refresh > happens immediately if the CS config was affected. > It does not wait for the user to click the Restart Services button. > This can cause problems when the num nodes is being reduced, since the app is > still running - and the queue size is too small for it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-19716) CS queue refresh happens before the user clicks on the restart button
Vivek Ratnavel Subramanian created AMBARI-19716: --- Summary: CS queue refresh happens before the user clicks on the restart button Key: AMBARI-19716 URL: https://issues.apache.org/jira/browse/AMBARI-19716 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 2.5.0 Build 2.6.0.0-644. When the llap sliders are moved, and configuration is saved - a queue refresh happens immediately if the CS config was affected. It does not wait for the user to click the Restart Services button. This can cause problems when the num nodes is being reduced, since the app is still running - and the queue size is too small for it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19699) Axis units and aggregators are wrong in some graphs of ambari grafana dashboards
[ https://issues.apache.org/jira/browse/AMBARI-19699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19699: Status: Patch Available (was: Open) > Axis units and aggregators are wrong in some graphs of ambari grafana > dashboards > > > Key: AMBARI-19699 > URL: https://issues.apache.org/jira/browse/AMBARI-19699 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-19699.v0.branch-2.5.patch > > > Need to fix the following: > ReadAllQuery.HostRoleCommandEntity is missing a Y axis. > Total Cache Misses Y axis is wrong should not be time. > Remove Max aggregator from all metrics (JVM dashboard) > Cache Hits and Misses rate graphs aren't in the same units -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19699) Axis units and aggregators are wrong in some graphs of ambari grafana dashboards
[ https://issues.apache.org/jira/browse/AMBARI-19699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-19699: Attachment: AMBARI-19699.v0.branch-2.5.patch > Axis units and aggregators are wrong in some graphs of ambari grafana > dashboards > > > Key: AMBARI-19699 > URL: https://issues.apache.org/jira/browse/AMBARI-19699 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Minor > Fix For: 2.5.0 > > Attachments: AMBARI-19699.v0.branch-2.5.patch > > > Need to fix the following: > ReadAllQuery.HostRoleCommandEntity is missing a Y axis. > Total Cache Misses Y axis is wrong should not be time. > Remove Max aggregator from all metrics (JVM dashboard) > Cache Hits and Misses rate graphs aren't in the same units -- This message was sent by Atlassian JIRA (v6.3.4#6332)
