[jira] [Commented] (AMBARI-25978) add logsearch support
[ https://issues.apache.org/jira/browse/AMBARI-25978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17747389#comment-17747389 ] Zhiguo Wu commented on AMBARI-25978: [~yaolei] [~rongguo@gmail.com] Added, thanks for your contribution > add logsearch support > - > > Key: AMBARI-25978 > URL: https://issues.apache.org/jira/browse/AMBARI-25978 > Project: Ambari > Issue Type: Technical task > Components: ambari-logsearch >Reporter: Robin Zuo >Priority: Major > Fix For: 2.9.0 > > > ambari 2.8.0 does not support logsearch, I'd like to add it in next release -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25918) Ambari is not working with BIGTOP stack 3.2.0
[
https://issues.apache.org/jira/browse/AMBARI-25918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17707881#comment-17707881
]
Zhiguo Wu commented on AMBARI-25918:
Duplicated with: AMBARI-25888
Or check the document prepared for 2.8.0:
https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.8.0
> Ambari is not working with BIGTOP stack 3.2.0
> -
>
> Key: AMBARI-25918
> URL: https://issues.apache.org/jira/browse/AMBARI-25918
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Reporter: Mohammad Arshad
>Priority: Major
> Fix For: 3.0.0
>
>
> I was trying to install hadoop cluster using ambari trunk, ambari metrics
> 3.0.0 and BIGTOP 3.2.0, stack-select from master code
> Installation is failing with following errors
> 1. Stack installation failed with below error
> {code:java}
> 2023-03-31 07:21:11,018 - The 'hadoop-hdfs-datanode' component did not
> advertise a version. This may indicate a problem with the component
> packaging. However, the stack-select tool was able to report a single version
> installed (3.2.0). This is the version that will be reported.
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HDFS/package/scripts/datanode.py",
> line 172, in
> ...
> raise Fail("No package found for {0}(expected name: {1})".format(name,
> name_with_version))
> resource_management.core.exceptions.Fail: No package found for
> hadoop_${stack_version}(expected name: hadoop_3_2_0)
> {code}
> Seems this error is because BIGTOP packages are not versioned properly,
> packages are not prefixed with stack version. As a workaround I removed
> _${stack_version} from metafile.xml from all services for example removed
> _${stack_version} from stacks/BIGTOP/3.2.0/services/FLINK/metainfo.xml
> 2. After removing _${stack_version} from services, packages got installed but
> it is still failing with below error
> {code:java}
> 2023-04-02 16:19:37,115 - The 'hadoop-hdfs-datanode' component did not
> advertise a version. This may indicate a problem with the component
> packaging. However, the stack-select tool was able to report a single version
> installed (3.2.0). This is the version that will be reported.
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stack-hooks/after-INSTALL/scripts/hook.py", line
> 39, in
> ...
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> 'ambari-python-wrap /usr/lib/bigtop-select/distro-select set
> hadoop-hdfs-datanode 3.2.0' returned 1. ERROR: Invalid version 3.2.0
>
> Valid choices:
> 3.2.0
> {code}
> Packages are installed in /usr/lib but bigtop-select is expecting these
> packages at /usr/bigtop/3.2.0. This is causing above problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25894) Missing file service_advisor.py in some serivces
[ https://issues.apache.org/jira/browse/AMBARI-25894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25894: --- Fix Version/s: (was: 2.8.0) > Missing file service_advisor.py in some serivces > - > > Key: AMBARI-25894 > URL: https://issues.apache.org/jira/browse/AMBARI-25894 > Project: Ambari > Issue Type: Task >Reporter: Lei Yao >Assignee: Lei Yao >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > See AMBARI-19090 > Stack advisor should be broken into service advisor per service > In bigtop 3.20 stack, we can add hdfs/yarn/zookeeper service advisor and > delete stack_advisor.py -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25916) Ambari 2.8.0 Release
Zhiguo Wu created AMBARI-25916: -- Summary: Ambari 2.8.0 Release Key: AMBARI-25916 URL: https://issues.apache.org/jira/browse/AMBARI-25916 Project: Ambari Issue Type: Documentation Reporter: Zhiguo Wu -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-24712) Backport Execution Command Library from branch 'branch-feature-AMBARI-14714' to Ambari 2.8.0
[ https://issues.apache.org/jira/browse/AMBARI-24712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-24712: --- Issue Type: Sub-task (was: Technical task) > Backport Execution Command Library from branch 'branch-feature-AMBARI-14714' > to Ambari 2.8.0 > > > Key: AMBARI-24712 > URL: https://issues.apache.org/jira/browse/AMBARI-24712 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Major > Labels: pull-request-available > Fix For: trunk, 2.8.0 > > Time Spent: 3h 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-23476) Install wizard issues
[ https://issues.apache.org/jira/browse/AMBARI-23476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-23476: --- Fix Version/s: (was: 2.8.0) > Install wizard issues > - > > Key: AMBARI-23476 > URL: https://issues.apache.org/jira/browse/AMBARI-23476 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Attachments: Screen Shot 2018-04-05 at 5.35.06 PM.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > In the above cluster, when install wizard is running , reloading Ambari fails > to load the page -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-23419) Refine pre-check message to remove unsupported services before upgrade to HDP-3.0
[ https://issues.apache.org/jira/browse/AMBARI-23419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-23419: --- Fix Version/s: (was: 2.8.0) > Refine pre-check message to remove unsupported services before upgrade to > HDP-3.0 > - > > Key: AMBARI-23419 > URL: https://issues.apache.org/jira/browse/AMBARI-23419 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Vivek Sharma >Assignee: Vivek Sharma >Priority: Critical > Labels: upgrade > > Services such as Falcon. Flume, Mahout, Slider would be removed from HDP-3.0 > stack. The pre-check message to remove them should be refined to say that the > services would be removed and cannot be re-installed after upgrade -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-23655) While adding HDFS Namespace from UI, Timeline service fails to start
[
https://issues.apache.org/jira/browse/AMBARI-23655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-23655:
---
Fix Version/s: (was: 2.8.0)
> While adding HDFS Namespace from UI, Timeline service fails to start
>
>
> Key: AMBARI-23655
> URL: https://issues.apache.org/jira/browse/AMBARI-23655
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
>
> While adding HDFS Namespace from UI, Timeline service fails to start in the
> last step ("Restart All Services") because the active Namenode(from older
> namespace) is in Safe Mode
>
> It seems for restart all service operation we do not wait for namenode to
> leave safemode
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-23876) Upgrade history arrow does not indicate downwards when expanded
[ https://issues.apache.org/jira/browse/AMBARI-23876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-23876: --- Fix Version/s: (was: 2.8.0) > Upgrade history arrow does not indicate downwards when expanded > --- > > Key: AMBARI-23876 > URL: https://issues.apache.org/jira/browse/AMBARI-23876 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Sharma >Assignee: Antonenko Alexander >Priority: Critical > Attachments: s2-upg-history.png > > > See s2-upg-history.png, when 'Upgrade History' panel is expanded - the small > arrow to the left of 'Upgrade' text is still pointing to the right instead of > bottom -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-23327) Regression : Adding Atlas Metadata server, Hiveserver2 on an host takes forever
[ https://issues.apache.org/jira/browse/AMBARI-23327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-23327: --- Fix Version/s: (was: 2.8.0) > Regression : Adding Atlas Metadata server, Hiveserver2 on an host takes > forever > --- > > Key: AMBARI-23327 > URL: https://issues.apache.org/jira/browse/AMBARI-23327 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-24205) TestHeartbeatHandler.testComponents is flaky
[
https://issues.apache.org/jira/browse/AMBARI-24205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-24205:
---
Fix Version/s: (was: 2.8.0)
> TestHeartbeatHandler.testComponents is flaky
>
>
> Key: AMBARI-24205
> URL: https://issues.apache.org/jira/browse/AMBARI-24205
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Attila Doroszlai
>Priority: Major
>
> {{TestHeartbeatHandler.testComponents}} is failing ~15% of the time.
> {noformat}
> [ERROR] Tests run: 24, Failures: 1, Errors: 0, Skipped: 8, Time elapsed:
> 36.768 s <<< FAILURE! - in org.apache.ambari.server.agent.TestHeartbeatHandler
> [ERROR] testComponents(org.apache.ambari.server.agent.TestHeartbeatHandler)
> Time elapsed: 1.203 s <<< FAILURE!
> java.lang.AssertionError: expected:<{HDFS={NAMENODE=MASTER}}> but was:<{}>
> at
> org.apache.ambari.server.agent.TestHeartbeatHandler.testComponents(TestHeartbeatHandler.java:1352)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-24736) Backport Execution Command Library from 'branch-feature-AMBARI-14714' and use it.
[ https://issues.apache.org/jira/browse/AMBARI-24736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-24736: --- Fix Version/s: 2.9.0 (was: 2.8.0) > Backport Execution Command Library from 'branch-feature-AMBARI-14714' and use > it. > - > > Key: AMBARI-24736 > URL: https://issues.apache.org/jira/browse/AMBARI-24736 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Swapan Shridhar >Priority: Major > Fix For: 2.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-24682) Rolling Restarts: Option to specify number of failures per batch
[ https://issues.apache.org/jira/browse/AMBARI-24682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu resolved AMBARI-24682. Resolution: Fixed > Rolling Restarts: Option to specify number of failures per batch > > > Key: AMBARI-24682 > URL: https://issues.apache.org/jira/browse/AMBARI-24682 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.8.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > User may choose maximum number of failures or specify the number of failures > per batch -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-24711) backport mpack rest apis to trunk
[ https://issues.apache.org/jira/browse/AMBARI-24711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-24711: --- Fix Version/s: (was: 2.8.0) > backport mpack rest apis to trunk > - > > Key: AMBARI-24711 > URL: https://issues.apache.org/jira/browse/AMBARI-24711 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.8.0 >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-24805) not all arguments converted during string formatting
[ https://issues.apache.org/jira/browse/AMBARI-24805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu resolved AMBARI-24805. Resolution: Fixed > not all arguments converted during string formatting > > > Key: AMBARI-24805 > URL: https://issues.apache.org/jira/browse/AMBARI-24805 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.1 >Reporter: David Tucker >Priority: Minor > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > While running `ambari-server setup`, this error was encountered: > > ERROR: Exiting with exit code 1. > REASON: Downloading or installing JDK failed: 'Fatal exception: Failed to > download JDK: not all arguments converted during string formatting. Please > check that the JDK is available at > http://public-repo-1.hortonworks.com/ARTIFACTS/jdk-8u112-linux-x64.tar.gz. > Also you may specify JDK file location in local filesystem using > --jdk-location command line argument., exit code 1'. Exiting. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-24814) Add a rolling_restart_supported flag at the stack service endpoint
[ https://issues.apache.org/jira/browse/AMBARI-24814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu resolved AMBARI-24814. Resolution: Fixed > Add a rolling_restart_supported flag at the stack service endpoint > -- > > Key: AMBARI-24814 > URL: https://issues.apache.org/jira/browse/AMBARI-24814 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.8.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Similar to the one at stack service component level we need a flag for HDFS, > YARN and Zookeeper > at api/v1/stacks/HDP/versions//services/ -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-24798) Stack api for services should return if a service is tech preview and warning message content to be displayed
[ https://issues.apache.org/jira/browse/AMBARI-24798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu resolved AMBARI-24798. Resolution: Fixed > Stack api for services should return if a service is tech preview and warning > message content to be displayed > - > > Key: AMBARI-24798 > URL: https://issues.apache.org/jira/browse/AMBARI-24798 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.8.0 >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-24984) RestMetricsPropertyProviderTest is flaky
[
https://issues.apache.org/jira/browse/AMBARI-24984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-24984:
---
Fix Version/s: (was: 2.8.0)
> RestMetricsPropertyProviderTest is flaky
>
>
> Key: AMBARI-24984
> URL: https://issues.apache.org/jira/browse/AMBARI-24984
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Attila Doroszlai
>Priority: Major
>
> RestMetricsPropertyProviderTest is flaky, fails intermittently in Jenkins
> builds:
> {noformat}
> [ERROR] Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 144.862 s <<< FAILURE! - in
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest
> [ERROR]
> testRestMetricsPropertyProviderAsAdministrator(org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest)
> Time elapsed: 0.294 s <<< FAILURE!
> java.lang.AssertionError: expected:<400> but was:<399>
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testPopulateResourcesMany(RestMetricsPropertyProviderTest.java:466)
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsAdministrator(RestMetricsPropertyProviderTest.java:231)
> [ERROR] Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 147.514 s <<< FAILURE! - in
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest
> [ERROR]
> testRestMetricsPropertyProviderAsAdministrator(org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest)
> Time elapsed: 0.051 s <<< FAILURE!
> java.lang.AssertionError: expected:<1> but was:<0>
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testPopulateResources(RestMetricsPropertyProviderTest.java:320)
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsAdministrator(RestMetricsPropertyProviderTest.java:227)
> [ERROR] Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 17.434 s <<< FAILURE! - in
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest
> [ERROR]
> testRestMetricsPropertyProviderAsServiceAdministrator(org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest)
> Time elapsed: 0.088 s <<< FAILURE!
> java.lang.AssertionError: expected:<400> but was:<0>
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testPopulateResourcesMany(RestMetricsPropertyProviderTest.java:466)
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsServiceAdministrator(RestMetricsPropertyProviderTest.java:243)
> [ERROR] Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 17.376 s <<< FAILURE! - in
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest
> [ERROR]
> testRestMetricsPropertyProviderAsServiceAdministrator(org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest)
> Time elapsed: 0.098 s <<< FAILURE!
> java.lang.AssertionError: expected:<1> but was:<0>
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testPopulateResources_singleProperty(RestMetricsPropertyProviderTest.java:359)
> at
> org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest.testRestMetricsPropertyProviderAsServiceAdministrator(RestMetricsPropertyProviderTest.java:240)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-24863) [PERF] Install 250 components request failed when adding hosts
[
https://issues.apache.org/jira/browse/AMBARI-24863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-24863:
---
Fix Version/s: (was: 2.8.0)
> [PERF] Install 250 components request failed when adding hosts
> --
>
> Key: AMBARI-24863
> URL: https://issues.apache.org/jira/browse/AMBARI-24863
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.3
>Reporter: Srikanth Janardhan
>Priority: Critical
> Attachments: ambari-server-500hosts-addHosts.log
>
>
> Install components failed on more than 70 hosts out of 250 hosts that were
> being added
> Ambari server log: [^ambari-server-500hosts-addHosts.log]
> {code:title=BGOps logs}
> stderr:
> Command aborted. Reason: 'Server considered task failed and automatically
> aborted it'
> stdout:
> Command aborted. Reason: 'Server considered task failed and automatically
> aborted it'
> Command failed after 1 tries
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-24856) Ambari-server start CLI command timing out after 2 minutes on U18
[
https://issues.apache.org/jira/browse/AMBARI-24856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-24856:
---
Fix Version/s: (was: 2.8.0)
> Ambari-server start CLI command timing out after 2 minutes on U18
> -
>
> Key: AMBARI-24856
> URL: https://issues.apache.org/jira/browse/AMBARI-24856
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.3
>Reporter: Kishor Ramakrishnan
>Priority: Major
>
> Ambari-server start CLI command timing out after 2 minutes on U18, as the
> start took more than 3 minutes.
> {code:java}
> Using python /usr/bin/python
> Starting ambari-server
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server
> start..ERROR:
> Exiting with exit code 1.
> REASON: Server not yet listening on http port 8080 after 120 seconds. Exiting.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-24976) List Ozone as file system service
[ https://issues.apache.org/jira/browse/AMBARI-24976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-24976: --- Fix Version/s: 2.9.0 (was: 2.8.0) > List Ozone as file system service > - > > Key: AMBARI-24976 > URL: https://issues.apache.org/jira/browse/AMBARI-24976 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.8.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Major > Labels: pull-request-available > Fix For: 2.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25107) Ambari is not respecting host component maintenance mode when performing "Restart All Required" at the cluster level
[ https://issues.apache.org/jira/browse/AMBARI-25107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25107: --- Fix Version/s: 2.9.0 (was: 2.8.0) > Ambari is not respecting host component maintenance mode when performing > "Restart All Required" at the cluster level > > > Key: AMBARI-25107 > URL: https://issues.apache.org/jira/browse/AMBARI-25107 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.2 >Reporter: Andriy Babiichuk >Assignee: Andriy Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.9.0 > > Time Spent: 40m > Remaining Estimate: 0h > > * Put HSI in maintenance mode. > * Changed auth to local mapping in core-site. > * A bunch of services got a restart indicator. > * Triggering "Restart All Required" at the cluster level schedules HSI to be > restarted. HSI restart fails so the entire operation fails. This is > cumbersome because now the user has to trigger "restart affected" for > individual services. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25022) Allow DB setup with password from file
[
https://issues.apache.org/jira/browse/AMBARI-25022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-25022:
---
Fix Version/s: (was: 2.8.0)
> Allow DB setup with password from file
> --
>
> Key: AMBARI-25022
> URL: https://issues.apache.org/jira/browse/AMBARI-25022
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Reporter: Attila Doroszlai
>Priority: Major
>
> Unattended {{ambari-server setup}} for remote DB requires that all parameters
> including the password be specified on the command-line. It would be more
> safe to allow passing the password from a file.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25021) ambari-server setup fails without local Postgres even for remote DBs
[
https://issues.apache.org/jira/browse/AMBARI-25021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-25021:
---
Fix Version/s: (was: 2.8.0)
> ambari-server setup fails without local Postgres even for remote DBs
>
>
> Key: AMBARI-25021
> URL: https://issues.apache.org/jira/browse/AMBARI-25021
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Reporter: Attila Doroszlai
>Priority: Minor
>
> The call to setup Ambari Server with a remote DB fails if Ambari Server host
> doesn't have Postgres installed.
> {noformat:title=ambari-server setup -s --database mysql --databasehost db
> --databaseport=3306 --databasename ambari --databaseusername=ambari
> --databasepassword=bigdata}
> Using python /usr/bin/python
> Setup ambari-server
> Traceback (most recent call last):
> File "/usr/sbin/ambari-server.py", line 45, in
> from ambari_server.serverSetup import reset, setup, setup_jce_policy,
> setup_jdbc
> File "/usr/lib/ambari-server/lib/ambari_server/serverSetup.py", line 89, in
>
> JDBC_DB_OPTION_VALUES = get_supported_jdbc_drivers()
> File "/usr/lib/ambari-server/lib/ambari_server/serverSetup.py", line 86, in
> get_supported_jdbc_drivers
> factory = DBMSConfigFactory()
> File "/usr/lib/ambari-server/lib/ambari_server/dbConfiguration.py", line
> 390, in __init__
> from ambari_server.dbConfiguration_linux import createPGConfig,
> createOracleConfig, createMySQLConfig, \
> File "/usr/lib/ambari-server/lib/ambari_server/dbConfiguration_linux.py",
> line 348, in
> class PGConfig(LinuxDBMSConfig):
> File "/usr/lib/ambari-server/lib/ambari_server/dbConfiguration_linux.py",
> line 378, in PGConfig
> raise FatalException(1, "Cannot find postgresql-setup script.")
> ambari_commons.exceptions.FatalException: 'Fatal exception: Cannot find
> postgresql-setup script., exit code 1'
> {noformat}
> The {{ambari-server}} package has dependency on {{postgresql-server}}.
> Still, it would be nice not to fail unnecessarily.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25014) [Logsearch portal]add/remove columns in service logs table does not work as expected
[ https://issues.apache.org/jira/browse/AMBARI-25014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25014: --- Fix Version/s: (was: 2.8.0) > [Logsearch portal]add/remove columns in service logs table does not work as > expected > > > Key: AMBARI-25014 > URL: https://issues.apache.org/jira/browse/AMBARI-25014 > Project: Ambari > Issue Type: Bug > Components: logsearch >Affects Versions: 2.7.3 >Reporter: Kishor Ramakrishnan >Priority: Major > > [Logsearch portal]add/remove columns in service logs table does not work as > expected > 1. Login to Logsearch portal > 2. Filter logs with some valid time frame > 3. In the service logs table, try to add/remove columns by selecting options > from columns drop down. The Table is expected to be refreshed with the > corresponding action of adding/removing filter columns, but does not get > refreshed. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25046) Implement config group support in the Add Service request
[ https://issues.apache.org/jira/browse/AMBARI-25046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25046: --- Fix Version/s: (was: 2.8.0) > Implement config group support in the Add Service request > - > > Key: AMBARI-25046 > URL: https://issues.apache.org/jira/browse/AMBARI-25046 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.7.3 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Major > > This JIRA tracks the work involved to support the definition of configuration > groups within an Add Service API request call. > Since there are no Blueprint hostgroups that can be relied on, there will > likely need to be a separate syntax for specifying configuration groups in > this request. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-25145) Cover controllers of High Availability wizard with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-25145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu resolved AMBARI-25145. Resolution: Fixed > Cover controllers of High Availability wizard with unit tests > - > > Key: AMBARI-25145 > URL: https://issues.apache.org/jira/browse/AMBARI-25145 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Following files to cover: > * > app/controllers/main/admin/highAvailability/hawq/removeStandby/step3_controller.js > * > app/controllers/main/admin/highAvailability/hawq/removeStandby/wizard_controller.js -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-25131) Alert notification properties are wiped after enabling/disabling the notification
[ https://issues.apache.org/jira/browse/AMBARI-25131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu resolved AMBARI-25131. Resolution: Fixed > Alert notification properties are wiped after enabling/disabling the > notification > - > > Key: AMBARI-25131 > URL: https://issues.apache.org/jira/browse/AMBARI-25131 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.8.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > STR: > Create alert notification (tested on ALERT_SCRIPT notification_type) > Populate Script Dispatch Property and/or Script Filename > Disable the notification > Enable the notification > Script Dispatch Property and/or Script Filename properties are empty -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-25144) Cover config history controller with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-25144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu resolved AMBARI-25144. Resolution: Fixed > Cover config history controller with unit tests > --- > > Key: AMBARI-25144 > URL: https://issues.apache.org/jira/browse/AMBARI-25144 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Following files to cover: > * app/controllers/main/dashboard/config_history_controller.js -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25769) Missing yarn.resourcemanager.address. property when enabling resource manager HA
[ https://issues.apache.org/jira/browse/AMBARI-25769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25769: --- Fix Version/s: (was: 2.8.0) > Missing yarn.resourcemanager.address. property when enabling resource > manager HA > > > Key: AMBARI-25769 > URL: https://issues.apache.org/jira/browse/AMBARI-25769 > Project: Ambari > Issue Type: Improvement >Reporter: Lei Yao >Assignee: Lei Yao >Priority: Minor > Attachments: screenshot-1.png > > > When enabling Yarn HA , the yarn.resourcemanager.address. property is > not added. > !screenshot-1.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25761) Add Ranger support for Bigtop 3.3.0 Stack
[ https://issues.apache.org/jira/browse/AMBARI-25761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25761: --- Fix Version/s: (was: 2.8.0) > Add Ranger support for Bigtop 3.3.0 Stack > - > > Key: AMBARI-25761 > URL: https://issues.apache.org/jira/browse/AMBARI-25761 > Project: Ambari > Issue Type: Task >Reporter: Lei Yao >Assignee: Lei Yao >Priority: Major > > Add Ranger support for Bigtop 3.3.0 Stack > Related JIRA > https://issues.apache.org/jira/browse/BIGTOP-3909 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-24733) Rolling Restarts: Option to pause, resume and abort restarts
[ https://issues.apache.org/jira/browse/AMBARI-24733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu resolved AMBARI-24733. Resolution: Fixed > Rolling Restarts: Option to pause, resume and abort restarts > > > Key: AMBARI-24733 > URL: https://issues.apache.org/jira/browse/AMBARI-24733 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.8.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 3h 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-24118) Update KNOX Service Config to Better Integrate the Knox Admin UI
[ https://issues.apache.org/jira/browse/AMBARI-24118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-24118: --- Fix Version/s: 2.9.0 (was: 2.8.0) > Update KNOX Service Config to Better Integrate the Knox Admin UI > > > Key: AMBARI-24118 > URL: https://issues.apache.org/jira/browse/AMBARI-24118 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Reporter: Larry McCay >Assignee: Larry McCay >Priority: Major > Fix For: 2.9.0 > > Attachments: AMBARI-24118-001.patch > > > The manager.xml topology in Apache Knox hosts the endpoint for the Knox Admin > UI. In order to provide management of the configuration for access to the UI > we need to be able to manage the LDAP configuration for authentication, group > lookup and the ACLs for constraining access to admin users and groups. > We have taken a couple actions in Knox to facilitate this: > # Moved the authentication in manager.xml to leverage KnoxSSO as the > authentication mechanism. Will also buy us seamless SSO between Ambari and > Knox UIs. > # Made the group look up manageable from the gateway-site.xml and the > admin.xml and manager.xml topologies auto-redeploy on startup of the Knox > server to pick up gateway-site changes. > # Made the list of admin users and admin groups configurable in > gateway-site.xml > This patch will default the KNOX_ADMIN_USERS to "admin" and the > KNOX_ADMIN_GROUPS to "admin". These values will work with the Knox DEMO LDAP > server that can be used for demos and testing but will need to be adjusted to > the enterprise LDAP users/groups that require access to the Knox Admin UI. > The HadoopGroupProvider will assume the default configuration but when there > are no local OS accounts, the admin will be able to configure LDAP or other > group mapping mechanisms in gateway-site.xml via advanced params. > Lastly, the patch adds the admin group to the DEMO LDAP users.ldif file to > facilitate group lookup if needed. It will actually use no lookup by default > and will grant access to a user named "admin" only but can be configured to > use the admin group. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-23925) Zeppelin is not respecting the absolute hdfs path for notebooks
[ https://issues.apache.org/jira/browse/AMBARI-23925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-23925: --- Fix Version/s: 2.9.0 (was: 2.8.0) > Zeppelin is not respecting the absolute hdfs path for notebooks > --- > > Key: AMBARI-23925 > URL: https://issues.apache.org/jira/browse/AMBARI-23925 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.7.0 >Reporter: Supreeth Sharma >Assignee: Supreeth Sharma >Priority: Critical > Labels: pull-request-available > Fix For: 2.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Zeppelin is not respecting the absolute hdfs path and picking up the > incorrect path for notebooks. > Even when user is setting 'zeppelin.notebook.dir' as > 'hdfs://ns2/zeppelin/tmp/tmp1/notebook', ambari is picking up the path as > /user/zeppelin/hdfs://ns2/zeppelin/tmp/tmp1/notebook > and due to this zeppelin service start is failing. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-24744) Use Execution Command library (AMBARI-24712) in Ambari code base, wherever applicable.
[ https://issues.apache.org/jira/browse/AMBARI-24744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-24744: --- Fix Version/s: 2.9.0 (was: trunk) (was: 2.8.0) > Use Execution Command library (AMBARI-24712) in Ambari code base, wherever > applicable. > -- > > Key: AMBARI-24744 > URL: https://issues.apache.org/jira/browse/AMBARI-24744 > Project: Ambari > Issue Type: Technical task > Components: ambari-server >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Major > Labels: pull-request-available > Fix For: 2.9.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-24759) Ambari Server test failures with JDK11
[
https://issues.apache.org/jira/browse/AMBARI-24759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-24759:
---
Fix Version/s: (was: 2.8.0)
> Ambari Server test failures with JDK11
> --
>
> Key: AMBARI-24759
> URL: https://issues.apache.org/jira/browse/AMBARI-24759
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.1
>Reporter: Gabor Boros
>Assignee: Gabor Boros
>Priority: Major
> Labels: jdk11, pull-request-available
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Ambari Server tests failures prevent build with JDK11:
> {code}
> ± % JAVA_HOME=/tmp/jdk-11 mvn clean test -Drat.skip=true -am -pl
> ambari-server -DskipPythonTests=true
> ...
> ...
> [ERROR] ViewThrottleFilterTest.initializationError ? Objenesis
> java.lang.reflect.Invoc...
> [ERROR] DataStoreImplTest.initializationError ? Objenesis
> java.lang.reflect.Invocation...
> [INFO]
> [ERROR] Tests run: 4651, Failures: 0, Errors: 62, Skipped: 71
> [INFO]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main SUCCESS [ 2.216
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.008
> s]
> [INFO] Ambari Views ... SUCCESS [ 57.359
> s]
> [INFO] ambari-utility . SUCCESS [ 4.158
> s]
> [INFO] Ambari Server SPI .. SUCCESS [ 1.341
> s]
> [INFO] Ambari Service Advisor . SUCCESS [ 0.355
> s]
> [INFO] Ambari Server .. FAILURE [20:17
> min]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 21:23 min
> [INFO] Finished at: 2018-10-10T15:01:04+00:00
> [INFO] Final Memory: 133M/494M
> [INFO]
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Reopened] (AMBARI-24759) Ambari Server test failures with JDK11
[
https://issues.apache.org/jira/browse/AMBARI-24759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu reopened AMBARI-24759:
> Ambari Server test failures with JDK11
> --
>
> Key: AMBARI-24759
> URL: https://issues.apache.org/jira/browse/AMBARI-24759
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.1
>Reporter: Gabor Boros
>Assignee: Gabor Boros
>Priority: Major
> Labels: jdk11, pull-request-available
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Ambari Server tests failures prevent build with JDK11:
> {code}
> ± % JAVA_HOME=/tmp/jdk-11 mvn clean test -Drat.skip=true -am -pl
> ambari-server -DskipPythonTests=true
> ...
> ...
> [ERROR] ViewThrottleFilterTest.initializationError ? Objenesis
> java.lang.reflect.Invoc...
> [ERROR] DataStoreImplTest.initializationError ? Objenesis
> java.lang.reflect.Invocation...
> [INFO]
> [ERROR] Tests run: 4651, Failures: 0, Errors: 62, Skipped: 71
> [INFO]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main SUCCESS [ 2.216
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.008
> s]
> [INFO] Ambari Views ... SUCCESS [ 57.359
> s]
> [INFO] ambari-utility . SUCCESS [ 4.158
> s]
> [INFO] Ambari Server SPI .. SUCCESS [ 1.341
> s]
> [INFO] Ambari Service Advisor . SUCCESS [ 0.355
> s]
> [INFO] Ambari Server .. FAILURE [20:17
> min]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 21:23 min
> [INFO] Finished at: 2018-10-10T15:01:04+00:00
> [INFO] Final Memory: 133M/494M
> [INFO]
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-24841) Pause after first batch
[ https://issues.apache.org/jira/browse/AMBARI-24841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu resolved AMBARI-24841. Resolution: Fixed > Pause after first batch > --- > > Key: AMBARI-24841 > URL: https://issues.apache.org/jira/browse/AMBARI-24841 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.8.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Option to automatically pause after the first batch is completed -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-24759) Ambari Server test failures with JDK11
[
https://issues.apache.org/jira/browse/AMBARI-24759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu resolved AMBARI-24759.
Resolution: Fixed
> Ambari Server test failures with JDK11
> --
>
> Key: AMBARI-24759
> URL: https://issues.apache.org/jira/browse/AMBARI-24759
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.1
>Reporter: Gabor Boros
>Assignee: Gabor Boros
>Priority: Major
> Labels: jdk11, pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Ambari Server tests failures prevent build with JDK11:
> {code}
> ± % JAVA_HOME=/tmp/jdk-11 mvn clean test -Drat.skip=true -am -pl
> ambari-server -DskipPythonTests=true
> ...
> ...
> [ERROR] ViewThrottleFilterTest.initializationError ? Objenesis
> java.lang.reflect.Invoc...
> [ERROR] DataStoreImplTest.initializationError ? Objenesis
> java.lang.reflect.Invocation...
> [INFO]
> [ERROR] Tests run: 4651, Failures: 0, Errors: 62, Skipped: 71
> [INFO]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main SUCCESS [ 2.216
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.008
> s]
> [INFO] Ambari Views ... SUCCESS [ 57.359
> s]
> [INFO] ambari-utility . SUCCESS [ 4.158
> s]
> [INFO] Ambari Server SPI .. SUCCESS [ 1.341
> s]
> [INFO] Ambari Service Advisor . SUCCESS [ 0.355
> s]
> [INFO] Ambari Server .. FAILURE [20:17
> min]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 21:23 min
> [INFO] Finished at: 2018-10-10T15:01:04+00:00
> [INFO] Final Memory: 133M/494M
> [INFO]
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-25817) Fix DDLTests.testVerifyMySQL and DDLTests.testCompareMySQL Ambari test failures
[
https://issues.apache.org/jira/browse/AMBARI-25817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu resolved AMBARI-25817.
Resolution: Fixed
> Fix DDLTests.testVerifyMySQL and DDLTests.testCompareMySQL Ambari test
> failures
> ---
>
> Key: AMBARI-25817
> URL: https://issues.apache.org/jira/browse/AMBARI-25817
> Project: Ambari
> Issue Type: Bug
>Reporter: Himanshu Maurya
>Assignee: Himanshu Maurya
>Priority: Major
> Fix For: 2.8.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> FAILURE! - in org.apache.ambari.server.orm.db.DDLTests in testVerifyMySQL and
> testCompareMySQL
> {code:java}
> [ERROR] testVerifyMySQL(org.apache.ambari.server.orm.db.DDLTests) Time
> elapsed: 0.054 s <<< ERROR!
> com.google.common.util.concurrent.UncheckedExecutionException:
> java.lang.IllegalStateException: Optional.get() cannot be called on an absent
> value
> at org.apache.ambari.server.orm.db.DDLTests.verifyDDL(DDLTests.java:89)
> at
> org.apache.ambari.server.orm.db.DDLTests.testVerifyMySQL(DDLTests.java:60)
> Caused by: java.lang.IllegalStateException: Optional.get() cannot be called
> on an absent value
> at org.apache.ambari.server.orm.db.DDLTests.verifyDDL(DDLTests.java:89)
> at
> org.apache.ambari.server.orm.db.DDLTests.testVerifyMySQL(DDLTests.java:60)
> [ERROR] testCompareMySQL(org.apache.ambari.server.orm.db.DDLTests) Time
> elapsed: 0.047 s <<< ERROR!
> com.google.common.util.concurrent.UncheckedExecutionException:
> java.lang.IllegalStateException: Optional.get() cannot be called on an absent
> value
> at
> org.apache.ambari.server.orm.db.DDLTests.compareAgainstPostgres(DDLTests.java:150)
> at
> org.apache.ambari.server.orm.db.DDLTests.testCompareMySQL(DDLTests.java:134)
> Caused by: java.lang.IllegalStateException: Optional.get() cannot be called
> on an absent value
> at
> org.apache.ambari.server.orm.db.DDLTests.compareAgainstPostgres(DDLTests.java:150)
> at
> org.apache.ambari.server.orm.db.DDLTests.testCompareMySQL(DDLTests.java:134)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25790) HBase put metrics are not populated
[
https://issues.apache.org/jira/browse/AMBARI-25790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-25790:
---
Fix Version/s: metrics-3.1.0
(was: 2.8.0)
> HBase put metrics are not populated
>
>
> Key: AMBARI-25790
> URL: https://issues.apache.org/jira/browse/AMBARI-25790
> Project: Ambari
> Issue Type: Bug
> Components: metrics
>Reporter: Rajeshbabu Chintaguntla
>Assignee: Rajeshbabu Chintaguntla
>Priority: Major
> Labels: pull-request-available
> Fix For: metrics-3.1.0
>
>
> Currently the HBase put metrics are defined as
> {noformat}
> regionserver.Server.Mutate_75th_percentile
> regionserver.Server.Mutate_95th_percentile
> regionserver.Server.Mutate_99th_percentile
> regionserver.Server.Mutate_max
> regionserver.Server.Mutate_mean
> regionserver.Server.Mutate_median
> ipc.IPC.receivedBytes
> regionserver.Server.Mutate_min
> regionserver.Server.Mutate_num_ops
> {noformat}
> But actual metrics need to be defined for writes should be Put as below.
> {noformat}
> "Put_num_ops": 12007275,
> "Put_min": 0,
> "Put_max": 0,
> "Put_mean": 0,
> "Put_25th_percentile": 0,
> "Put_median": 0,
> "Put_75th_percentile": 0,
> "Put_90th_percentile": 0,
> "Put_95th_percentile": 0,
> "Put_98th_percentile": 0,
> "Put_99th_percentile": 0,
> "Put_99.9th_percentile": 0,
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25842) Update Angular version in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-25842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25842: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Update Angular version in Ambari > - > > Key: AMBARI-25842 > URL: https://issues.apache.org/jira/browse/AMBARI-25842 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: 2.8.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.8.0 > > Attachments: AMBARI-25842--branch-2.7.7.patch, > AMBARI-25842--trunk.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Angluar version in Ambari admin-web needs to be updated. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25842) Update Angular version in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-25842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25842: --- Affects Version/s: 2.8.0 (was: 2.7.8) > Update Angular version in Ambari > - > > Key: AMBARI-25842 > URL: https://issues.apache.org/jira/browse/AMBARI-25842 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: 2.8.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.8.0 > > Attachments: AMBARI-25842--branch-2.7.7.patch, > AMBARI-25842--trunk.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Angluar version in Ambari admin-web needs to be updated. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25842) Update Angular version in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-25842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25842: --- Fix Version/s: (was: 2.7.8) > Update Angular version in Ambari > - > > Key: AMBARI-25842 > URL: https://issues.apache.org/jira/browse/AMBARI-25842 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: 2.7.8 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Fix For: 2.8.0 > > Attachments: AMBARI-25842--branch-2.7.7.patch, > AMBARI-25842--trunk.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Angluar version in Ambari admin-web needs to be updated. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-25792) Introduce BIGTOP as default stack
[ https://issues.apache.org/jira/browse/AMBARI-25792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu resolved AMBARI-25792. Resolution: Fixed > Introduce BIGTOP as default stack > - > > Key: AMBARI-25792 > URL: https://issues.apache.org/jira/browse/AMBARI-25792 > Project: Ambari > Issue Type: Epic >Affects Versions: 2.8.0 >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Fix For: 2.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25775) Failed to compile Ambari-Infra because of invalid url
[
https://issues.apache.org/jira/browse/AMBARI-25775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-25775:
---
Epic Link: (was: AMBARI-25792)
Fix Version/s: (was: 2.8.0)
Affects Version/s: (was: 2.8.0)
> Failed to compile Ambari-Infra because of invalid url
> -
>
> Key: AMBARI-25775
> URL: https://issues.apache.org/jira/browse/AMBARI-25775
> Project: Ambari
> Issue Type: Bug
> Components: ambari-infra
> Environment: Centos7
> Ambari-infra-2.8.0
>Reporter: Yu Hou
>Assignee: Yu Hou
>Priority: Major
> Labels: pull-request-available
> Attachments: image-2022-11-04-10-05-46-029.png
>
>
> http://central.maven.org/maven2 has been unable to access
> !image-2022-11-04-10-05-46-029.png!
> {code}
> kage/code/ambari-infra/ambari-infra-solr-client/target/migrate/lucene-core-6.6.2.jar
> [INFO]
>
> [INFO] Reactor Summary for ambari-infra 3.0.0.0-SNAPSHOT:
> [INFO]
> [INFO] ambari-infra ... SUCCESS [ 6.914
> s]
> [INFO] Ambari Infra Solr Client ... FAILURE [ 7.090
> s]
> [INFO] Ambari Infra Solr Plugin ... SKIPPED
> [INFO] Ambari Infra Manager ... SKIPPED
> [INFO] Ambari Infra Assembly .. SKIPPED
> [INFO] Ambari Infra Manager Integration Tests . SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 14.279 s
> [INFO] Finished at: 2022-11-04T10:04:29+08:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-antrun-plugin:1.7:run (default) on project
> ambari-infra-solr-client: An Ant BuildException has occured: The following
> error occurred while executing this line:
> [ERROR] /opt/package/code/ambari-infra/ambari-infra-solr-client/build.xml:39:
> java.net.UnknownHostException: central.maven.org
> [ERROR] around Ant part .. @ 4:28 in
> /opt/package/code/ambari-infra/ambari-infra-solr-client/target/antrun/build-main.xml:
> Unknown host central.maven.org
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :ambari-infra-solr-client
> make: *** [rpm] Error 1
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25863) Fix a problem where the 'supported-refresh-commands' Element in configuration files for service was invalided
[ https://issues.apache.org/jira/browse/AMBARI-25863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25863: --- Epic Link: (was: AMBARI-25792) Fix Version/s: (was: 2.8.0) Affects Version/s: (was: 2.8.0) > Fix a problem where the 'supported-refresh-commands' Element in configuration > files for service was invalided > - > > Key: AMBARI-25863 > URL: https://issues.apache.org/jira/browse/AMBARI-25863 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Environment: Centos7(x86_64) > Ambari-2.8.0 > Bigtop-3.2.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Attachments: image-2023-02-23-21-53-04-918.png, > image-2023-02-23-21-56-07-440.png, image-2023-02-23-21-58-31-071.png > > Time Spent: 10m > Remaining Estimate: 0h > > As https://issues.apache.org/jira/browse/AMBARI-21406 > describes，'supported-refresh-commands' can Refresh configurations without > restart command. > But it has a few bugs that cause the 'supported-refresh-commands' tags to > fail, as shown below, > !image-2023-02-23-21-53-04-918.png! > which they should be to stay consistent with the rest. > !image-2023-02-23-21-56-07-440.png! > How was this patch tested? > !image-2023-02-23-21-58-31-071.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-25799) Introduce AMBARI-METRICS to BIGTOP stack
[ https://issues.apache.org/jira/browse/AMBARI-25799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu resolved AMBARI-25799. Resolution: Fixed > Introduce AMBARI-METRICS to BIGTOP stack > > > Key: AMBARI-25799 > URL: https://issues.apache.org/jira/browse/AMBARI-25799 > Project: Ambari > Issue Type: Improvement > Components: ambari-metrics >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Fix For: 2.8.0 > > > Introduce AMBARI-METRICS service to common-services -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25913) Align version of Ambari Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25913: --- Parent: AMBARI-25799 Issue Type: Sub-task (was: Task) > Align version of Ambari Metrics > --- > > Key: AMBARI-25913 > URL: https://issues.apache.org/jira/browse/AMBARI-25913 > Project: Ambari > Issue Type: Sub-task >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Fix For: 2.8.0 > > Time Spent: 50m > Remaining Estimate: 0h > > We need to align version after release ambari-metrics 3.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-22442) Log Search GA
[ https://issues.apache.org/jira/browse/AMBARI-22442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-22442: --- Fix Version/s: 2.9.0 (was: 2.8.0) > Log Search GA > - > > Key: AMBARI-22442 > URL: https://issues.apache.org/jira/browse/AMBARI-22442 > Project: Ambari > Issue Type: Epic > Components: ambari-logsearch >Affects Versions: 2.9.0 >Reporter: Oliver Szabo >Assignee: Oliver Szabo >Priority: Blocker > Fix For: 2.9.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-22442) Log Search GA
[ https://issues.apache.org/jira/browse/AMBARI-22442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-22442: --- Affects Version/s: 2.9.0 (was: 2.8.0) > Log Search GA > - > > Key: AMBARI-22442 > URL: https://issues.apache.org/jira/browse/AMBARI-22442 > Project: Ambari > Issue Type: Epic > Components: ambari-logsearch >Affects Versions: 2.9.0 >Reporter: Oliver Szabo >Assignee: Oliver Szabo >Priority: Blocker > Fix For: 2.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-24686) Ambari 2.8 Stack Upgrades
[ https://issues.apache.org/jira/browse/AMBARI-24686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu resolved AMBARI-24686. Resolution: Fixed > Ambari 2.8 Stack Upgrades > - > > Key: AMBARI-24686 > URL: https://issues.apache.org/jira/browse/AMBARI-24686 > Project: Ambari > Issue Type: Epic > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Major > Fix For: 2.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-25050) Create Ambari Setting to Control VDF Filesystem Access
[
https://issues.apache.org/jira/browse/AMBARI-25050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu resolved AMBARI-25050.
Resolution: Fixed
> Create Ambari Setting to Control VDF Filesystem Access
> --
>
> Key: AMBARI-25050
> URL: https://issues.apache.org/jira/browse/AMBARI-25050
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Create an entry in {{ambari.properties}} to control whether to allow reading
> filesystem VDF. Default {{false}} for this access.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-24011) Add workaround to hide client modules in the dashboard
[ https://issues.apache.org/jira/browse/AMBARI-24011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-24011: --- Fix Version/s: 3.0.0 > Add workaround to hide client modules in the dashboard > -- > > Key: AMBARI-24011 > URL: https://issues.apache.org/jira/browse/AMBARI-24011 > Project: Ambari > Issue Type: Task >Reporter: Jayush Luniya >Assignee: Jayush Luniya >Priority: Blocker > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Add workaround to hide client modules in the dashboard until we figure out > how to represent client modules across mpacks. > > cc: [~ishanbha] [~jgolieb] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-25915) The quicklink of Solr is not display
[ https://issues.apache.org/jira/browse/AMBARI-25915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu resolved AMBARI-25915. Fix Version/s: 2.8.0 Assignee: guluo Resolution: Fixed > The quicklink of Solr is not display > > > Key: AMBARI-25915 > URL: https://issues.apache.org/jira/browse/AMBARI-25915 > Project: Ambari > Issue Type: Bug > Components: solr >Affects Versions: trunk > Environment: Centos7 > ambari-trunk >Reporter: guluo >Assignee: guluo >Priority: Minor > Fix For: 2.8.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Create a cluster containing Solr, > And I found there is nothing in section of Solr's quicklinks, > But in fact Solr has Solr UI service -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-25914) Solr startup failed beacause of starting before Zookeeper
[ https://issues.apache.org/jira/browse/AMBARI-25914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu resolved AMBARI-25914. Fix Version/s: 2.8.0 Assignee: guluo Resolution: Fixed > Solr startup failed beacause of starting before Zookeeper > - > > Key: AMBARI-25914 > URL: https://issues.apache.org/jira/browse/AMBARI-25914 > Project: Ambari > Issue Type: Bug > Components: solr >Affects Versions: trunk > Environment: Centos7 > Ambari-trunk >Reporter: guluo >Assignee: guluo >Priority: Critical > Fix For: 2.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > I create a cluster containing HDFS/ZK/Solr Service by Ambari. > Solr startup failed during the startup service phase. > I found that the reason for Solr startup failed was that Solr startup before > Zookeeper-server by default on Ambari. > > This is not correct because Solr is dependent on ZK . -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-25913) Align version of Ambari Metrics
[ https://issues.apache.org/jira/browse/AMBARI-25913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu resolved AMBARI-25913. Resolution: Fixed > Align version of Ambari Metrics > --- > > Key: AMBARI-25913 > URL: https://issues.apache.org/jira/browse/AMBARI-25913 > Project: Ambari > Issue Type: Task >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Fix For: 2.8.0 > > Time Spent: 50m > Remaining Estimate: 0h > > We need to align version after release ambari-metrics 3.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25913) Align version of Ambari Metrics
Zhiguo Wu created AMBARI-25913: -- Summary: Align version of Ambari Metrics Key: AMBARI-25913 URL: https://issues.apache.org/jira/browse/AMBARI-25913 Project: Ambari Issue Type: Task Reporter: Zhiguo Wu Assignee: Zhiguo Wu Fix For: 2.8.0 We need to align version after release ambari-metrics 3.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25854) Ambari With Python3 Support
[
https://issues.apache.org/jira/browse/AMBARI-25854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17704056#comment-17704056
]
Zhiguo Wu commented on AMBARI-25854:
[~Charming603473] PR is enough, thanks a lot for helping with this feature!
> Ambari With Python3 Support
> ---
>
> Key: AMBARI-25854
> URL: https://issues.apache.org/jira/browse/AMBARI-25854
> Project: Ambari
> Issue Type: Improvement
>Affects Versions: 2.7.5
> Environment: {*}Ambari：{*}Ambari-2.7.5
> *OS：* OpenEuler-22.03
> *Python：* Python 3.9.9
>
>
>
>Reporter: Charming Wu
>Priority: Major
> Labels: Ambari, OpenEuler, Python3
>
> Python3 had been released for more than 10 years and has obvious difference
> with Python2. Support for python3 is an increasing urgent need.
> In this issue, I would like to continiously provide some modification on
> Ambari for python3 support and welcome your discussion and help!
>
> Main Topic :
> Adapt Ambari from Python2 to Python3 !
>
> Patch Nodes:
> --patch1-sitpacke.patch
> 1. Modify tag "python 2.6" or "python 2.7" to "python 3.9".
> 2. python version judgement compatibility.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-25881) Ambari Metrics 3.0.0 Release
[ https://issues.apache.org/jira/browse/AMBARI-25881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu resolved AMBARI-25881. Resolution: Done > Ambari Metrics 3.0.0 Release > > > Key: AMBARI-25881 > URL: https://issues.apache.org/jira/browse/AMBARI-25881 > Project: Ambari > Issue Type: Documentation >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Labels: release-note > > h1. Release Notes: > h2. Bug > * [AMBARI-17382] - Migrate AMS queries to use ROW_TIMESTAMP instead of > native timerange hint > * [AMBARI-21214] - Use a uuid vs long row key for metrics in AMS schema > * [AMBARI-24665] - Migrating grafana plugin for 5.x use > * [AMBARI-24688] - Backend changes for the newer version of AMS Grafana. > * [AMBARI-24884] - AMS Grafana query editor panel does not work in upgraded > version. > * [AMBARI-24898] - Add cluster drop down to Grafana aggregate dashboards. > * [AMBARI-25780] - Ambari metrics should upgrade hadoop and hbase for known > CVE issues > * [AMBARI-25782] - Fix Ambari Metrics build failure > * [AMBARI-25808] - Metrics data simulator throws NPE > * [AMBARI-25809] - ambari-metrics-host-monitoring project build creates temp > folder outside of target folder > * [AMBARI-25810] - Allow skipping Python unit tests in ambari-metrics > * [AMBARI-25819] - Ambari Metrics build fails when using -Dbuild-rpm > * [AMBARI-25821] - Fixed syntax error that caused OOM in the > ambari-metrics-collector > * [AMBARI-25822] - Remove invalid relocations in pom.xml for > ambari-metrics-common > * [AMBARI-25828] - Switch class Metrics to KafkaYammerMetrics on Ambari > Metrics > * [AMBARI-25834] - Fix syntax errors for ambari-metrics-collector > * [AMBARI-25859] - Correct Ambari Metrics version parsing logic > * [AMBARI-25864] - Fix an unit test failure on ambari-metrics-common > * [AMBARI-25865] - Fix an unit test failure on ambari-metrics-host-monitoring > * [AMBARI-25866] - Fix an unit test failure on ambari-metrics-kafka-sink > h2. Epic > * [AMBARI-20773] - AMS: Schema changes for nextGen feature support > * [AMBARI-22745] - Migrate AMS from HBase 1.1.2 to HBase 2.0 > * [AMBARI-23466] - Upgrade AMS Grafana version to 9.3.2 > * [AMBARI-25860] - Ambari Metrics GA > h2. Improvement > * [AMBARI-25811] - Optimize ambari metrics build time > * [AMBARI-25825] - Adjust Ambari metrics dependency > * [AMBARI-25840] - Optimized rpm packaging for the Ambari-Metric-Collector > * [AMBARI-25867] - Introduce CI build for Ambari Metrics > h2. Task > * [AMBARI-21079] - Add ability to sink Raw metrics to external system via > Http > * [AMBARI-22688] - Fix AMS compilation issues and unit test with > hbase,hadoop and phoenix upgraded > * [AMBARI-22744] - Fix issues with webapp deployment with new Hadoop common > changes > * [AMBARI-24738] - Update grafana datasource to get values from new object > * [AMBARI-25801] - Make the version for Kafka,Hbase,Hadoop to be consistent > with Ambari > * [AMBARI-25815] - upgrade gson-2.2.2.jar to 2.9.0 > * [AMBARI-25830] - Upgrade AMS Grafana version to 9.3.2 > * [AMBARI-25875] - Use separate property for release version for Ambari > Metrics > * [AMBARI-25876] - Define next version number for Ambari Metrics -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25881) Ambari Metrics 3.0.0 Release
[ https://issues.apache.org/jira/browse/AMBARI-25881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25881: --- Summary: Ambari Metrics 3.0.0 Release (was: Release Ambari Metrics 3.0.0) > Ambari Metrics 3.0.0 Release > > > Key: AMBARI-25881 > URL: https://issues.apache.org/jira/browse/AMBARI-25881 > Project: Ambari > Issue Type: Documentation >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Labels: release-note > > h1. Release Notes: > h2. Bug > * [AMBARI-17382] - Migrate AMS queries to use ROW_TIMESTAMP instead of > native timerange hint > * [AMBARI-21214] - Use a uuid vs long row key for metrics in AMS schema > * [AMBARI-24665] - Migrating grafana plugin for 5.x use > * [AMBARI-24688] - Backend changes for the newer version of AMS Grafana. > * [AMBARI-24884] - AMS Grafana query editor panel does not work in upgraded > version. > * [AMBARI-24898] - Add cluster drop down to Grafana aggregate dashboards. > * [AMBARI-25780] - Ambari metrics should upgrade hadoop and hbase for known > CVE issues > * [AMBARI-25782] - Fix Ambari Metrics build failure > * [AMBARI-25808] - Metrics data simulator throws NPE > * [AMBARI-25809] - ambari-metrics-host-monitoring project build creates temp > folder outside of target folder > * [AMBARI-25810] - Allow skipping Python unit tests in ambari-metrics > * [AMBARI-25819] - Ambari Metrics build fails when using -Dbuild-rpm > * [AMBARI-25821] - Fixed syntax error that caused OOM in the > ambari-metrics-collector > * [AMBARI-25822] - Remove invalid relocations in pom.xml for > ambari-metrics-common > * [AMBARI-25828] - Switch class Metrics to KafkaYammerMetrics on Ambari > Metrics > * [AMBARI-25834] - Fix syntax errors for ambari-metrics-collector > * [AMBARI-25859] - Correct Ambari Metrics version parsing logic > * [AMBARI-25864] - Fix an unit test failure on ambari-metrics-common > * [AMBARI-25865] - Fix an unit test failure on ambari-metrics-host-monitoring > * [AMBARI-25866] - Fix an unit test failure on ambari-metrics-kafka-sink > h2. Epic > * [AMBARI-20773] - AMS: Schema changes for nextGen feature support > * [AMBARI-22745] - Migrate AMS from HBase 1.1.2 to HBase 2.0 > * [AMBARI-23466] - Upgrade AMS Grafana version to 9.3.2 > * [AMBARI-25860] - Ambari Metrics GA > h2. Improvement > * [AMBARI-25811] - Optimize ambari metrics build time > * [AMBARI-25825] - Adjust Ambari metrics dependency > * [AMBARI-25840] - Optimized rpm packaging for the Ambari-Metric-Collector > * [AMBARI-25867] - Introduce CI build for Ambari Metrics > h2. Task > * [AMBARI-21079] - Add ability to sink Raw metrics to external system via > Http > * [AMBARI-22688] - Fix AMS compilation issues and unit test with > hbase,hadoop and phoenix upgraded > * [AMBARI-22744] - Fix issues with webapp deployment with new Hadoop common > changes > * [AMBARI-24738] - Update grafana datasource to get values from new object > * [AMBARI-25801] - Make the version for Kafka,Hbase,Hadoop to be consistent > with Ambari > * [AMBARI-25815] - upgrade gson-2.2.2.jar to 2.9.0 > * [AMBARI-25830] - Upgrade AMS Grafana version to 9.3.2 > * [AMBARI-25875] - Use separate property for release version for Ambari > Metrics > * [AMBARI-25876] - Define next version number for Ambari Metrics -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25881) Release Ambari Metrics 3.0.0
[ https://issues.apache.org/jira/browse/AMBARI-25881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25881: --- Issue Type: Documentation (was: Task) > Release Ambari Metrics 3.0.0 > > > Key: AMBARI-25881 > URL: https://issues.apache.org/jira/browse/AMBARI-25881 > Project: Ambari > Issue Type: Documentation >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Labels: release-note > > h1. Release Notes: > h2. Bug > * [AMBARI-17382] - Migrate AMS queries to use ROW_TIMESTAMP instead of > native timerange hint > * [AMBARI-21214] - Use a uuid vs long row key for metrics in AMS schema > * [AMBARI-24665] - Migrating grafana plugin for 5.x use > * [AMBARI-24688] - Backend changes for the newer version of AMS Grafana. > * [AMBARI-24884] - AMS Grafana query editor panel does not work in upgraded > version. > * [AMBARI-24898] - Add cluster drop down to Grafana aggregate dashboards. > * [AMBARI-25780] - Ambari metrics should upgrade hadoop and hbase for known > CVE issues > * [AMBARI-25782] - Fix Ambari Metrics build failure > * [AMBARI-25808] - Metrics data simulator throws NPE > * [AMBARI-25809] - ambari-metrics-host-monitoring project build creates temp > folder outside of target folder > * [AMBARI-25810] - Allow skipping Python unit tests in ambari-metrics > * [AMBARI-25819] - Ambari Metrics build fails when using -Dbuild-rpm > * [AMBARI-25821] - Fixed syntax error that caused OOM in the > ambari-metrics-collector > * [AMBARI-25822] - Remove invalid relocations in pom.xml for > ambari-metrics-common > * [AMBARI-25828] - Switch class Metrics to KafkaYammerMetrics on Ambari > Metrics > * [AMBARI-25834] - Fix syntax errors for ambari-metrics-collector > * [AMBARI-25859] - Correct Ambari Metrics version parsing logic > * [AMBARI-25864] - Fix an unit test failure on ambari-metrics-common > * [AMBARI-25865] - Fix an unit test failure on ambari-metrics-host-monitoring > * [AMBARI-25866] - Fix an unit test failure on ambari-metrics-kafka-sink > h2. Epic > * [AMBARI-20773] - AMS: Schema changes for nextGen feature support > * [AMBARI-22745] - Migrate AMS from HBase 1.1.2 to HBase 2.0 > * [AMBARI-23466] - Upgrade AMS Grafana version to 9.3.2 > * [AMBARI-25860] - Ambari Metrics GA > h2. Improvement > * [AMBARI-25811] - Optimize ambari metrics build time > * [AMBARI-25825] - Adjust Ambari metrics dependency > * [AMBARI-25840] - Optimized rpm packaging for the Ambari-Metric-Collector > * [AMBARI-25867] - Introduce CI build for Ambari Metrics > h2. Task > * [AMBARI-21079] - Add ability to sink Raw metrics to external system via > Http > * [AMBARI-22688] - Fix AMS compilation issues and unit test with > hbase,hadoop and phoenix upgraded > * [AMBARI-22744] - Fix issues with webapp deployment with new Hadoop common > changes > * [AMBARI-24738] - Update grafana datasource to get values from new object > * [AMBARI-25801] - Make the version for Kafka,Hbase,Hadoop to be consistent > with Ambari > * [AMBARI-25815] - upgrade gson-2.2.2.jar to 2.9.0 > * [AMBARI-25830] - Upgrade AMS Grafana version to 9.3.2 > * [AMBARI-25875] - Use separate property for release version for Ambari > Metrics > * [AMBARI-25876] - Define next version number for Ambari Metrics -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25881) Release Ambari Metrics 3.0.0
[ https://issues.apache.org/jira/browse/AMBARI-25881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25881: --- Labels: release-note (was: ) > Release Ambari Metrics 3.0.0 > > > Key: AMBARI-25881 > URL: https://issues.apache.org/jira/browse/AMBARI-25881 > Project: Ambari > Issue Type: Task >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Labels: release-note > > h1. Release Notes: > h2. Bug > * [AMBARI-17382] - Migrate AMS queries to use ROW_TIMESTAMP instead of > native timerange hint > * [AMBARI-21214] - Use a uuid vs long row key for metrics in AMS schema > * [AMBARI-24665] - Migrating grafana plugin for 5.x use > * [AMBARI-24688] - Backend changes for the newer version of AMS Grafana. > * [AMBARI-24884] - AMS Grafana query editor panel does not work in upgraded > version. > * [AMBARI-24898] - Add cluster drop down to Grafana aggregate dashboards. > * [AMBARI-25780] - Ambari metrics should upgrade hadoop and hbase for known > CVE issues > * [AMBARI-25782] - Fix Ambari Metrics build failure > * [AMBARI-25808] - Metrics data simulator throws NPE > * [AMBARI-25809] - ambari-metrics-host-monitoring project build creates temp > folder outside of target folder > * [AMBARI-25810] - Allow skipping Python unit tests in ambari-metrics > * [AMBARI-25819] - Ambari Metrics build fails when using -Dbuild-rpm > * [AMBARI-25821] - Fixed syntax error that caused OOM in the > ambari-metrics-collector > * [AMBARI-25822] - Remove invalid relocations in pom.xml for > ambari-metrics-common > * [AMBARI-25828] - Switch class Metrics to KafkaYammerMetrics on Ambari > Metrics > * [AMBARI-25834] - Fix syntax errors for ambari-metrics-collector > * [AMBARI-25859] - Correct Ambari Metrics version parsing logic > * [AMBARI-25864] - Fix an unit test failure on ambari-metrics-common > * [AMBARI-25865] - Fix an unit test failure on ambari-metrics-host-monitoring > * [AMBARI-25866] - Fix an unit test failure on ambari-metrics-kafka-sink > h2. Epic > * [AMBARI-20773] - AMS: Schema changes for nextGen feature support > * [AMBARI-22745] - Migrate AMS from HBase 1.1.2 to HBase 2.0 > * [AMBARI-23466] - Upgrade AMS Grafana version to 9.3.2 > * [AMBARI-25860] - Ambari Metrics GA > h2. Improvement > * [AMBARI-25811] - Optimize ambari metrics build time > * [AMBARI-25825] - Adjust Ambari metrics dependency > * [AMBARI-25840] - Optimized rpm packaging for the Ambari-Metric-Collector > * [AMBARI-25867] - Introduce CI build for Ambari Metrics > h2. Task > * [AMBARI-21079] - Add ability to sink Raw metrics to external system via > Http > * [AMBARI-22688] - Fix AMS compilation issues and unit test with > hbase,hadoop and phoenix upgraded > * [AMBARI-22744] - Fix issues with webapp deployment with new Hadoop common > changes > * [AMBARI-24738] - Update grafana datasource to get values from new object > * [AMBARI-25801] - Make the version for Kafka,Hbase,Hadoop to be consistent > with Ambari > * [AMBARI-25815] - upgrade gson-2.2.2.jar to 2.9.0 > * [AMBARI-25830] - Upgrade AMS Grafana version to 9.3.2 > * [AMBARI-25875] - Use separate property for release version for Ambari > Metrics > * [AMBARI-25876] - Define next version number for Ambari Metrics -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25881) Release Ambari Metrics 3.0.0
[ https://issues.apache.org/jira/browse/AMBARI-25881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25881: --- Description: h1. Release Notes: h2. Bug * [AMBARI-17382] - Migrate AMS queries to use ROW_TIMESTAMP instead of native timerange hint * [AMBARI-21214] - Use a uuid vs long row key for metrics in AMS schema * [AMBARI-24665] - Migrating grafana plugin for 5.x use * [AMBARI-24688] - Backend changes for the newer version of AMS Grafana. * [AMBARI-24884] - AMS Grafana query editor panel does not work in upgraded version. * [AMBARI-24898] - Add cluster drop down to Grafana aggregate dashboards. * [AMBARI-25780] - Ambari metrics should upgrade hadoop and hbase for known CVE issues * [AMBARI-25782] - Fix Ambari Metrics build failure * [AMBARI-25808] - Metrics data simulator throws NPE * [AMBARI-25809] - ambari-metrics-host-monitoring project build creates temp folder outside of target folder * [AMBARI-25810] - Allow skipping Python unit tests in ambari-metrics * [AMBARI-25819] - Ambari Metrics build fails when using -Dbuild-rpm * [AMBARI-25821] - Fixed syntax error that caused OOM in the ambari-metrics-collector * [AMBARI-25822] - Remove invalid relocations in pom.xml for ambari-metrics-common * [AMBARI-25828] - Switch class Metrics to KafkaYammerMetrics on Ambari Metrics * [AMBARI-25834] - Fix syntax errors for ambari-metrics-collector * [AMBARI-25859] - Correct Ambari Metrics version parsing logic * [AMBARI-25864] - Fix an unit test failure on ambari-metrics-common * [AMBARI-25865] - Fix an unit test failure on ambari-metrics-host-monitoring * [AMBARI-25866] - Fix an unit test failure on ambari-metrics-kafka-sink h2. Epic * [AMBARI-20773] - AMS: Schema changes for nextGen feature support * [AMBARI-22745] - Migrate AMS from HBase 1.1.2 to HBase 2.0 * [AMBARI-23466] - Upgrade AMS Grafana version to 9.3.2 * [AMBARI-25860] - Ambari Metrics GA h2. Improvement * [AMBARI-25811] - Optimize ambari metrics build time * [AMBARI-25825] - Adjust Ambari metrics dependency * [AMBARI-25840] - Optimized rpm packaging for the Ambari-Metric-Collector * [AMBARI-25867] - Introduce CI build for Ambari Metrics h2. Task * [AMBARI-21079] - Add ability to sink Raw metrics to external system via Http * [AMBARI-22688] - Fix AMS compilation issues and unit test with hbase,hadoop and phoenix upgraded * [AMBARI-22744] - Fix issues with webapp deployment with new Hadoop common changes * [AMBARI-24738] - Update grafana datasource to get values from new object * [AMBARI-25801] - Make the version for Kafka,Hbase,Hadoop to be consistent with Ambari * [AMBARI-25815] - upgrade gson-2.2.2.jar to 2.9.0 * [AMBARI-25830] - Upgrade AMS Grafana version to 9.3.2 * [AMBARI-25875] - Use separate property for release version for Ambari Metrics * [AMBARI-25876] - Define next version number for Ambari Metrics was: h1. Release Notes: h2. Bug * [AMBARI-24665] - Migrating grafana plugin for 5.x use * [AMBARI-24688] - Backend changes for the newer version of AMS Grafana. * [AMBARI-24884] - AMS Grafana query editor panel does not work in upgraded version. * [AMBARI-24898] - Add cluster drop down to Grafana aggregate dashboards. * [AMBARI-25780] - Ambari metrics should upgrade hadoop and hbase for known CVE issues * [AMBARI-25782] - Fix Ambari Metrics build failure * [AMBARI-25808] - Metrics data simulator throws NPE * [AMBARI-25809] - ambari-metrics-host-monitoring project build creates temp folder outside of target folder * [AMBARI-25810] - Allow skipping Python unit tests in ambari-metrics * [AMBARI-25819] - Ambari Metrics build fails when using -Dbuild-rpm * [AMBARI-25821] - Fixed syntax error that caused OOM in the ambari-metrics-collector * [AMBARI-25822] - Remove invalid relocations in pom.xml for ambari-metrics-common * [AMBARI-25828] - Switch class Metrics to KafkaYammerMetrics on Ambari Metrics * [AMBARI-25834] - Fix syntax errors for ambari-metrics-collector * [AMBARI-25859] - Correct Ambari Metrics version parsing logic * [AMBARI-25864] - Fix an unit test failure on ambari-metrics-common * [AMBARI-25865] - Fix an unit test failure on ambari-metrics-host-monitoring * [AMBARI-25866] - Fix an unit test failure on ambari-metrics-kafka-sink h2. Epic * [AMBARI-22745] - Migrate AMS from HBase 1.1.2 to HBase 2.0 * [AMBARI-23466] - Upgrade AMS Grafana version to 9.3.2 * [AMBARI-25860] - Ambari Metrics GA h2. Improvement * [AMBARI-25811] - Optimize ambari metrics build time * [AMBARI-25825] - Adjust Ambari metrics dependency * [AMBARI-25840] - Optimized rpm packaging for the Ambari-Metric-Collector * [AMBARI-25867] - Introduce CI build for Ambari Metrics h2. Task * [AMBARI-22688] - Fix AMS compilation issues and unit test with hbase,hadoop and phoenix upgraded * [AMBARI-22744] - Fix issues with webapp deployment with new Hadoop common changes * [AMBARI-24738] - Update grafana
[jira] [Updated] (AMBARI-21079) Add ability to sink Raw metrics to external system via Http
[ https://issues.apache.org/jira/browse/AMBARI-21079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-21079: --- Fix Version/s: metrics-3.0.0 (was: 3.0.0) (was: branch-3.0-ams) > Add ability to sink Raw metrics to external system via Http > --- > > Key: AMBARI-21079 > URL: https://issues.apache.org/jira/browse/AMBARI-21079 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Major > Fix For: metrics-3.0.0 > > Attachments: AMBARI-21079.patch > > > - Define interface to add MetricsSources to AMS > - Define sink interfaces > - Add caching layer to allow flush interval to be different from sink > interval. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-20773) AMS: Schema changes for nextGen feature support
[ https://issues.apache.org/jira/browse/AMBARI-20773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-20773: --- Fix Version/s: metrics-3.0.0 (was: 3.0.0) > AMS: Schema changes for nextGen feature support > --- > > Key: AMBARI-20773 > URL: https://issues.apache.org/jira/browse/AMBARI-20773 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: metrics-3.0.0 > > > Presently, AMS stores (metricName, hostname, serverTime, appId, instanceId) > for every row. > Although this makes SQL query easy to write, it adds duplication when storing > it in the Regions memory. > This epic is used to track the investigation and implementation of a unique > integer ID for an application-instance metric on a host and use that as a > lookup table with a write through cache when inserting or reading data in the > METRIC_RECORD table. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-20773) AMS: Schema changes for nextGen feature support
[ https://issues.apache.org/jira/browse/AMBARI-20773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-20773: --- Affects Version/s: metrics-3.0.0 (was: 3.0.0) > AMS: Schema changes for nextGen feature support > --- > > Key: AMBARI-20773 > URL: https://issues.apache.org/jira/browse/AMBARI-20773 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 3.0.0 > > > Presently, AMS stores (metricName, hostname, serverTime, appId, instanceId) > for every row. > Although this makes SQL query easy to write, it adds duplication when storing > it in the Regions memory. > This epic is used to track the investigation and implementation of a unique > integer ID for an application-instance metric on a host and use that as a > lookup table with a write through cache when inserting or reading data in the > METRIC_RECORD table. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-21214) Use a uuid vs long row key for metrics in AMS schema
[ https://issues.apache.org/jira/browse/AMBARI-21214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-21214: --- Affects Version/s: (was: 3.0.0) > Use a uuid vs long row key for metrics in AMS schema > > > Key: AMBARI-21214 > URL: https://issues.apache.org/jira/browse/AMBARI-21214 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-21214.patch > > > Presently we store (metircName, hostname, serverTime, appId, instanceId) for > every row. > Although this makes SQL query easy to write, it adds duplication when storing > it in the Regions memory. > We should have a unique integer ID for an application-instance metric on a > host and use that as a lookup table with a write through cache when inserting > or reading data in the METRIC_RECORD table. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-21214) Use a uuid vs long row key for metrics in AMS schema
[ https://issues.apache.org/jira/browse/AMBARI-21214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-21214: --- Fix Version/s: metrics-3.0.0 (was: 3.0.0) > Use a uuid vs long row key for metrics in AMS schema > > > Key: AMBARI-21214 > URL: https://issues.apache.org/jira/browse/AMBARI-21214 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Fix For: metrics-3.0.0 > > Attachments: AMBARI-21214.patch > > > Presently we store (metircName, hostname, serverTime, appId, instanceId) for > every row. > Although this makes SQL query easy to write, it adds duplication when storing > it in the Regions memory. > We should have a unique integer ID for an application-instance metric on a > host and use that as a lookup table with a write through cache when inserting > or reading data in the METRIC_RECORD table. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-17382) Migrate AMS queries to use ROW_TIMESTAMP instead of native timerange hint
[
https://issues.apache.org/jira/browse/AMBARI-17382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-17382:
---
Fix Version/s: metrics-3.0.0
(was: 3.0.0)
> Migrate AMS queries to use ROW_TIMESTAMP instead of native timerange hint
> -
>
> Key: AMBARI-17382
> URL: https://issues.apache.org/jira/browse/AMBARI-17382
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Labels: ambari-metrics
> Fix For: metrics-3.0.0
>
> Attachments: AMBARI-17382-1.patch
>
>
> With PHOENIX-914, there is a change in implementation , As earlier, timestamp
> range was passed as a hint to the query to get advantage of native timerange
> optimization in hbase but with new implementation we can mark the timestamp
> column in the schema as a ROW_TIMESTAMP and pass timestamp range with “where”
> clause only to achieve equivalent performance and better accuracy.
> For eq:-
> With earlier implementation , AMS forms query like this:-
> SELECT /*+ NATIVE_TIME_RANGE(1448029523000) */ METRIC_NAME, APP_ID,
> INSTANCE_ID, SERVER_TIME, UNITS, METRIC_SUM, HOSTS_COUNT, METRIC_MAX,
> METRIC_MIN FROM METRIC_AGGREGATE WHERE (METRIC_NAME IN
> ('regionserver.Server.totalRequestCount',
> 'regionserver.Server.blockCacheCountHitPercent',
> 'regionserver.Server.regionCount',
> 'regionserver.Server.compactionQueueLength',
> 'regionserver.Server.storeFileCount', 'master.Server.averageLoad')) AND
> APP_ID = 'ams-hbase' AND SERVER_TIME >= 1448029643000 AND SERVER_TIME <
> 1448033243 ORDER BY METRIC_NAME, SERVER_TIME LIMIT 11520
> But with PHOENIX-914 :-
> Declare SERVER_TIME as ROW_TIMESTAMP in schema:-
> CREATE TABLE DESTINATION_METRICS_TABLE (SERVER_TIME DATE not null, METRIC_ID
> CHAR(15) not null, METRIC_VALUE bigint … CONSTRAINT PK PRIMARY
> KEY(CREATED_DATE ROW_TIMESTAMP, METRIC_ID…)) …;
> And remove hint from the query:-
> SELECT METRIC_NAME, APP_ID, INSTANCE_ID, SERVER_TIME, UNITS, METRIC_SUM,
> HOSTS_COUNT, METRIC_MAX, METRIC_MIN FROM METRIC_AGGREGATE WHERE (METRIC_NAME
> IN ('regionserver.Server.totalRequestCount',
> 'regionserver.Server.blockCacheCountHitPercent',
> 'regionserver.Server.regionCount',
> 'regionserver.Server.compactionQueueLength',
> 'regionserver.Server.storeFileCount', 'master.Server.averageLoad')) AND
> APP_ID = 'ams-hbase' AND SERVER_TIME >= 1448029643000 AND SERVER_TIME <
> 1448033243 ORDER BY METRIC_NAME, SERVER_TIME LIMIT 11520
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25881) Release Ambari Metrics 3.0.0
[ https://issues.apache.org/jira/browse/AMBARI-25881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25881: --- Description: h1. Release Notes: h2. Bug * [AMBARI-24665] - Migrating grafana plugin for 5.x use * [AMBARI-24688] - Backend changes for the newer version of AMS Grafana. * [AMBARI-24884] - AMS Grafana query editor panel does not work in upgraded version. * [AMBARI-24898] - Add cluster drop down to Grafana aggregate dashboards. * [AMBARI-25780] - Ambari metrics should upgrade hadoop and hbase for known CVE issues * [AMBARI-25782] - Fix Ambari Metrics build failure * [AMBARI-25808] - Metrics data simulator throws NPE * [AMBARI-25809] - ambari-metrics-host-monitoring project build creates temp folder outside of target folder * [AMBARI-25810] - Allow skipping Python unit tests in ambari-metrics * [AMBARI-25819] - Ambari Metrics build fails when using -Dbuild-rpm * [AMBARI-25821] - Fixed syntax error that caused OOM in the ambari-metrics-collector * [AMBARI-25822] - Remove invalid relocations in pom.xml for ambari-metrics-common * [AMBARI-25828] - Switch class Metrics to KafkaYammerMetrics on Ambari Metrics * [AMBARI-25834] - Fix syntax errors for ambari-metrics-collector * [AMBARI-25859] - Correct Ambari Metrics version parsing logic * [AMBARI-25864] - Fix an unit test failure on ambari-metrics-common * [AMBARI-25865] - Fix an unit test failure on ambari-metrics-host-monitoring * [AMBARI-25866] - Fix an unit test failure on ambari-metrics-kafka-sink h2. Epic * [AMBARI-22745] - Migrate AMS from HBase 1.1.2 to HBase 2.0 * [AMBARI-23466] - Upgrade AMS Grafana version to 9.3.2 * [AMBARI-25860] - Ambari Metrics GA h2. Improvement * [AMBARI-25811] - Optimize ambari metrics build time * [AMBARI-25825] - Adjust Ambari metrics dependency * [AMBARI-25840] - Optimized rpm packaging for the Ambari-Metric-Collector * [AMBARI-25867] - Introduce CI build for Ambari Metrics h2. Task * [AMBARI-22688] - Fix AMS compilation issues and unit test with hbase,hadoop and phoenix upgraded * [AMBARI-22744] - Fix issues with webapp deployment with new Hadoop common changes * [AMBARI-24738] - Update grafana datasource to get values from new object * [AMBARI-25801] - Make the version for Kafka,Hbase,Hadoop to be consistent with Ambari * [AMBARI-25815] - upgrade gson-2.2.2.jar to 2.9.0 * [AMBARI-25830] - Upgrade AMS Grafana version to 9.3.2 * [AMBARI-25875] - Use separate property for release version for Ambari Metrics * [AMBARI-25876] - Define next version number for Ambari Metrics > Release Ambari Metrics 3.0.0 > > > Key: AMBARI-25881 > URL: https://issues.apache.org/jira/browse/AMBARI-25881 > Project: Ambari > Issue Type: Task >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > > h1. Release Notes: > h2. Bug > * [AMBARI-24665] - Migrating grafana plugin for 5.x use > * [AMBARI-24688] - Backend changes for the newer version of AMS Grafana. > * [AMBARI-24884] - AMS Grafana query editor panel does not work in upgraded > version. > * [AMBARI-24898] - Add cluster drop down to Grafana aggregate dashboards. > * [AMBARI-25780] - Ambari metrics should upgrade hadoop and hbase for known > CVE issues > * [AMBARI-25782] - Fix Ambari Metrics build failure > * [AMBARI-25808] - Metrics data simulator throws NPE > * [AMBARI-25809] - ambari-metrics-host-monitoring project build creates temp > folder outside of target folder > * [AMBARI-25810] - Allow skipping Python unit tests in ambari-metrics > * [AMBARI-25819] - Ambari Metrics build fails when using -Dbuild-rpm > * [AMBARI-25821] - Fixed syntax error that caused OOM in the > ambari-metrics-collector > * [AMBARI-25822] - Remove invalid relocations in pom.xml for > ambari-metrics-common > * [AMBARI-25828] - Switch class Metrics to KafkaYammerMetrics on Ambari > Metrics > * [AMBARI-25834] - Fix syntax errors for ambari-metrics-collector > * [AMBARI-25859] - Correct Ambari Metrics version parsing logic > * [AMBARI-25864] - Fix an unit test failure on ambari-metrics-common > * [AMBARI-25865] - Fix an unit test failure on ambari-metrics-host-monitoring > * [AMBARI-25866] - Fix an unit test failure on ambari-metrics-kafka-sink > h2. Epic > * [AMBARI-22745] - Migrate AMS from HBase 1.1.2 to HBase 2.0 > * [AMBARI-23466] - Upgrade AMS Grafana version to 9.3.2 > * [AMBARI-25860] - Ambari Metrics GA > h2. Improvement > * [AMBARI-25811] - Optimize ambari metrics build time > * [AMBARI-25825] - Adjust Ambari metrics dependency > * [AMBARI-25840] - Optimized rpm packaging for the Ambari-Metric-Collector > * [AMBARI-25867] - Introduce CI build for Ambari Metrics > h2. Task > * [AMBARI-22688] - Fix AMS compilation issues and unit test with > hbase,hadoop and phoenix upgraded > * [AMBARI-22744] - Fix issues with webapp
[jira] [Updated] (AMBARI-25815) upgrade gson-2.2.2.jar to 2.9.0
[ https://issues.apache.org/jira/browse/AMBARI-25815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25815: --- Issue Type: Task (was: Story) > upgrade gson-2.2.2.jar to 2.9.0 > --- > > Key: AMBARI-25815 > URL: https://issues.apache.org/jira/browse/AMBARI-25815 > Project: Ambari > Issue Type: Task >Reporter: Ananya Singh >Assignee: Ananya Singh >Priority: Major > Labels: pull-request-available > Fix For: metrics-3.0.0 > > > |[CVE-2022-25647 > |http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-25647]| > upgrade gson in ambari-metrics. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-22744) Fix issues with webapp deployment with new Hadoop common changes
[ https://issues.apache.org/jira/browse/AMBARI-22744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-22744: --- Affects Version/s: (was: 3.0.0) > Fix issues with webapp deployment with new Hadoop common changes > > > Key: AMBARI-22744 > URL: https://issues.apache.org/jira/browse/AMBARI-22744 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22744.patch > > > - Fix deploy time issues after migration. > - Fix imports. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-22744) Fix issues with webapp deployment with new Hadoop common changes
[ https://issues.apache.org/jira/browse/AMBARI-22744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-22744: --- Fix Version/s: metrics-3.0.0 (was: 3.0.0) > Fix issues with webapp deployment with new Hadoop common changes > > > Key: AMBARI-22744 > URL: https://issues.apache.org/jira/browse/AMBARI-22744 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: metrics-3.0.0 > > Attachments: AMBARI-22744.patch > > > - Fix deploy time issues after migration. > - Fix imports. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-22745) Migrate AMS from HBase 1.1.2 to HBase 2.0
[ https://issues.apache.org/jira/browse/AMBARI-22745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-22745: --- Fix Version/s: metrics-3.0.0 (was: 2.8.0) > Migrate AMS from HBase 1.1.2 to HBase 2.0 > - > > Key: AMBARI-22745 > URL: https://issues.apache.org/jira/browse/AMBARI-22745 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: metrics-3.0.0 > > > As part of the move towards HDP 3, we'll be upgrading HBase from 1.1.2 to > HBase 2.0. > This task is used to track the work necessary to make Ambari metric services > compile and run against HBase 2.0. > All underlying system integration tests and unit tests should also be running > against HBase 2.0. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-22688) Fix AMS compilation issues and unit test with hbase,hadoop and phoenix upgraded
[ https://issues.apache.org/jira/browse/AMBARI-22688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-22688: --- Fix Version/s: metrics-3.0.0 (was: branch-3.0-ams) > Fix AMS compilation issues and unit test with hbase,hadoop and phoenix > upgraded > --- > > Key: AMBARI-22688 > URL: https://issues.apache.org/jira/browse/AMBARI-22688 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Major > Fix For: metrics-3.0.0 > > Attachments: AMBARI-22688.patch > > > - Build AMS with HBase 2.0 and fix resulting compilation problems and unit > tests. > - Also removed a bunch of unused code from YARN ATS > - Fix compatibility issues with new HBaseAdmin -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-22745) Migrate AMS from HBase 1.1.2 to HBase 2.0
[ https://issues.apache.org/jira/browse/AMBARI-22745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-22745: --- Affects Version/s: metrics-3.0.0 (was: 2.8.0) > Migrate AMS from HBase 1.1.2 to HBase 2.0 > - > > Key: AMBARI-22745 > URL: https://issues.apache.org/jira/browse/AMBARI-22745 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.8.0 > > > As part of the move towards HDP 3, we'll be upgrading HBase from 1.1.2 to > HBase 2.0. > This task is used to track the work necessary to make Ambari metric services > compile and run against HBase 2.0. > All underlying system integration tests and unit tests should also be running > against HBase 2.0. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-24884) AMS Grafana query editor panel does not work in upgraded version.
[ https://issues.apache.org/jira/browse/AMBARI-24884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-24884: --- Fix Version/s: metrics-3.0.0 (was: 2.8.0) > AMS Grafana query editor panel does not work in upgraded version. > - > > Key: AMBARI-24884 > URL: https://issues.apache.org/jira/browse/AMBARI-24884 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: metrics-3.0.0 > > > Following issues are encountered > - Dropdown list not appearing. > - Metrics not automatically refreshed > - Error on collapsing a metric. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-24898) Add cluster drop down to Grafana aggregate dashboards.
[ https://issues.apache.org/jira/browse/AMBARI-24898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-24898: --- Fix Version/s: metrics-3.0.0 (was: 2.8.0) > Add cluster drop down to Grafana aggregate dashboards. > -- > > Key: AMBARI-24898 > URL: https://issues.apache.org/jira/browse/AMBARI-24898 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: metrics-3.0.0 > > > Currently, the HOST based dashboards (System-Servers, HDFS Namenodes, > HBase-Regionservers etc) have a dropdown for the cluster level selection. > This selection determines the set of hosts in the HOST dropdown, and the > cluster is tagged in the API call made by every graph in the dashboard > through the "instanceId" query parameter. > We need to add the cluster dropdown to aggregate dashboards as well. This > cluster selection will also be tagged in the API call (instanceId) like in > other dashboards. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-24688) Backend changes for the newer version of AMS Grafana.
[ https://issues.apache.org/jira/browse/AMBARI-24688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-24688: --- Fix Version/s: metrics-3.0.0 (was: 2.8.0) > Backend changes for the newer version of AMS Grafana. > - > > Key: AMBARI-24688 > URL: https://issues.apache.org/jira/browse/AMBARI-24688 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: metrics-3.0.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-24738) Update grafana datasource to get values from new object
[ https://issues.apache.org/jira/browse/AMBARI-24738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-24738: --- Fix Version/s: metrics-3.0.0 (was: 2.8.0) > Update grafana datasource to get values from new object > --- > > Key: AMBARI-24738 > URL: https://issues.apache.org/jira/browse/AMBARI-24738 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: metrics-3.0.0 > > > In the new grafana version templateSrv doesn't have some fields. We need to > get these values from a different fields -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-24665) Migrating grafana plugin for 5.x use
[ https://issues.apache.org/jira/browse/AMBARI-24665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-24665: --- Fix Version/s: metrics-3.0.0 (was: 3.0.0) > Migrating grafana plugin for 5.x use > > > Key: AMBARI-24665 > URL: https://issues.apache.org/jira/browse/AMBARI-24665 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: metrics-3.0.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-24688) Backend changes for the newer version of AMS Grafana.
[ https://issues.apache.org/jira/browse/AMBARI-24688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-24688: --- Affects Version/s: (was: 2.8.0) > Backend changes for the newer version of AMS Grafana. > - > > Key: AMBARI-24688 > URL: https://issues.apache.org/jira/browse/AMBARI-24688 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25830) Upgrade AMS Grafana version to 9.3.2
[ https://issues.apache.org/jira/browse/AMBARI-25830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25830: --- Fix Version/s: metrics-3.0.0 (was: 2.8.0) > Upgrade AMS Grafana version to 9.3.2 > > > Key: AMBARI-25830 > URL: https://issues.apache.org/jira/browse/AMBARI-25830 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: metrics-3.0.0 > > > Upgrade grafana from 6.7.4 to 9.3.2. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25860) Ambari Metrics GA
[ https://issues.apache.org/jira/browse/AMBARI-25860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25860: --- Affects Version/s: metrics-3.0.0 (was: 2.8.0) > Ambari Metrics GA > - > > Key: AMBARI-25860 > URL: https://issues.apache.org/jira/browse/AMBARI-25860 > Project: Ambari > Issue Type: Epic >Affects Versions: metrics-3.0.0 >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Fix For: metrics-3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-23466) Upgrade AMS Grafana version to 9.3.2
[ https://issues.apache.org/jira/browse/AMBARI-23466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu resolved AMBARI-23466. Resolution: Fixed > Upgrade AMS Grafana version to 9.3.2 > > > Key: AMBARI-23466 > URL: https://issues.apache.org/jira/browse/AMBARI-23466 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Aravindan Vijayan >Assignee: lucas >Priority: Critical > Fix For: metrics-3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-23466) Upgrade AMS Grafana version to 9.3.2
[ https://issues.apache.org/jira/browse/AMBARI-23466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-23466: --- Fix Version/s: metrics-3.0.0 (was: 2.8.0) > Upgrade AMS Grafana version to 9.3.2 > > > Key: AMBARI-23466 > URL: https://issues.apache.org/jira/browse/AMBARI-23466 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Aravindan Vijayan >Assignee: lucas >Priority: Critical > Fix For: metrics-3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Resolved] (AMBARI-25860) Ambari Metrics GA
[ https://issues.apache.org/jira/browse/AMBARI-25860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu resolved AMBARI-25860. Resolution: Fixed > Ambari Metrics GA > - > > Key: AMBARI-25860 > URL: https://issues.apache.org/jira/browse/AMBARI-25860 > Project: Ambari > Issue Type: Epic >Affects Versions: metrics-3.0.0 >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Fix For: metrics-3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-23466) Upgrade AMS Grafana version to 9.3.2
[ https://issues.apache.org/jira/browse/AMBARI-23466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-23466: --- Affects Version/s: metrics-3.0.0 > Upgrade AMS Grafana version to 9.3.2 > > > Key: AMBARI-23466 > URL: https://issues.apache.org/jira/browse/AMBARI-23466 > Project: Ambari > Issue Type: Epic > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Aravindan Vijayan >Assignee: lucas >Priority: Critical > Fix For: 2.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25860) Ambari Metrics GA
[ https://issues.apache.org/jira/browse/AMBARI-25860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-25860: --- Fix Version/s: metrics-3.0.0 (was: 2.8.0) > Ambari Metrics GA > - > > Key: AMBARI-25860 > URL: https://issues.apache.org/jira/browse/AMBARI-25860 > Project: Ambari > Issue Type: Epic >Affects Versions: 2.8.0 >Reporter: Zhiguo Wu >Assignee: Zhiguo Wu >Priority: Major > Fix For: metrics-3.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25886) Blueprint fails to select configurations
[
https://issues.apache.org/jira/browse/AMBARI-25886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-25886:
---
Description:
When I'm using blueprint to create a cluster, it fails to select configuration
sometimes
!image-2023-03-09-17-42-54-720.png!
It causes errors when installing services:
{code:java}
result_protected = self.vformat(format_string, args, all_params)
File "/usr/lib64/python2.7/string.py", line 549, in vformat
result = self._vformat(format_string, args, kwargs, used_args, 2)
File "/usr/lib64/python2.7/string.py", line 582, in _vformat
result.append(self.format_field(obj, format_spec))
File "/usr/lib64/python2.7/string.py", line 599, in format_field
return format(value, format_spec)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py",
line 75, in __getattr__
raise Fail("Configuration parameter '" + self.name + "' was not found in
configurations dictionary!")
resource_management.core.exceptions.Fail: Configuration parameter 'hive-env'
was not found in configurations dictionary! {code}
Blueprint document:
https://cwiki.apache.org/confluence/display/AMBARI/Blueprints
was:
When I'm using blueprint to create a cluster, it fails to select configuration
sometimes
!image-2023-03-09-17-42-54-720.png!
It causes errors when installing services:
{code:java}
result_protected = self.vformat(format_string, args, all_params)
File "/usr/lib64/python2.7/string.py", line 549, in vformat
result = self._vformat(format_string, args, kwargs, used_args, 2)
File "/usr/lib64/python2.7/string.py", line 582, in _vformat
result.append(self.format_field(obj, format_spec))
File "/usr/lib64/python2.7/string.py", line 599, in format_field
return format(value, format_spec)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py",
line 75, in __getattr__
raise Fail("Configuration parameter '" + self.name + "' was not found in
configurations dictionary!")
resource_management.core.exceptions.Fail: Configuration parameter 'hive-env'
was not found in configurations dictionary! {code}
> Blueprint fails to select configurations
>
>
> Key: AMBARI-25886
> URL: https://issues.apache.org/jira/browse/AMBARI-25886
> Project: Ambari
> Issue Type: Bug
>Reporter: Zhiguo Wu
>Assignee: Zhiguo Wu
>Priority: Major
> Attachments: image-2023-03-09-17-42-54-720.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When I'm using blueprint to create a cluster, it fails to select
> configuration sometimes
> !image-2023-03-09-17-42-54-720.png!
>
> It causes errors when installing services:
> {code:java}
> result_protected = self.vformat(format_string, args, all_params)
> File "/usr/lib64/python2.7/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
> File "/usr/lib64/python2.7/string.py", line 582, in _vformat
> result.append(self.format_field(obj, format_spec))
> File "/usr/lib64/python2.7/string.py", line 599, in format_field
> return format(value, format_spec)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py",
> line 75, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 'hive-env'
> was not found in configurations dictionary! {code}
>
> Blueprint document:
> https://cwiki.apache.org/confluence/display/AMBARI/Blueprints
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Comment Edited] (AMBARI-25888) component did not advertise a version. This may indicate a problem with the component packaging. However, the stack-select tool was able to report a single versi
[
https://issues.apache.org/jira/browse/AMBARI-25888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17698931#comment-17698931
]
Zhiguo Wu edited comment on AMBARI-25888 at 3/10/23 12:59 PM:
--
[~vivekraghuwanshi]
Ambari Server version should be 3.0.0.0-SNAPSHOT if you build from trunk
branch, we haven't updated it yet.
You can use this url for the repo which is already set as default:
[https://bigtop-snapshot.s3.amazonaws.com/centos-7/$basearch]
RPM packages under bigtop repo are a little different from s3, bigtop packages
follow {*}Linux Filesystem Hierarchy Standard{*}:
[https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html]
But we add some functions to be compatible with Ambari, so you need to use RPMs
provided by Ambari Community
was (Author: JIRAUSER294567):
[~vivekraghuwanshi]
Ambari Server version should be 3.0.0.0-SNAPSHOT if you build from trunk
branch, we haven't updated it yet.
You can use this url for the repo which is already set as default:
[https://bigtop-snapshot.s3.amazonaws.com/centos-7/$basearch]
RPM packages under bigtop repo are a little different from s3, bigtop packages
follow {*}Linux Filesystem Hierarchy Standard{*}:
[https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html|https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html),]
But we add some functions to be compatible with Ambari, so you need to use RPMs
provided by Ambari Community
> component did not advertise a version. This may indicate a problem with the
> component packaging. However, the stack-select tool was able to report a
> single version installed (3.2.0). This is the version that will be report
> --
>
> Key: AMBARI-25888
> URL: https://issues.apache.org/jira/browse/AMBARI-25888
> Project: Ambari
> Issue Type: Bug
> Environment: Centos 7.9
> Python 2.7
>Reporter: ViVek Raghuwanshi
>Priority: Major
>
> stderr:
> 2023-03-09 16:31:58,811 - The 'hadoop-hdfs-namenode' component did not
> advertise a version. This may indicate a problem with the component
> packaging. However, the stack-select tool was able to report a single version
> installed (3.2.0). This is the version that will be reported.
> 2023-03-09 16:32:03,973 - The 'hadoop-hdfs-namenode' component did not
> advertise a version. This may indicate a problem with the component
> packaging. However, the stack-select tool was able to report a single version
> installed (3.2.0). This is the version that will be reported.
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HDFS/package/scripts/namenode.py",
> line 419, in
> NameNode().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 355, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HDFS/package/scripts/namenode.py",
> line 71, in install
> self.install_packages(env)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 876, in install_packages
> name = self.format_package_name(package['name'])
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 569, in format_package_name
> return self.get_package_from_available(name)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 536, in get_package_from_available
> raise Fail("No package found for \{0}(expected name: \{1})".format(name,
> name_with_version))
> resource_management.core.exceptions.Fail: No package found for
> hadoop_${stack_version}(expected name: hadoop_3_2_0)
> stdout:
> 2023-03-09 16:31:58,575 - Stack Feature Version Info: Cluster Stack=3.2.0,
> Command Stack=None, Command Version=None -> 3.2.0
> 2023-03-09 16:31:58,575 - Using hadoop conf dir: /etc/hadoop/conf
> 2023-03-09 16:31:58,577 - Group['hdfs'] {}
> 2023-03-09 16:31:58,578 - Group['hadoop'] {}
> 2023-03-09 16:31:58,578 - User['zookeeper'] \{'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-09 16:31:58,579 - User['ams'] \{'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-09 16:31:58,580 - User['ambari-qa'] \{'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-09 16:31:58,581 - User['hdfs'] \{'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hdfs', 'hadoop'], 'uid': None}
> 2023-03-09 16:31:58,581 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
> \{'content':
[jira] [Commented] (AMBARI-25888) component did not advertise a version. This may indicate a problem with the component packaging. However, the stack-select tool was able to report a single version in
[
https://issues.apache.org/jira/browse/AMBARI-25888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17698931#comment-17698931
]
Zhiguo Wu commented on AMBARI-25888:
[~vivekraghuwanshi]
Ambari Server version should be 3.0.0.0-SNAPSHOT if you build from trunk
branch, we haven't updated it yet.
You can use this url for the repo which is already set as default:
[https://bigtop-snapshot.s3.amazonaws.com/centos-7/$basearch]
RPM packages under bigtop repo are a little different from s3, bigtop packages
follow *Linux Filesystem Hierarchy* Standard:
[https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html|https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html),]
But we add some functions to be compatible with Ambari, so you need to use RPMs
provided by Ambari Community
> component did not advertise a version. This may indicate a problem with the
> component packaging. However, the stack-select tool was able to report a
> single version installed (3.2.0). This is the version that will be report
> --
>
> Key: AMBARI-25888
> URL: https://issues.apache.org/jira/browse/AMBARI-25888
> Project: Ambari
> Issue Type: Bug
> Environment: Centos 7.9
> Python 2.7
>Reporter: ViVek Raghuwanshi
>Priority: Major
>
> stderr:
> 2023-03-09 16:31:58,811 - The 'hadoop-hdfs-namenode' component did not
> advertise a version. This may indicate a problem with the component
> packaging. However, the stack-select tool was able to report a single version
> installed (3.2.0). This is the version that will be reported.
> 2023-03-09 16:32:03,973 - The 'hadoop-hdfs-namenode' component did not
> advertise a version. This may indicate a problem with the component
> packaging. However, the stack-select tool was able to report a single version
> installed (3.2.0). This is the version that will be reported.
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HDFS/package/scripts/namenode.py",
> line 419, in
> NameNode().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 355, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HDFS/package/scripts/namenode.py",
> line 71, in install
> self.install_packages(env)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 876, in install_packages
> name = self.format_package_name(package['name'])
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 569, in format_package_name
> return self.get_package_from_available(name)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 536, in get_package_from_available
> raise Fail("No package found for \{0}(expected name: \{1})".format(name,
> name_with_version))
> resource_management.core.exceptions.Fail: No package found for
> hadoop_${stack_version}(expected name: hadoop_3_2_0)
> stdout:
> 2023-03-09 16:31:58,575 - Stack Feature Version Info: Cluster Stack=3.2.0,
> Command Stack=None, Command Version=None -> 3.2.0
> 2023-03-09 16:31:58,575 - Using hadoop conf dir: /etc/hadoop/conf
> 2023-03-09 16:31:58,577 - Group['hdfs'] {}
> 2023-03-09 16:31:58,578 - Group['hadoop'] {}
> 2023-03-09 16:31:58,578 - User['zookeeper'] \{'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-09 16:31:58,579 - User['ams'] \{'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-09 16:31:58,580 - User['ambari-qa'] \{'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-09 16:31:58,581 - User['hdfs'] \{'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hdfs', 'hadoop'], 'uid': None}
> 2023-03-09 16:31:58,581 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
> \{'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
> 2023-03-09 16:31:58,583 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh
> ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa
> 0'] \{'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}
> 2023-03-09 16:31:58,588 - Skipping
> Execute['/var/lib/ambari-agent/tmp/changeUid.sh ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa
> 0'] due to not_if
> 2023-03-09 16:31:58,589 - Group['hdfs'] {}
> 2023-03-09 16:31:58,589 - User['hdfs'] \{'fetch_nonlocal_groups': True,
> 'groups': ['hdfs', 'hadoop', 'hdfs']}
[jira] [Comment Edited] (AMBARI-25888) component did not advertise a version. This may indicate a problem with the component packaging. However, the stack-select tool was able to report a single versi
[
https://issues.apache.org/jira/browse/AMBARI-25888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17698931#comment-17698931
]
Zhiguo Wu edited comment on AMBARI-25888 at 3/10/23 12:58 PM:
--
[~vivekraghuwanshi]
Ambari Server version should be 3.0.0.0-SNAPSHOT if you build from trunk
branch, we haven't updated it yet.
You can use this url for the repo which is already set as default:
[https://bigtop-snapshot.s3.amazonaws.com/centos-7/$basearch]
RPM packages under bigtop repo are a little different from s3, bigtop packages
follow {*}Linux Filesystem Hierarchy Standard{*}:
[https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html|https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html),]
But we add some functions to be compatible with Ambari, so you need to use RPMs
provided by Ambari Community
was (Author: JIRAUSER294567):
[~vivekraghuwanshi]
Ambari Server version should be 3.0.0.0-SNAPSHOT if you build from trunk
branch, we haven't updated it yet.
You can use this url for the repo which is already set as default:
[https://bigtop-snapshot.s3.amazonaws.com/centos-7/$basearch]
RPM packages under bigtop repo are a little different from s3, bigtop packages
follow *Linux Filesystem Hierarchy* Standard:
[https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html|https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html),]
But we add some functions to be compatible with Ambari, so you need to use RPMs
provided by Ambari Community
> component did not advertise a version. This may indicate a problem with the
> component packaging. However, the stack-select tool was able to report a
> single version installed (3.2.0). This is the version that will be report
> --
>
> Key: AMBARI-25888
> URL: https://issues.apache.org/jira/browse/AMBARI-25888
> Project: Ambari
> Issue Type: Bug
> Environment: Centos 7.9
> Python 2.7
>Reporter: ViVek Raghuwanshi
>Priority: Major
>
> stderr:
> 2023-03-09 16:31:58,811 - The 'hadoop-hdfs-namenode' component did not
> advertise a version. This may indicate a problem with the component
> packaging. However, the stack-select tool was able to report a single version
> installed (3.2.0). This is the version that will be reported.
> 2023-03-09 16:32:03,973 - The 'hadoop-hdfs-namenode' component did not
> advertise a version. This may indicate a problem with the component
> packaging. However, the stack-select tool was able to report a single version
> installed (3.2.0). This is the version that will be reported.
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HDFS/package/scripts/namenode.py",
> line 419, in
> NameNode().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 355, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HDFS/package/scripts/namenode.py",
> line 71, in install
> self.install_packages(env)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 876, in install_packages
> name = self.format_package_name(package['name'])
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 569, in format_package_name
> return self.get_package_from_available(name)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 536, in get_package_from_available
> raise Fail("No package found for \{0}(expected name: \{1})".format(name,
> name_with_version))
> resource_management.core.exceptions.Fail: No package found for
> hadoop_${stack_version}(expected name: hadoop_3_2_0)
> stdout:
> 2023-03-09 16:31:58,575 - Stack Feature Version Info: Cluster Stack=3.2.0,
> Command Stack=None, Command Version=None -> 3.2.0
> 2023-03-09 16:31:58,575 - Using hadoop conf dir: /etc/hadoop/conf
> 2023-03-09 16:31:58,577 - Group['hdfs'] {}
> 2023-03-09 16:31:58,578 - Group['hadoop'] {}
> 2023-03-09 16:31:58,578 - User['zookeeper'] \{'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-09 16:31:58,579 - User['ams'] \{'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-09 16:31:58,580 - User['ambari-qa'] \{'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-09 16:31:58,581 - User['hdfs'] \{'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hdfs', 'hadoop'], 'uid': None}
> 2023-03-09 16:31:58,581 -
[jira] [Commented] (AMBARI-25888) component did not advertise a version. This may indicate a problem with the component packaging. However, the stack-select tool was able to report a single version in
[
https://issues.apache.org/jira/browse/AMBARI-25888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17698693#comment-17698693
]
Zhiguo Wu commented on AMBARI-25888:
Which repository you are using for BIGTOP stack?
> component did not advertise a version. This may indicate a problem with the
> component packaging. However, the stack-select tool was able to report a
> single version installed (3.2.0). This is the version that will be report
> --
>
> Key: AMBARI-25888
> URL: https://issues.apache.org/jira/browse/AMBARI-25888
> Project: Ambari
> Issue Type: Bug
> Environment: Centos 7.9
> Python 2.7
>Reporter: ViVek Raghuwanshi
>Priority: Major
>
> stderr:
> 2023-03-09 16:31:58,811 - The 'hadoop-hdfs-namenode' component did not
> advertise a version. This may indicate a problem with the component
> packaging. However, the stack-select tool was able to report a single version
> installed (3.2.0). This is the version that will be reported.
> 2023-03-09 16:32:03,973 - The 'hadoop-hdfs-namenode' component did not
> advertise a version. This may indicate a problem with the component
> packaging. However, the stack-select tool was able to report a single version
> installed (3.2.0). This is the version that will be reported.
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HDFS/package/scripts/namenode.py",
> line 419, in
> NameNode().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 355, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HDFS/package/scripts/namenode.py",
> line 71, in install
> self.install_packages(env)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 876, in install_packages
> name = self.format_package_name(package['name'])
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 569, in format_package_name
> return self.get_package_from_available(name)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 536, in get_package_from_available
> raise Fail("No package found for \{0}(expected name: \{1})".format(name,
> name_with_version))
> resource_management.core.exceptions.Fail: No package found for
> hadoop_${stack_version}(expected name: hadoop_3_2_0)
> stdout:
> 2023-03-09 16:31:58,575 - Stack Feature Version Info: Cluster Stack=3.2.0,
> Command Stack=None, Command Version=None -> 3.2.0
> 2023-03-09 16:31:58,575 - Using hadoop conf dir: /etc/hadoop/conf
> 2023-03-09 16:31:58,577 - Group['hdfs'] {}
> 2023-03-09 16:31:58,578 - Group['hadoop'] {}
> 2023-03-09 16:31:58,578 - User['zookeeper'] \{'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-09 16:31:58,579 - User['ams'] \{'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-09 16:31:58,580 - User['ambari-qa'] \{'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-09 16:31:58,581 - User['hdfs'] \{'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hdfs', 'hadoop'], 'uid': None}
> 2023-03-09 16:31:58,581 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
> \{'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
> 2023-03-09 16:31:58,583 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh
> ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa
> 0'] \{'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}
> 2023-03-09 16:31:58,588 - Skipping
> Execute['/var/lib/ambari-agent/tmp/changeUid.sh ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa
> 0'] due to not_if
> 2023-03-09 16:31:58,589 - Group['hdfs'] {}
> 2023-03-09 16:31:58,589 - User['hdfs'] \{'fetch_nonlocal_groups': True,
> 'groups': ['hdfs', 'hadoop', 'hdfs']}
> 2023-03-09 16:31:58,590 - FS Type: HDFS
> 2023-03-09 16:31:58,590 - Directory['/etc/hadoop'] \{'mode': 0755}
> 2023-03-09 16:31:58,606 - File['/etc/hadoop/conf/hadoop-env.sh'] \{'content':
> InlineTemplate(...), 'owner': 'hdfs', 'group': 'hadoop'}
> 2023-03-09 16:31:58,607 -
> Directory['/var/lib/ambari-agent/tmp/hadoop_java_io_tmpdir'] \{'owner':
> 'hdfs', 'group': 'hadoop', 'mode': 01777}
> 2023-03-09 16:31:58,619 - Repository for BIGTOP/3.2.0/BIGTOP-3.2.0 is not
> managed by Ambari
> 2023-03-09 16:31:58,619 - Repository[None] \{'action': ['create']}
> 2023-03-09
[jira] [Created] (AMBARI-25887) Blueprint inconsistent import/export logic for database connection url
Zhiguo Wu created AMBARI-25887:
--
Summary: Blueprint inconsistent import/export logic for database
connection url
Key: AMBARI-25887
URL: https://issues.apache.org/jira/browse/AMBARI-25887
Project: Ambari
Issue Type: Bug
Reporter: Zhiguo Wu
Assignee: Zhiguo Wu
Attachments: blueprint-configuration.json,
image-2023-03-09-18-53-14-454.png
When I manually deploy a cluster which contains hive service, and get blueprint
config from the cluster:
!image-2023-03-09-18-53-14-454.png!
then create a new cluster by this config, an error occurs because it cannot
resolve mysql connection url on hive-site configuration
{code:java}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package/scripts/hive_metastore.py",
line 201, in
HiveMetastore().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 355, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package/scripts/hive_metastore.py",
line 61, in start
create_metastore_schema() # execute without config lock
File
"/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package/scripts/hive.py",
line 466, in create_metastore_schema
user = params.hive_user
File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line 166,
in __init__
self.env.run()
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py", line
280, in action_run
returns=self.resource.returns)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 72,
in inner
result = function(command, **kwargs)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 102,
in checked_call
tries=tries, try_sleep=try_sleep,
timeout_kill_strategy=timeout_kill_strategy, returns=returns)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 150,
in _call_wrapper
result = _call(command, **kwargs_copy)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 314,
in _call
raise ExecutionFailed(err_msg, code, out, err)
resource_management.core.exceptions.ExecutionFailed: Execution of 'export
HIVE_CONF_DIR=/etc/hive/conf ; /usr/bigtop/current/hive-client/bin/schematool
-initSchema -dbType mysql -userName hive -passWord [PROTECTED] -verbose'
returned 1. SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/usr/bigtop/3.2.0/usr/lib/hive/lib/log4j-slf4j-impl-2.17.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/usr/bigtop/3.2.0/usr/lib/hadoop/lib/slf4j-reload4j-1.7.36.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
Metastore connection URL:jdbc:mysql://%HOSTGROUP::host_group_1%/hive
Metastore Connection Driver :com.mysql.jdbc.Driver
Metastore connection User: hive
org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema
version.
Underlying cause:
com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException : Cannot
load connection class because of underlying exception:
'java.lang.NumberFormatException: For input string: ":host_group_1%"'.
SQL Error code: 0
org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema
version.
at
org.apache.hadoop.hive.metastore.tools.HiveSchemaHelper.getConnectionToMetastore(HiveSchemaHelper.java:94)
at
org.apache.hive.beeline.HiveSchemaTool.getConnectionToMetastore(HiveSchemaTool.java:169)
at
org.apache.hive.beeline.HiveSchemaTool.testConnectionToMetastore(HiveSchemaTool.java:475)
at
org.apache.hive.beeline.HiveSchemaTool.doInit(HiveSchemaTool.java:581)
at
org.apache.hive.beeline.HiveSchemaTool.doInit(HiveSchemaTool.java:567)
at org.apache.hive.beeline.HiveSchemaTool.main(HiveSchemaTool.java:1517)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.hadoop.util.RunJar.run(RunJar.java:323)
at org.apache.hadoop.util.RunJar.main(RunJar.java:236)
Caused by:
com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException: Cannot
load connection class because of
[jira] [Updated] (AMBARI-25887) Blueprint inconsistent import/export logic for database connection url
[
https://issues.apache.org/jira/browse/AMBARI-25887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-25887:
---
Attachment: blueprint-configuration.json
> Blueprint inconsistent import/export logic for database connection url
> --
>
> Key: AMBARI-25887
> URL: https://issues.apache.org/jira/browse/AMBARI-25887
> Project: Ambari
> Issue Type: Bug
>Reporter: Zhiguo Wu
>Assignee: Zhiguo Wu
>Priority: Major
> Attachments: blueprint-configuration.json,
> image-2023-03-09-18-53-14-454.png
>
>
> When I manually deploy a cluster which contains hive service, and get
> blueprint config from the cluster:
> !image-2023-03-09-18-53-14-454.png!
>
> then create a new cluster by this config, an error occurs because it cannot
> resolve mysql connection url on hive-site configuration
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package/scripts/hive_metastore.py",
> line 201, in
> HiveMetastore().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 355, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package/scripts/hive_metastore.py",
> line 61, in start
> create_metastore_schema() # execute without config lock
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HIVE/package/scripts/hive.py",
> line 466, in create_metastore_schema
> user = params.hive_user
> File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
> 166, in __init__
> self.env.run()
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py",
> line 280, in action_run
> returns=self.resource.returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy, returns=returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 314, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'export
> HIVE_CONF_DIR=/etc/hive/conf ; /usr/bigtop/current/hive-client/bin/schematool
> -initSchema -dbType mysql -userName hive -passWord [PROTECTED] -verbose'
> returned 1. SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/usr/bigtop/3.2.0/usr/lib/hive/lib/log4j-slf4j-impl-2.17.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/usr/bigtop/3.2.0/usr/lib/hadoop/lib/slf4j-reload4j-1.7.36.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
> Metastore connection URL: jdbc:mysql://%HOSTGROUP::host_group_1%/hive
> Metastore Connection Driver : com.mysql.jdbc.Driver
> Metastore connection User: hive
> org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema
> version.
> Underlying cause:
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException : Cannot
> load connection class because of underlying exception:
> 'java.lang.NumberFormatException: For input string: ":host_group_1%"'.
> SQL Error code: 0
> org.apache.hadoop.hive.metastore.HiveMetaException: Failed to get schema
> version.
> at
> org.apache.hadoop.hive.metastore.tools.HiveSchemaHelper.getConnectionToMetastore(HiveSchemaHelper.java:94)
> at
> org.apache.hive.beeline.HiveSchemaTool.getConnectionToMetastore(HiveSchemaTool.java:169)
> at
> org.apache.hive.beeline.HiveSchemaTool.testConnectionToMetastore(HiveSchemaTool.java:475)
> at
> org.apache.hive.beeline.HiveSchemaTool.doInit(HiveSchemaTool.java:581)
> at
> org.apache.hive.beeline.HiveSchemaTool.doInit(HiveSchemaTool.java:567)
> at org.apache.hive.beeline.HiveSchemaTool.main(HiveSchemaTool.java:1517)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
[jira] [Updated] (AMBARI-25886) Blueprint fails to select configurations
[
https://issues.apache.org/jira/browse/AMBARI-25886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-25886:
---
Attachment: (was: singlenode-hostmap.json)
> Blueprint fails to select configurations
>
>
> Key: AMBARI-25886
> URL: https://issues.apache.org/jira/browse/AMBARI-25886
> Project: Ambari
> Issue Type: Bug
>Reporter: Zhiguo Wu
>Assignee: Zhiguo Wu
>Priority: Major
> Attachments: image-2023-03-09-17-42-54-720.png
>
>
> When I'm using blueprint to create a cluster, it fails to select
> configuration sometimes
> !image-2023-03-09-17-42-54-720.png!
>
> It causes errors when installing services:
> {code:java}
> result_protected = self.vformat(format_string, args, all_params)
> File "/usr/lib64/python2.7/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
> File "/usr/lib64/python2.7/string.py", line 582, in _vformat
> result.append(self.format_field(obj, format_spec))
> File "/usr/lib64/python2.7/string.py", line 599, in format_field
> return format(value, format_spec)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py",
> line 75, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 'hive-env'
> was not found in configurations dictionary! {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25886) Blueprint fails to select configurations
[
https://issues.apache.org/jira/browse/AMBARI-25886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-25886:
---
Attachment: (was: blueprint-singlenode-default.json)
> Blueprint fails to select configurations
>
>
> Key: AMBARI-25886
> URL: https://issues.apache.org/jira/browse/AMBARI-25886
> Project: Ambari
> Issue Type: Bug
>Reporter: Zhiguo Wu
>Assignee: Zhiguo Wu
>Priority: Major
> Attachments: image-2023-03-09-17-42-54-720.png
>
>
> When I'm using blueprint to create a cluster, it fails to select
> configuration sometimes
> !image-2023-03-09-17-42-54-720.png!
>
> It causes errors when installing services:
> {code:java}
> result_protected = self.vformat(format_string, args, all_params)
> File "/usr/lib64/python2.7/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
> File "/usr/lib64/python2.7/string.py", line 582, in _vformat
> result.append(self.format_field(obj, format_spec))
> File "/usr/lib64/python2.7/string.py", line 599, in format_field
> return format(value, format_spec)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py",
> line 75, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 'hive-env'
> was not found in configurations dictionary! {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25886) Blueprint fails to select configurations
[
https://issues.apache.org/jira/browse/AMBARI-25886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhiguo Wu updated AMBARI-25886:
---
Attachment: blueprint-singlenode-default.json
singlenode-hostmap.json
> Blueprint fails to select configurations
>
>
> Key: AMBARI-25886
> URL: https://issues.apache.org/jira/browse/AMBARI-25886
> Project: Ambari
> Issue Type: Bug
>Reporter: Zhiguo Wu
>Assignee: Zhiguo Wu
>Priority: Major
> Attachments: blueprint-singlenode-default.json,
> image-2023-03-09-17-42-54-720.png, singlenode-hostmap.json
>
>
> When I'm using blueprint to create a cluster, it fails to select
> configuration sometimes
> !image-2023-03-09-17-42-54-720.png!
>
> It causes errors when installing services:
> {code:java}
> result_protected = self.vformat(format_string, args, all_params)
> File "/usr/lib64/python2.7/string.py", line 549, in vformat
> result = self._vformat(format_string, args, kwargs, used_args, 2)
> File "/usr/lib64/python2.7/string.py", line 582, in _vformat
> result.append(self.format_field(obj, format_spec))
> File "/usr/lib64/python2.7/string.py", line 599, in format_field
> return format(value, format_spec)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py",
> line 75, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 'hive-env'
> was not found in configurations dictionary! {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
