[jira] [Created] (AMBARI-25706) -DskipPythonTests is not skipping python tests in amabri-agent
Mohammad Arshad created AMBARI-25706:
Summary: -DskipPythonTests is not skipping python tests in
amabri-agent
Key: AMBARI-25706
URL: https://issues.apache.org/jira/browse/AMBARI-25706
Project: Ambari
Issue Type: Bug
Components: ambari-agent, test
Reporter: Mohammad Arshad
-DskipPythonTests is not skipping python tests in amabri-agent.
To fix this issue we should use skipPythonTests instead of skipTests for
python test case execution.
{code:java}
${skipTests}
{code}
should be changed to
{code:java}
${skipPythonTests}
{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] [Commented] (AMBARI-25706) -DskipPythonTests is not skipping python tests in amabri-agent
[
https://issues.apache.org/jira/browse/AMBARI-25706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17565155#comment-17565155
]
Mohammad Arshad commented on AMBARI-25706:
--
I will submit the PR.
> -DskipPythonTests is not skipping python tests in amabri-agent
> --
>
> Key: AMBARI-25706
> URL: https://issues.apache.org/jira/browse/AMBARI-25706
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, test
>Reporter: Mohammad Arshad
>Priority: Major
>
> -DskipPythonTests is not skipping python tests in amabri-agent.
> To fix this issue we should use skipPythonTests instead of skipTests for
> python test case execution.
> {code:java}
> ${skipTests}
> {code}
> should be changed to
> {code:java}
> ${skipPythonTests}
> {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] [Commented] (AMBARI-23780) Implement an upgrade helper in Ambari Metrics collector that copies data from the old schema to the new.
[ https://issues.apache.org/jira/browse/AMBARI-23780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17566652#comment-17566652 ] Mohammad Arshad commented on AMBARI-23780: -- Upgrade helper is upgrading only following table's data * METRIC_AGGREGATE_DAILY * METRIC_AGGREGATE_HOURLY * METRIC_AGGREGATE_MINUTE * METRIC_RECORD_DAILY * METRIC_RECORD_HOURLY * METRIC_RECORD_MINUTE Any insight on why other below tables are not upgraded? * HOSTED_APPS_METADATA * METRICS_METADATA * METRIC_AGGREGATE * METRIC_RECORD > Implement an upgrade helper in Ambari Metrics collector that copies data from > the old schema to the new. > - > > Key: AMBARI-23780 > URL: https://issues.apache.org/jira/browse/AMBARI-23780 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 2h 50m > Remaining Estimate: 0h > > * The upgrade helper can be a main class that is callable through command > line. > * Inputs to the upgrade helper > # Metric list file (Default -> metrics_whitelist file in conf. If not > present, copy over all the metrics) > # Start timestamp (Default -> Last 1 month) (Max 8640 points per metric > in minute table) > * The upgrade helper runs a set of SQL queries to fetch data from all > aggregate tables except METRIC_AGGREGATE and uses the API to write to the > corresponding new tables. > * The tool marks the completion of every metric entry by using a marker file > (list of processed metric names) or a simple hbase table. > * The next time the upgrade tool is invoked, the marker is used to identify > whether the metric needs to be copied. > * Let's have the upgrade helper log the status to a different file than > collector log as a mechanism to monitor the status. > We have to make a decision on whether the upgrade tool helper should be > *synchronous* or *asynchronous*. If it is asynchronous, we should add the > ability for it to '*stop performing 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] [Commented] (AMBARI-25706) -DskipPythonTests is not skipping python tests in amabri-agent
[
https://issues.apache.org/jira/browse/AMBARI-25706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644933#comment-17644933
]
Mohammad Arshad commented on AMBARI-25706:
--
Thanks [~brahmareddy] for reviewing and merging the PR.
> -DskipPythonTests is not skipping python tests in amabri-agent
> --
>
> Key: AMBARI-25706
> URL: https://issues.apache.org/jira/browse/AMBARI-25706
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, test
>Reporter: Mohammad Arshad
>Priority: Major
> Fix For: 2.7.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> -DskipPythonTests is not skipping python tests in amabri-agent.
> To fix this issue we should use skipPythonTests instead of skipTests for
> python test case execution.
> {code:java}
> ${skipTests}
> {code}
> should be changed to
> {code:java}
> ${skipPythonTests}
> {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] [Commented] (AMBARI-25706) -DskipPythonTests is not skipping python tests in amabri-agent
[
https://issues.apache.org/jira/browse/AMBARI-25706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645313#comment-17645313
]
Mohammad Arshad commented on AMBARI-25706:
--
bq. I added you as contributor and welcome to aboard. Feel free to assign to
assign your self.
Not able to assign this jira and any other ambari jira to me, Assignee field
edit is not enabled. I am able to assign Zookeeper, HBase jiras to my self, but
not ambari jiras.
any idea what could be the reason?
> -DskipPythonTests is not skipping python tests in amabri-agent
> --
>
> Key: AMBARI-25706
> URL: https://issues.apache.org/jira/browse/AMBARI-25706
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, test
>Reporter: Mohammad Arshad
>Priority: Major
> Fix For: 2.7.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> -DskipPythonTests is not skipping python tests in amabri-agent.
> To fix this issue we should use skipPythonTests instead of skipTests for
> python test case execution.
> {code:java}
> ${skipTests}
> {code}
> should be changed to
> {code:java}
> ${skipPythonTests}
> {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] [Created] (AMBARI-25803) ambari and ambari-metrics repo cloning logs warning because of case sensitive files
Mohammad Arshad created AMBARI-25803:
Summary: ambari and ambari-metrics repo cloning logs warning
because of case sensitive files
Key: AMBARI-25803
URL: https://issues.apache.org/jira/browse/AMBARI-25803
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Reporter: Mohammad Arshad
Fix For: 2.7.8
{noformat}
git clone https://github.com/apache/ambari-metrics.git
{noformat}
above commands logs following warning
{noformat}
warning: the following paths have collided (e.g. case-sensitive paths
on a case-insensitive filesystem) and only one from the same
colliding group is in the working tree:
'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.DAT'
'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.dat'
'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.DAT'
'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.dat'
{noformat}
I checked cotent of AMSSMOKETESTFAKE.DAT AMSSMOKETESTFAKE.data is same.
Also the content of TIMELINE_METRIC_STORE_WATCHER.DAT and
TIMELINE_METRIC_STORE_WATCHER.data is same.
There is not reason to keep both the files. we should delete .DAT files.
--
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-25803) ambari and ambari-metrics repo cloning logs warning because of case sensitive files
[
https://issues.apache.org/jira/browse/AMBARI-25803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645319#comment-17645319
]
Mohammad Arshad commented on AMBARI-25803:
--
I will submit the PR
> ambari and ambari-metrics repo cloning logs warning because of case sensitive
> files
> ---
>
> Key: AMBARI-25803
> URL: https://issues.apache.org/jira/browse/AMBARI-25803
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Priority: Major
> Fix For: 2.7.8
>
>
> {noformat}
> git clone https://github.com/apache/ambari-metrics.git
> {noformat}
> above commands logs following warning
> {noformat}
> warning: the following paths have collided (e.g. case-sensitive paths
> on a case-insensitive filesystem) and only one from the same
> colliding group is in the working tree:
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.DAT'
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.dat'
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.DAT'
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.dat'
> {noformat}
> I checked cotent of AMSSMOKETESTFAKE.DAT AMSSMOKETESTFAKE.data is same.
> Also the content of TIMELINE_METRIC_STORE_WATCHER.DAT and
> TIMELINE_METRIC_STORE_WATCHER.data is same.
> There is not reason to keep both the files. we should delete .DAT files.
--
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-25803) ambari and ambari-metrics repo cloning logs warning because of case sensitive files
[
https://issues.apache.org/jira/browse/AMBARI-25803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25803:
-
Description:
{noformat}
git clone https://github.com/apache/ambari-metrics.git
{noformat}
above commands logs following warning
{noformat}
warning: the following paths have collided (e.g. case-sensitive paths
on a case-insensitive filesystem) and only one from the same
colliding group is in the working tree:
'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.DAT'
'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.dat'
'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.DAT'
'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.dat'
{noformat}
I checked content of AMSSMOKETESTFAKE.DAT AMSSMOKETESTFAKE.dat is same.
Also the content of TIMELINE_METRIC_STORE_WATCHER.DAT and
TIMELINE_METRIC_STORE_WATCHER.dat is same.
There is no reason to keep both the files. we should delete .DAT files.
was:
{noformat}
git clone https://github.com/apache/ambari-metrics.git
{noformat}
above commands logs following warning
{noformat}
warning: the following paths have collided (e.g. case-sensitive paths
on a case-insensitive filesystem) and only one from the same
colliding group is in the working tree:
'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.DAT'
'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.dat'
'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.DAT'
'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.dat'
{noformat}
I checked cotent of AMSSMOKETESTFAKE.DAT AMSSMOKETESTFAKE.data is same.
Also the content of TIMELINE_METRIC_STORE_WATCHER.DAT and
TIMELINE_METRIC_STORE_WATCHER.data is same.
There is not reason to keep both the files. we should delete .DAT files.
> ambari and ambari-metrics repo cloning logs warning because of case sensitive
> files
> ---
>
> Key: AMBARI-25803
> URL: https://issues.apache.org/jira/browse/AMBARI-25803
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Priority: Major
> Fix For: 2.7.8
>
>
> {noformat}
> git clone https://github.com/apache/ambari-metrics.git
> {noformat}
> above commands logs following warning
> {noformat}
> warning: the following paths have collided (e.g. case-sensitive paths
> on a case-insensitive filesystem) and only one from the same
> colliding group is in the working tree:
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.DAT'
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.dat'
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.DAT'
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.dat'
> {noformat}
> I checked content of AMSSMOKETESTFAKE.DAT AMSSMOKETESTFAKE.dat is same.
> Also the content of TIMELINE_METRIC_STORE_WATCHER.DAT and
> TIMELINE_METRIC_STORE_WATCHER.dat is same.
> There is no reason to keep both the files. we should delete .DAT files.
--
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-25803) ambari and ambari-metrics repo cloning logs warning because of case sensitive files
[
https://issues.apache.org/jira/browse/AMBARI-25803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25803:
-
Description:
{noformat}
git clone https://github.com/apache/ambari-metrics.git
{noformat}
above command logs following warning
{noformat}
warning: the following paths have collided (e.g. case-sensitive paths
on a case-insensitive filesystem) and only one from the same
colliding group is in the working tree:
'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.DAT'
'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.dat'
'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.DAT'
'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.dat'
{noformat}
I checked content of AMSSMOKETESTFAKE.DAT AMSSMOKETESTFAKE.dat is same.
Also the content of TIMELINE_METRIC_STORE_WATCHER.DAT and
TIMELINE_METRIC_STORE_WATCHER.dat is same.
There is no reason to keep both the files. we should delete .DAT files.
was:
{noformat}
git clone https://github.com/apache/ambari-metrics.git
{noformat}
above commands logs following warning
{noformat}
warning: the following paths have collided (e.g. case-sensitive paths
on a case-insensitive filesystem) and only one from the same
colliding group is in the working tree:
'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.DAT'
'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.dat'
'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.DAT'
'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.dat'
{noformat}
I checked content of AMSSMOKETESTFAKE.DAT AMSSMOKETESTFAKE.dat is same.
Also the content of TIMELINE_METRIC_STORE_WATCHER.DAT and
TIMELINE_METRIC_STORE_WATCHER.dat is same.
There is no reason to keep both the files. we should delete .DAT files.
> ambari and ambari-metrics repo cloning logs warning because of case sensitive
> files
> ---
>
> Key: AMBARI-25803
> URL: https://issues.apache.org/jira/browse/AMBARI-25803
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Priority: Major
> Fix For: 2.7.8
>
>
> {noformat}
> git clone https://github.com/apache/ambari-metrics.git
> {noformat}
> above command logs following warning
> {noformat}
> warning: the following paths have collided (e.g. case-sensitive paths
> on a case-insensitive filesystem) and only one from the same
> colliding group is in the working tree:
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.DAT'
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.dat'
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.DAT'
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.dat'
> {noformat}
> I checked content of AMSSMOKETESTFAKE.DAT AMSSMOKETESTFAKE.dat is same.
> Also the content of TIMELINE_METRIC_STORE_WATCHER.DAT and
> TIMELINE_METRIC_STORE_WATCHER.dat is same.
> There is no reason to keep both the files. we should delete .DAT files.
--
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-25808) Metrics data simulator throws NPE
Mohammad Arshad created AMBARI-25808:
Summary: Metrics data simulator throws NPE
Key: AMBARI-25808
URL: https://issues.apache.org/jira/browse/AMBARI-25808
Project: Ambari
Issue Type: Bug
Reporter: Mohammad Arshad
Fix For: 2.7.8
{noformat}
user@host1 bin % ./start.sh localhost:6188 2
{noformat}
{code:java}
2022-12-10 00:00:15,245 INFO [main] loadsimulator.MetricsLoadSimulator
(MetricsLoadSimulator.java:parseArgs(110)) - Recognized options:
baseHostName=host1 hosts#=2 trafficMode=burst metricsHostName=localhost:6188
collectIntervalMillis=15000 sendIntervalMillis=6 simulateMaster=false
2022-12-10 00:00:15,250 INFO [main] data.MetricsGeneratorConfigurer
(MetricsGeneratorConfigurer.java:readMetrics(67)) - Loading metrics_def/HOST.dat
2022-12-10 00:00:15,269 INFO [main] data.MetricsGeneratorConfigurer
(MetricsGeneratorConfigurer.java:readMetrics(67)) - Loading
metrics_def/DATANODE.dat
2022-12-10 00:00:15,270 INFO [main] data.MetricsGeneratorConfigurer
(MetricsGeneratorConfigurer.java:readMetrics(67)) - Loading
metrics_def/NODEMANAGER.dat
2022-12-10 00:00:15,272 INFO [main] data.MetricsGeneratorConfigurer
(MetricsGeneratorConfigurer.java:readMetrics(67)) - Loading
metrics_def/SLAVE_HBASE.dat
Exception in thread "main" java.lang.NullPointerException
at java.io.Reader.(Reader.java:78)
at java.io.InputStreamReader.(InputStreamReader.java:72)
at
org.apache.ambari.metrics.core.loadsimulator.data.MetricsGeneratorConfigurer.readMetrics(MetricsGeneratorConfigurer.java:72)
at
org.apache.ambari.metrics.core.loadsimulator.data.MetricsGeneratorConfigurer.createMetricsForHost(MetricsGeneratorConfigurer.java:57)
at
org.apache.ambari.metrics.core.loadsimulator.LoadRunner.createApplicationMetrics(LoadRunner.java:112)
at
org.apache.ambari.metrics.core.loadsimulator.LoadRunner.addMetricsWorkers(LoadRunner.java:100)
at
org.apache.ambari.metrics.core.loadsimulator.LoadRunner.prepareWorkers(LoadRunner.java:88)
at
org.apache.ambari.metrics.core.loadsimulator.LoadRunner.(LoadRunner.java:69)
at
org.apache.ambari.metrics.core.loadsimulator.MetricsLoadSimulator.main(MetricsLoadSimulator.java:48)
{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] [Created] (AMBARI-25809) ambari-metrics-host-monitoring project build creates temp folder outside of target folder
Mohammad Arshad created AMBARI-25809:
Summary: ambari-metrics-host-monitoring project build creates temp
folder outside of target folder
Key: AMBARI-25809
URL: https://issues.apache.org/jira/browse/AMBARI-25809
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Reporter: Mohammad Arshad
Fix For: 2.0.0
ambari-metrics-host-monitoring project creates
ambari-metrics-host-monitoring\target\psutil_build_temp folder under ambari
folder
it should be created under the target folder
Run mvn clean install -DskipTests then run git status to know the folder
creation status
{noformat}
user1@host1 ambari-metrics-host-monitoring % git status
On branch master
Your branch is up to date with 'origin/master'.
Untracked files:
(use "git add ..." to include in what will be committed)
"../ambari-metrics-host-monitoring\\target\\psutil_build_temp/"
{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] [Created] (AMBARI-25810) Allow skipping Python unit tests in ambari-metrics
Mohammad Arshad created AMBARI-25810: Summary: Allow skipping Python unit tests in ambari-metrics Key: AMBARI-25810 URL: https://issues.apache.org/jira/browse/AMBARI-25810 Project: Ambari Issue Type: Bug Components: metrics Reporter: Mohammad Arshad Fix For: 2.0.0 Currently skipPythonTests flag is available in ambari but not in metrics. Lets add in metrics too. -- 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] [Assigned] (AMBARI-25706) -DskipPythonTests is not skipping python tests in amabri-agent
[
https://issues.apache.org/jira/browse/AMBARI-25706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad reassigned AMBARI-25706:
Assignee: Mohammad Arshad
> -DskipPythonTests is not skipping python tests in amabri-agent
> --
>
> Key: AMBARI-25706
> URL: https://issues.apache.org/jira/browse/AMBARI-25706
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, test
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Fix For: 2.7.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> -DskipPythonTests is not skipping python tests in amabri-agent.
> To fix this issue we should use skipPythonTests instead of skipTests for
> python test case execution.
> {code:java}
> ${skipTests}
> {code}
> should be changed to
> {code:java}
> ${skipPythonTests}
> {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] [Assigned] (AMBARI-25810) Allow skipping Python unit tests in ambari-metrics
[ https://issues.apache.org/jira/browse/AMBARI-25810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad reassigned AMBARI-25810: Assignee: Mohammad Arshad > Allow skipping Python unit tests in ambari-metrics > -- > > Key: AMBARI-25810 > URL: https://issues.apache.org/jira/browse/AMBARI-25810 > Project: Ambari > Issue Type: Bug > Components: metrics >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Minor > Labels: pull-request-available > Fix For: 2.0.0 > > > Currently skipPythonTests flag is available in ambari but not in metrics. > Lets add in metrics too. -- 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] [Assigned] (AMBARI-25808) Metrics data simulator throws NPE
[
https://issues.apache.org/jira/browse/AMBARI-25808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad reassigned AMBARI-25808:
Assignee: Mohammad Arshad
> Metrics data simulator throws NPE
> -
>
> Key: AMBARI-25808
> URL: https://issues.apache.org/jira/browse/AMBARI-25808
> Project: Ambari
> Issue Type: Bug
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> user@host1 bin % ./start.sh localhost:6188 2
> {noformat}
> {code:java}
> 2022-12-10 00:00:15,245 INFO [main] loadsimulator.MetricsLoadSimulator
> (MetricsLoadSimulator.java:parseArgs(110)) - Recognized options:
> baseHostName=host1 hosts#=2 trafficMode=burst metricsHostName=localhost:6188
> collectIntervalMillis=15000 sendIntervalMillis=6 simulateMaster=false
> 2022-12-10 00:00:15,250 INFO [main] data.MetricsGeneratorConfigurer
> (MetricsGeneratorConfigurer.java:readMetrics(67)) - Loading
> metrics_def/HOST.dat
> 2022-12-10 00:00:15,269 INFO [main] data.MetricsGeneratorConfigurer
> (MetricsGeneratorConfigurer.java:readMetrics(67)) - Loading
> metrics_def/DATANODE.dat
> 2022-12-10 00:00:15,270 INFO [main] data.MetricsGeneratorConfigurer
> (MetricsGeneratorConfigurer.java:readMetrics(67)) - Loading
> metrics_def/NODEMANAGER.dat
> 2022-12-10 00:00:15,272 INFO [main] data.MetricsGeneratorConfigurer
> (MetricsGeneratorConfigurer.java:readMetrics(67)) - Loading
> metrics_def/SLAVE_HBASE.dat
> Exception in thread "main" java.lang.NullPointerException
> at java.io.Reader.(Reader.java:78)
> at java.io.InputStreamReader.(InputStreamReader.java:72)
> at
> org.apache.ambari.metrics.core.loadsimulator.data.MetricsGeneratorConfigurer.readMetrics(MetricsGeneratorConfigurer.java:72)
> at
> org.apache.ambari.metrics.core.loadsimulator.data.MetricsGeneratorConfigurer.createMetricsForHost(MetricsGeneratorConfigurer.java:57)
> at
> org.apache.ambari.metrics.core.loadsimulator.LoadRunner.createApplicationMetrics(LoadRunner.java:112)
> at
> org.apache.ambari.metrics.core.loadsimulator.LoadRunner.addMetricsWorkers(LoadRunner.java:100)
> at
> org.apache.ambari.metrics.core.loadsimulator.LoadRunner.prepareWorkers(LoadRunner.java:88)
> at
> org.apache.ambari.metrics.core.loadsimulator.LoadRunner.(LoadRunner.java:69)
> at
> org.apache.ambari.metrics.core.loadsimulator.MetricsLoadSimulator.main(MetricsLoadSimulator.java:48)
> {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] [Assigned] (AMBARI-25809) ambari-metrics-host-monitoring project build creates temp folder outside of target folder
[
https://issues.apache.org/jira/browse/AMBARI-25809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad reassigned AMBARI-25809:
Assignee: Mohammad Arshad
> ambari-metrics-host-monitoring project build creates temp folder outside of
> target folder
> -
>
> Key: AMBARI-25809
> URL: https://issues.apache.org/jira/browse/AMBARI-25809
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.0.0
>
>
> ambari-metrics-host-monitoring project creates
> ambari-metrics-host-monitoring\target\psutil_build_temp folder under ambari
> folder
> it should be created under the target folder
> Run mvn clean install -DskipTests then run git status to know the folder
> creation status
> {noformat}
> user1@host1 ambari-metrics-host-monitoring % git status
> On branch master
> Your branch is up to date with 'origin/master'.
> Untracked files:
> (use "git add ..." to include in what will be committed)
> "../ambari-metrics-host-monitoring\\target\\psutil_build_temp/"
> {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] [Assigned] (AMBARI-25803) ambari and ambari-metrics repo cloning logs warning because of case sensitive files
[
https://issues.apache.org/jira/browse/AMBARI-25803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad reassigned AMBARI-25803:
Assignee: Mohammad Arshad
> ambari and ambari-metrics repo cloning logs warning because of case sensitive
> files
> ---
>
> Key: AMBARI-25803
> URL: https://issues.apache.org/jira/browse/AMBARI-25803
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> git clone https://github.com/apache/ambari-metrics.git
> {noformat}
> above command logs following warning
> {noformat}
> warning: the following paths have collided (e.g. case-sensitive paths
> on a case-insensitive filesystem) and only one from the same
> colliding group is in the working tree:
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.DAT'
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.dat'
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.DAT'
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.dat'
> {noformat}
> I checked content of AMSSMOKETESTFAKE.DAT AMSSMOKETESTFAKE.dat is same.
> Also the content of TIMELINE_METRIC_STORE_WATCHER.DAT and
> TIMELINE_METRIC_STORE_WATCHER.dat is same.
> There is no reason to keep both the files. we should delete .DAT files.
--
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-25811) Optimize ambari metrics build time
Mohammad Arshad created AMBARI-25811:
Summary: Optimize ambari metrics build time
Key: AMBARI-25811
URL: https://issues.apache.org/jira/browse/AMBARI-25811
Project: Ambari
Issue Type: Improvement
Components: metrics
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
Fix For: 2.0.0
Currently in ambari metrics build, most of the time is taken by
ambari-metrics-assembly.
Looks maven-assembly-plugin is taking lot of time in stitching the artifacts.
Upgrading maven-assembly-plugin from 2.2-beta-5 to 3.4.2(latest version)
reduces the build time significantly
*Before change:*
{noformat}
15:58:46,215 [INFO] Reactor Summary for ambari-metrics 2.0.0.0-SNAPSHOT:
15:58:46,215 [INFO]
15:58:46,218 [INFO] ambari-metrics .
SUCCESS [ 3.960 s]
15:58:46,220 [INFO] Ambari Metrics Common ..
SUCCESS [ 11.492 s]
15:58:46,220 [INFO] Ambari Metrics Hadoop Sink .
SUCCESS [ 7.655 s]
15:58:46,220 [INFO] Ambari Metrics Flume Sink ..
SUCCESS [ 4.045 s]
15:58:46,220 [INFO] Ambari Metrics Kafka Sink ..
SUCCESS [ 3.465 s]
15:58:46,220 [INFO] Ambari Metrics Storm Sink ..
SUCCESS [ 2.887 s]
15:58:46,220 [INFO] Ambari Metrics Collector ...
SUCCESS [ 19.416 s]
15:58:46,220 [INFO] Ambari Metrics Monitor .
SUCCESS [ 4.791 s]
15:58:46,220 [INFO] Ambari Metrics Grafana .
SUCCESS [ 2.838 s]
15:58:46,220 [INFO] Ambari Metrics Host Aggregator .
SUCCESS [ 8.363 s]
15:58:46,220 [INFO] Ambari Metrics Assembly
SUCCESS [09:09 min]
15:58:46,220 [INFO]
15:58:46,220 [INFO] BUILD SUCCESS
15:58:46,220 [INFO]
15:58:46,221 [INFO] Total time: 10:18 min
15:58:46,221 [INFO] Finished at: 2022-12-14T15:58:46+05:30
{noformat}
*After Change:*
{noformat}
16:18:22,667 [INFO] Reactor Summary for ambari-metrics 2.0.0.0-SNAPSHOT:
16:18:22,667 [INFO]
16:18:22,670 [INFO] ambari-metrics .
SUCCESS [ 3.897 s]
16:18:22,671 [INFO] Ambari Metrics Common ..
SUCCESS [ 10.880 s]
16:18:22,671 [INFO] Ambari Metrics Hadoop Sink .
SUCCESS [ 4.681 s]
16:18:22,671 [INFO] Ambari Metrics Flume Sink ..
SUCCESS [ 2.184 s]
16:18:22,671 [INFO] Ambari Metrics Kafka Sink ..
SUCCESS [ 2.949 s]
16:18:22,671 [INFO] Ambari Metrics Storm Sink ..
SUCCESS [ 3.071 s]
16:18:22,671 [INFO] Ambari Metrics Collector ...
SUCCESS [ 18.471 s]
16:18:22,671 [INFO] Ambari Metrics Monitor .
SUCCESS [ 5.416 s]
16:18:22,671 [INFO] Ambari Metrics Grafana .
SUCCESS [ 2.458 s]
16:18:22,671 [INFO] Ambari Metrics Host Aggregator .
SUCCESS [ 8.963 s]
16:18:22,671 [INFO] Ambari Metrics Assembly
SUCCESS [ 57.413 s]
16:18:22,671 [INFO]
16:18:22,671 [INFO] BUILD SUCCESS
16:18:22,671 [INFO]
16:18:22,671 [INFO] Total time: 02:00 min
16:18:22,673 [INFO] Finished at: 2022-12-14T16:18:22+05:30
{noformat}
*As shown above, in my build environment, build time is reduced from 10 minute
to 2 minute.*
--
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-25818) Set default value for jdk.version in ambari-serviceadvisor
Mohammad Arshad created AMBARI-25818:
Summary: Set default value for jdk.version in ambari-serviceadvisor
Key: AMBARI-25818
URL: https://issues.apache.org/jira/browse/AMBARI-25818
Project: Ambari
Issue Type: Bug
Components: service-advisor
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
Fix For: 3.0.0
import the ambari trunk into intellij
try to run any test case.
test case run fails with following error
{noformat}
java: invalid target release: 17
Module ambari-serviceadvisor SDK 1.8 is not compatible with the source version
17.
Upgrade Module SDK in project settings to 17 or higher. Open project settings.
{noformat}
This is because for module ambari-serviceadvisor language level got set wrongly
to 17.
Setting default value for jdk.version in ambari-serviceadvisor solves this
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] [Commented] (AMBARI-25811) Optimize ambari metrics build time
[
https://issues.apache.org/jira/browse/AMBARI-25811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17650939#comment-17650939
]
Mohammad Arshad commented on AMBARI-25811:
--
Thanks [~brahmareddy] for pointing branch-2.7. yes it is applicable to branch-2
as well, raised the PR.
> Optimize ambari metrics build time
> --
>
> Key: AMBARI-25811
> URL: https://issues.apache.org/jira/browse/AMBARI-25811
> Project: Ambari
> Issue Type: Improvement
> Components: build, metrics
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently in ambari metrics build, most of the time is taken by
> ambari-metrics-assembly.
> Looks maven-assembly-plugin is taking lot of time in stitching the artifacts.
> Upgrading maven-assembly-plugin from 2.2-beta-5 to 3.4.2(latest version)
> reduces the build time significantly
> *Before change:*
> {noformat}
> 15:58:46,215 [INFO] Reactor Summary for ambari-metrics 2.0.0.0-SNAPSHOT:
> 15:58:46,215 [INFO]
> 15:58:46,218 [INFO] ambari-metrics .
> SUCCESS [ 3.960 s]
> 15:58:46,220 [INFO] Ambari Metrics Common ..
> SUCCESS [ 11.492 s]
> 15:58:46,220 [INFO] Ambari Metrics Hadoop Sink .
> SUCCESS [ 7.655 s]
> 15:58:46,220 [INFO] Ambari Metrics Flume Sink ..
> SUCCESS [ 4.045 s]
> 15:58:46,220 [INFO] Ambari Metrics Kafka Sink ..
> SUCCESS [ 3.465 s]
> 15:58:46,220 [INFO] Ambari Metrics Storm Sink ..
> SUCCESS [ 2.887 s]
> 15:58:46,220 [INFO] Ambari Metrics Collector ...
> SUCCESS [ 19.416 s]
> 15:58:46,220 [INFO] Ambari Metrics Monitor .
> SUCCESS [ 4.791 s]
> 15:58:46,220 [INFO] Ambari Metrics Grafana .
> SUCCESS [ 2.838 s]
> 15:58:46,220 [INFO] Ambari Metrics Host Aggregator .
> SUCCESS [ 8.363 s]
> 15:58:46,220 [INFO] Ambari Metrics Assembly
> SUCCESS [09:09 min]
> 15:58:46,220 [INFO]
>
> 15:58:46,220 [INFO] BUILD SUCCESS
> 15:58:46,220 [INFO]
>
> 15:58:46,221 [INFO] Total time: 10:18 min
> 15:58:46,221 [INFO] Finished at: 2022-12-14T15:58:46+05:30
> {noformat}
> *After Change:*
> {noformat}
> 16:18:22,667 [INFO] Reactor Summary for ambari-metrics 2.0.0.0-SNAPSHOT:
> 16:18:22,667 [INFO]
> 16:18:22,670 [INFO] ambari-metrics .
> SUCCESS [ 3.897 s]
> 16:18:22,671 [INFO] Ambari Metrics Common ..
> SUCCESS [ 10.880 s]
> 16:18:22,671 [INFO] Ambari Metrics Hadoop Sink .
> SUCCESS [ 4.681 s]
> 16:18:22,671 [INFO] Ambari Metrics Flume Sink ..
> SUCCESS [ 2.184 s]
> 16:18:22,671 [INFO] Ambari Metrics Kafka Sink ..
> SUCCESS [ 2.949 s]
> 16:18:22,671 [INFO] Ambari Metrics Storm Sink ..
> SUCCESS [ 3.071 s]
> 16:18:22,671 [INFO] Ambari Metrics Collector ...
> SUCCESS [ 18.471 s]
> 16:18:22,671 [INFO] Ambari Metrics Monitor .
> SUCCESS [ 5.416 s]
> 16:18:22,671 [INFO] Ambari Metrics Grafana .
> SUCCESS [ 2.458 s]
> 16:18:22,671 [INFO] Ambari Metrics Host Aggregator .
> SUCCESS [ 8.963 s]
> 16:18:22,671 [INFO] Ambari Metrics Assembly
> SUCCESS [ 57.413 s]
> 16:18:22,671 [INFO]
>
> 16:18:22,671 [INFO] BUILD SUCCESS
> 16:18:22,671 [INFO]
>
> 16:18:22,671 [INFO] Total time: 02:00 min
> 16:18:22,673 [INFO] Finished at: 2022-12-14T16:18:22+05:30
> {noformat}
> *As shown above, in my build environment, build time is reduced from 10
> minute to 2 minute.*
--
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-25818) Set default value for jdk.version in ambari-serviceadvisor
[
https://issues.apache.org/jira/browse/AMBARI-25818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17651359#comment-17651359
]
Mohammad Arshad commented on AMBARI-25818:
--
This bug is not directly applicable to branch-2.7
But I see another problem there, ambari-serviceadviser is using java 1.7 but
other modules are using java 1.8.
I think this should be improved. Set the java version 1.8 for
ambari-serviceadviser module also. Raised the PR
https://github.com/apache/ambari/pull/3618
> Set default value for jdk.version in ambari-serviceadvisor
> --
>
> Key: AMBARI-25818
> URL: https://issues.apache.org/jira/browse/AMBARI-25818
> Project: Ambari
> Issue Type: Bug
> Components: service-advisor
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> import the ambari trunk into intellij
> try to run any test case.
> test case run fails with following error
> {noformat}
> java: invalid target release: 17
> Module ambari-serviceadvisor SDK 1.8 is not compatible with the source
> version 17.
> Upgrade Module SDK in project settings to 17 or higher. Open project settings.
> {noformat}
> This is because for module ambari-serviceadvisor language level got set
> wrongly to 17.
> Setting default value for jdk.version in ambari-serviceadvisor solves this
> 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] [Commented] (AMBARI-25803) ambari and ambari-metrics repo cloning logs warning because of case sensitive files
[
https://issues.apache.org/jira/browse/AMBARI-25803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17652195#comment-17652195
]
Mohammad Arshad commented on AMBARI-25803:
--
AMBARI-23427 added AMSSMOKETESTFAKE.DAT and TIMELINE_METRIC_STORE_WATCHER.DAT
on Apr 5, 2018
AMBARI-23804 added AMSSMOKETESTFAKE.dat and TIMELINE_METRIC_STORE_WATCHER.dat
on May 15, 2018
As the content of both .DAT and .dat file is same, .DAT should have been
deleted. looks .DAT deletion was missed.
> ambari and ambari-metrics repo cloning logs warning because of case sensitive
> files
> ---
>
> Key: AMBARI-25803
> URL: https://issues.apache.org/jira/browse/AMBARI-25803
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> git clone https://github.com/apache/ambari-metrics.git
> {noformat}
> above command logs following warning
> {noformat}
> warning: the following paths have collided (e.g. case-sensitive paths
> on a case-insensitive filesystem) and only one from the same
> colliding group is in the working tree:
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.DAT'
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.dat'
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.DAT'
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.dat'
> {noformat}
> I checked content of AMSSMOKETESTFAKE.DAT AMSSMOKETESTFAKE.dat is same.
> Also the content of TIMELINE_METRIC_STORE_WATCHER.DAT and
> TIMELINE_METRIC_STORE_WATCHER.dat is same.
> There is no reason to keep both the files. we should delete .DAT files.
--
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-25803) ambari and ambari-metrics repo cloning logs warning because of case sensitive files
[
https://issues.apache.org/jira/browse/AMBARI-25803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693918#comment-17693918
]
Mohammad Arshad commented on AMBARI-25803:
--
yes
> ambari and ambari-metrics repo cloning logs warning because of case sensitive
> files
> ---
>
> Key: AMBARI-25803
> URL: https://issues.apache.org/jira/browse/AMBARI-25803
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {noformat}
> git clone https://github.com/apache/ambari-metrics.git
> {noformat}
> above command logs following warning
> {noformat}
> warning: the following paths have collided (e.g. case-sensitive paths
> on a case-insensitive filesystem) and only one from the same
> colliding group is in the working tree:
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.DAT'
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/AMSSMOKETESTFAKE.dat'
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.DAT'
>
> 'ambari-metrics-timelineservice/src/main/resources/metrics_def/TIMELINE_METRIC_STORE_WATCHER.dat'
> {noformat}
> I checked content of AMSSMOKETESTFAKE.DAT AMSSMOKETESTFAKE.dat is same.
> Also the content of TIMELINE_METRIC_STORE_WATCHER.DAT and
> TIMELINE_METRIC_STORE_WATCHER.dat is same.
> There is no reason to keep both the files. we should delete .DAT files.
--
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-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:all-tabpanel ] Mohammad Arshad updated AMBARI-25918: - Summary: Ambari is not working with BIGTOP stack 3.2.0 (was: Ambari is not working with BIGTOP stack 3.0ubnucvtr163.92286) > 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 > > -- 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-25918) Ambari is not working with BIGTOP stack 3.0ubnucccccvtr163.92286
Mohammad Arshad created AMBARI-25918: Summary: Ambari is not working with BIGTOP stack 3.0ubnucvtr163.92286 Key: AMBARI-25918 URL: https://issues.apache.org/jira/browse/AMBARI-25918 Project: Ambari Issue Type: Bug Components: stacks Reporter: Mohammad Arshad Fix For: 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-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:all-tabpanel
]
Mohammad Arshad updated AMBARI-25918:
-
Description:
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.
> 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/big
[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&focusedCommentId=17721616#comment-17721616
]
Mohammad Arshad commented on AMBARI-25918:
--
Thanks [~wuzhiguo].
When I build the bigtop with -PparentDir=/usr/bigtop -PpkgSuffix options, both
problems, mentioned in this jira, are solved.
> 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] [Resolved] (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:all-tabpanel
]
Mohammad Arshad resolved AMBARI-25918.
--
Assignee: Mohammad Arshad
Resolution: Duplicate
> 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
>Assignee: 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] [Created] (AMBARI-25936) Ambari metrics collector fails with IncompatibleClassChangeError, Found HdfsFileStatus but expected FanOutOneBlockAsyncDFSOutputHelper
Mohammad Arshad created AMBARI-25936:
Summary: Ambari metrics collector fails with
IncompatibleClassChangeError, Found HdfsFileStatus but expected
FanOutOneBlockAsyncDFSOutputHelper
Key: AMBARI-25936
URL: https://issues.apache.org/jira/browse/AMBARI-25936
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
Built ambari trunk, ambari metrics master. Using bitop 3.2.0
installed hadoop cluster using ambari,
ambari metrics is failing with following errors
{code:java}
2023-05-15 06:00:35,374 INFO [master/Host1:61300:becomeActiveMaster]
wal.AbstractFSWAL: Closed WAL: AsyncFSWAL Host1%2C61300%2C1684130431341:(num
1684130435340)
2023-05-15 06:00:35,376 ERROR [master/Host1:61300:becomeActiveMaster]
master.HMaster: Failed to become active master
java.lang.IncompatibleClassChangeError: Found interface
org.apache.hadoop.hdfs.protocol.HdfsFileStatus, but class was expected
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:535)
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.access$400(FanOutOneBlockAsyncDFSOutputHelper.java:112)
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:615)
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:610)
at
org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:623)
at
org.apache.hadoop.hbase.io.asyncfs.AsyncFSOutputHelper.createOutput(AsyncFSOutputHelper.java:53)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncProtobufLogWriter.initOutput(AsyncProtobufLogWriter.java:190)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractProtobufLogWriter.init(AbstractProtobufLogWriter.java:160)
at
org.apache.hadoop.hbase.wal.AsyncFSWALProvider.createAsyncWriter(AsyncFSWALProvider.java:116)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:723)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:129)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:833)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:547)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.init(AbstractFSWAL.java:488)
at
org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:160)
at
org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:62)
at org.apache.hadoop.hbase.wal.WALFactory.getWAL(WALFactory.java:295)
at
org.apache.hadoop.hbase.master.region.MasterRegion.createWAL(MasterRegion.java:200)
at
org.apache.hadoop.hbase.master.region.MasterRegion.open(MasterRegion.java:255)
at
org.apache.hadoop.hbase.master.region.MasterRegion.create(MasterRegion.java:336)
at
org.apache.hadoop.hbase.master.region.MasterRegionFactory.create(MasterRegionFactory.java:104)
at
org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:846)
at
org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2175)
at org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:520)
at java.lang.Thread.run(Thread.java:750)
2023-05-15 06:00:35,378 ERROR [master/Host1:61300:becomeActiveMaster]
master.HMaster: * ABORTING master Host1,61300,1684130431341: Unhandled
exception. Starting shutdown. *
java.lang.IncompatibleClassChangeError: Found interface
org.apache.hadoop.hdfs.protocol.HdfsFileStatus, but class was expected
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:535)
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.access$400(FanOutOneBlockAsyncDFSOutputHelper.java:112)
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:615)
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:610)
at
org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
{code}
Seems whatever hbase is used in ambari metrics is not build using hadoop3
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (AMBARI-25936) Ambari metrics collector fails with IncompatibleClassChangeError, Found HdfsFileStatus but expected FanOutOneBlockAsyncDFSOutputHelper
[
https://issues.apache.org/jira/browse/AMBARI-25936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25936:
-
Description:
Built ambari trunk, ambari metrics master. Using bitop 3.2.0
installed hadoop cluster using ambari,
ambari metrics is failing with following errors
{code:java}
2023-05-15 06:00:35,374 INFO [master/Host1:61300:becomeActiveMaster]
wal.AbstractFSWAL: Closed WAL: AsyncFSWAL Host1%2C61300%2C1684130431341:(num
1684130435340)
2023-05-15 06:00:35,376 ERROR [master/Host1:61300:becomeActiveMaster]
master.HMaster: Failed to become active master
java.lang.IncompatibleClassChangeError: Found interface
org.apache.hadoop.hdfs.protocol.HdfsFileStatus, but class was expected
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:535)
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.access$400(FanOutOneBlockAsyncDFSOutputHelper.java:112)
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:615)
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:610)
at
org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:623)
at
org.apache.hadoop.hbase.io.asyncfs.AsyncFSOutputHelper.createOutput(AsyncFSOutputHelper.java:53)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncProtobufLogWriter.initOutput(AsyncProtobufLogWriter.java:190)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractProtobufLogWriter.init(AbstractProtobufLogWriter.java:160)
at
org.apache.hadoop.hbase.wal.AsyncFSWALProvider.createAsyncWriter(AsyncFSWALProvider.java:116)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:723)
at
org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:129)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:833)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:547)
at
org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.init(AbstractFSWAL.java:488)
at
org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:160)
at
org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:62)
at org.apache.hadoop.hbase.wal.WALFactory.getWAL(WALFactory.java:295)
at
org.apache.hadoop.hbase.master.region.MasterRegion.createWAL(MasterRegion.java:200)
at
org.apache.hadoop.hbase.master.region.MasterRegion.open(MasterRegion.java:255)
at
org.apache.hadoop.hbase.master.region.MasterRegion.create(MasterRegion.java:336)
at
org.apache.hadoop.hbase.master.region.MasterRegionFactory.create(MasterRegionFactory.java:104)
at
org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:846)
at
org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2175)
at org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:520)
at java.lang.Thread.run(Thread.java:750)
2023-05-15 06:00:35,378 ERROR [master/Host1:61300:becomeActiveMaster]
master.HMaster: * ABORTING master Host1,61300,1684130431341: Unhandled
exception. Starting shutdown. *
java.lang.IncompatibleClassChangeError: Found interface
org.apache.hadoop.hdfs.protocol.HdfsFileStatus, but class was expected
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:535)
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.access$400(FanOutOneBlockAsyncDFSOutputHelper.java:112)
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:615)
at
org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:610)
at
org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
{code}
was:
Built ambari trunk, ambari metrics master. Using bitop 3.2.0
installed hadoop cluster using ambari,
ambari metrics is failing with following errors
{code:java}
2023-05-15 06:00:35,374 INFO [master/Host1:61300:becomeActiveMaster]
wal.AbstractFSWAL: Closed WAL: AsyncFSWAL Host1%2C61300%2C1684130431341:(num
1684130435340)
2023-05-15 06:00:35,376 ERROR [master/Host1:61300:becomeActiveMaster]
master.HMaster: Failed to become active master
java.lang.IncompatibleClassChangeE
[jira] [Created] (AMBARI-25939) Move Ambari metrics collector does not update timeline.metrics.service.webapp.address
Mohammad Arshad created AMBARI-25939:
Summary: Move Ambari metrics collector does not update
timeline.metrics.service.webapp.address
Key: AMBARI-25939
URL: https://issues.apache.org/jira/browse/AMBARI-25939
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: metrics-3.0.0
Reporter: Mohammad Arshad
Move Ambari metrics collector does not update
timeline.metrics.service.webapp.address and restart fails with follwing
exceptions
{code:java}
2023-05-15 13:59:52,221 INFO org.apache.hadoop.http.HttpServer2:
HttpServer.start() threw a non Bind IOException
java.net.BindException: Port in use: Host1:6188
at
org.apache.hadoop.http.HttpServer2.constructBindException(HttpServer2.java:1344)
at
org.apache.hadoop.http.HttpServer2.bindForSinglePort(HttpServer2.java:1366)
at
org.apache.hadoop.http.HttpServer2.openListeners(HttpServer2.java:1429)
at org.apache.hadoop.http.HttpServer2.start(HttpServer2.java:1275)
at org.apache.hadoop.yarn.webapp.WebApps$Builder.start(WebApps.java:472)
at org.apache.hadoop.yarn.webapp.WebApps$Builder.start(WebApps.java:461)
at
org.apache.ambari.metrics.AMSApplicationServer.startWebApp(AMSApplicationServer.java:135)
at
org.apache.ambari.metrics.AMSApplicationServer.serviceStart(AMSApplicationServer.java:73)
at
org.apache.hadoop.service.AbstractService.start(AbstractService.java:194)
at
org.apache.ambari.metrics.AMSApplicationServer.launchAMSApplicationServer(AMSApplicationServer.java:98)
at
org.apache.ambari.metrics.AMSApplicationServer.main(AMSApplicationServer.java:107)
Caused by: java.io.IOException: Failed to bind to Host1/IP:6188
at
org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:349)
at
org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:310)
at
org.apache.hadoop.http.HttpServer2.bindListener(HttpServer2.java:1331)
at
org.apache.hadoop.http.HttpServer2.bindForSinglePort(HttpServer2.java:1362)
... 9 more
Caused by: java.net.BindException: Cannot assign requested address
at sun.nio.ch.Net.bind0(Native Method)
{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] [Assigned] (AMBARI-25939) Move Ambari metrics collector does not update timeline.metrics.service.webapp.address
[
https://issues.apache.org/jira/browse/AMBARI-25939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad reassigned AMBARI-25939:
Assignee: Mohammad Arshad
> Move Ambari metrics collector does not update
> timeline.metrics.service.webapp.address
> -
>
> Key: AMBARI-25939
> URL: https://issues.apache.org/jira/browse/AMBARI-25939
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
>
> Move Ambari metrics collector does not update
> timeline.metrics.service.webapp.address and restart fails with follwing
> exceptions
> {code:java}
> 2023-05-15 13:59:52,221 INFO org.apache.hadoop.http.HttpServer2:
> HttpServer.start() threw a non Bind IOException
> java.net.BindException: Port in use: Host1:6188
> at
> org.apache.hadoop.http.HttpServer2.constructBindException(HttpServer2.java:1344)
> at
> org.apache.hadoop.http.HttpServer2.bindForSinglePort(HttpServer2.java:1366)
> at
> org.apache.hadoop.http.HttpServer2.openListeners(HttpServer2.java:1429)
> at org.apache.hadoop.http.HttpServer2.start(HttpServer2.java:1275)
> at
> org.apache.hadoop.yarn.webapp.WebApps$Builder.start(WebApps.java:472)
> at
> org.apache.hadoop.yarn.webapp.WebApps$Builder.start(WebApps.java:461)
> at
> org.apache.ambari.metrics.AMSApplicationServer.startWebApp(AMSApplicationServer.java:135)
> at
> org.apache.ambari.metrics.AMSApplicationServer.serviceStart(AMSApplicationServer.java:73)
> at
> org.apache.hadoop.service.AbstractService.start(AbstractService.java:194)
> at
> org.apache.ambari.metrics.AMSApplicationServer.launchAMSApplicationServer(AMSApplicationServer.java:98)
> at
> org.apache.ambari.metrics.AMSApplicationServer.main(AMSApplicationServer.java:107)
> Caused by: java.io.IOException: Failed to bind to Host1/IP:6188
> at
> org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:349)
> at
> org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:310)
> at
> org.apache.hadoop.http.HttpServer2.bindListener(HttpServer2.java:1331)
> at
> org.apache.hadoop.http.HttpServer2.bindForSinglePort(HttpServer2.java:1362)
> ... 9 more
> Caused by: java.net.BindException: Cannot assign requested address
> at sun.nio.ch.Net.bind0(Native Method)
> {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] [Created] (AMBARI-25940) Ambari grafana ambari-server-jvm dashboard loading fails
Mohammad Arshad created AMBARI-25940:
Summary: Ambari grafana ambari-server-jvm dashboard loading fails
Key: AMBARI-25940
URL: https://issues.apache.org/jira/browse/AMBARI-25940
Project: Ambari
Issue Type: Bug
Components: ambari-trunk
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
Installed hadoop cluster using ambari. Used following version of components
Ambari trunk(3.0.0.0-SNAPSHOT)
Ambari metrics master(3.1.0-SNAPSHOT)
Bigtop 3.2.0
Opened grafana link, opened
ambari-server-jvm(http://host1:3000/d/ehbY5d84z/ambari-server-jvm?orgId=1)
dashboard, observed following error
{code:java}
An unexpected error happened
Details
TypeError: Cannot read properties of null (reading 'text')
at t (http://host1:3000/public/build/8310.56f209a52d089da1c262.js:8878:3025)
at g (http://host1:3000/public/build/9512.8fae0c667bb767d8cfd1.js:2:1042468)
at div
at en
(http://host1:3000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:150)
{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] [Created] (AMBARI-25941) Ambari grafana ams-hbase-home dashboard values are wrong
Mohammad Arshad created AMBARI-25941: Summary: Ambari grafana ams-hbase-home dashboard values are wrong Key: AMBARI-25941 URL: https://issues.apache.org/jira/browse/AMBARI-25941 Project: Ambari Issue Type: Bug Components: ambari-metrics Environment: Ambari trunk(3.0.0.0-SNAPSHOT) Ambari metrics master(3.1.0-SNAPSHOT) Bigtop 3.2.0 Reporter: Mohammad Arshad Assignee: Mohammad Arshad Attachments: image-2023-05-15-20-31-45-499.png I am installed only one ambari metrics collector, so there is only one region server, but ams-hbase-home dashboard is showing as 3.8. Similarly other metrics also in this dashboard are wrong !image-2023-05-15-20-31-45-499.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-25940) Ambari grafana ambari-server-jvm dashboard loading fails
[
https://issues.apache.org/jira/browse/AMBARI-25940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25940:
-
Component/s: ambari-metrics
(was: ambari-trunk)
> Ambari grafana ambari-server-jvm dashboard loading fails
>
>
> Key: AMBARI-25940
> URL: https://issues.apache.org/jira/browse/AMBARI-25940
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
>
> Installed hadoop cluster using ambari. Used following version of components
> Ambari trunk(3.0.0.0-SNAPSHOT)
> Ambari metrics master(3.1.0-SNAPSHOT)
> Bigtop 3.2.0
> Opened grafana link, opened
> ambari-server-jvm(http://host1:3000/d/ehbY5d84z/ambari-server-jvm?orgId=1)
> dashboard, observed following error
> {code:java}
> An unexpected error happened
> Details
> TypeError: Cannot read properties of null (reading 'text')
> at t
> (http://host1:3000/public/build/8310.56f209a52d089da1c262.js:8878:3025)
> at g
> (http://host1:3000/public/build/9512.8fae0c667bb767d8cfd1.js:2:1042468)
> at div
> at en
> (http://host1:3000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:150)
> {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] [Commented] (AMBARI-25936) Ambari metrics collector fails with IncompatibleClassChangeError, Found HdfsFileStatus but expected FanOutOneBlockAsyncDFSOutputHelper
[
https://issues.apache.org/jira/browse/AMBARI-25936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17722818#comment-17722818
]
Mohammad Arshad commented on AMBARI-25936:
--
In my environment ambari metrics build was using hbase from
https://archive.apache.org/dist/hbase/2.4.13/hbase-2.4.13-bin.tar.gz
After using hbase from
http://repo.bigtop.apache.org.s3.amazonaws.com/bigtop-stack-binary/3.2.0/centos-7/x86_64/hbase-2.4.13-bin.tar.gz,
the issue resolved.
> Ambari metrics collector fails with IncompatibleClassChangeError, Found
> HdfsFileStatus but expected FanOutOneBlockAsyncDFSOutputHelper
> --
>
> Key: AMBARI-25936
> URL: https://issues.apache.org/jira/browse/AMBARI-25936
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
>
> Built ambari trunk, ambari metrics master. Using bitop 3.2.0
> installed hadoop cluster using ambari,
> ambari metrics is failing with following errors
> {code:java}
> 2023-05-15 06:00:35,374 INFO [master/Host1:61300:becomeActiveMaster]
> wal.AbstractFSWAL: Closed WAL: AsyncFSWAL Host1%2C61300%2C1684130431341:(num
> 1684130435340)
> 2023-05-15 06:00:35,376 ERROR [master/Host1:61300:becomeActiveMaster]
> master.HMaster: Failed to become active master
> java.lang.IncompatibleClassChangeError: Found interface
> org.apache.hadoop.hdfs.protocol.HdfsFileStatus, but class was expected
> at
> org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:535)
> at
> org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.access$400(FanOutOneBlockAsyncDFSOutputHelper.java:112)
> at
> org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:615)
> at
> org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:610)
> at
> org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
> at
> org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:623)
> at
> org.apache.hadoop.hbase.io.asyncfs.AsyncFSOutputHelper.createOutput(AsyncFSOutputHelper.java:53)
> at
> org.apache.hadoop.hbase.regionserver.wal.AsyncProtobufLogWriter.initOutput(AsyncProtobufLogWriter.java:190)
> at
> org.apache.hadoop.hbase.regionserver.wal.AbstractProtobufLogWriter.init(AbstractProtobufLogWriter.java:160)
> at
> org.apache.hadoop.hbase.wal.AsyncFSWALProvider.createAsyncWriter(AsyncFSWALProvider.java:116)
> at
> org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:723)
> at
> org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:129)
> at
> org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:833)
> at
> org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:547)
> at
> org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.init(AbstractFSWAL.java:488)
> at
> org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:160)
> at
> org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:62)
> at org.apache.hadoop.hbase.wal.WALFactory.getWAL(WALFactory.java:295)
> at
> org.apache.hadoop.hbase.master.region.MasterRegion.createWAL(MasterRegion.java:200)
> at
> org.apache.hadoop.hbase.master.region.MasterRegion.open(MasterRegion.java:255)
> at
> org.apache.hadoop.hbase.master.region.MasterRegion.create(MasterRegion.java:336)
> at
> org.apache.hadoop.hbase.master.region.MasterRegionFactory.create(MasterRegionFactory.java:104)
> at
> org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:846)
> at
> org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2175)
> at
> org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:520)
> at java.lang.Thread.run(Thread.java:750)
> 2023-05-15 06:00:35,378 ERROR [master/Host1:61300:becomeActiveMaster]
> master.HMaster: * ABORTING master Host1,61300,1684130431341: Unhandled
> exception. Starting shutdown. *
> java.lang.IncompatibleClassChangeError: Found interface
> org.apache.hadoop.hdfs.protocol.HdfsFileStatus, but class was expected
> at
> org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.crea
[jira] [Resolved] (AMBARI-25936) Ambari metrics collector fails with IncompatibleClassChangeError, Found HdfsFileStatus but expected FanOutOneBlockAsyncDFSOutputHelper
[
https://issues.apache.org/jira/browse/AMBARI-25936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad resolved AMBARI-25936.
--
Resolution: Not A Problem
> Ambari metrics collector fails with IncompatibleClassChangeError, Found
> HdfsFileStatus but expected FanOutOneBlockAsyncDFSOutputHelper
> --
>
> Key: AMBARI-25936
> URL: https://issues.apache.org/jira/browse/AMBARI-25936
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
>
> Built ambari trunk, ambari metrics master. Using bitop 3.2.0
> installed hadoop cluster using ambari,
> ambari metrics is failing with following errors
> {code:java}
> 2023-05-15 06:00:35,374 INFO [master/Host1:61300:becomeActiveMaster]
> wal.AbstractFSWAL: Closed WAL: AsyncFSWAL Host1%2C61300%2C1684130431341:(num
> 1684130435340)
> 2023-05-15 06:00:35,376 ERROR [master/Host1:61300:becomeActiveMaster]
> master.HMaster: Failed to become active master
> java.lang.IncompatibleClassChangeError: Found interface
> org.apache.hadoop.hdfs.protocol.HdfsFileStatus, but class was expected
> at
> org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:535)
> at
> org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.access$400(FanOutOneBlockAsyncDFSOutputHelper.java:112)
> at
> org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:615)
> at
> org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOutputHelper.java:610)
> at
> org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
> at
> org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:623)
> at
> org.apache.hadoop.hbase.io.asyncfs.AsyncFSOutputHelper.createOutput(AsyncFSOutputHelper.java:53)
> at
> org.apache.hadoop.hbase.regionserver.wal.AsyncProtobufLogWriter.initOutput(AsyncProtobufLogWriter.java:190)
> at
> org.apache.hadoop.hbase.regionserver.wal.AbstractProtobufLogWriter.init(AbstractProtobufLogWriter.java:160)
> at
> org.apache.hadoop.hbase.wal.AsyncFSWALProvider.createAsyncWriter(AsyncFSWALProvider.java:116)
> at
> org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:723)
> at
> org.apache.hadoop.hbase.regionserver.wal.AsyncFSWAL.createWriterInstance(AsyncFSWAL.java:129)
> at
> org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:833)
> at
> org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.rollWriter(AbstractFSWAL.java:547)
> at
> org.apache.hadoop.hbase.regionserver.wal.AbstractFSWAL.init(AbstractFSWAL.java:488)
> at
> org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:160)
> at
> org.apache.hadoop.hbase.wal.AbstractFSWALProvider.getWAL(AbstractFSWALProvider.java:62)
> at org.apache.hadoop.hbase.wal.WALFactory.getWAL(WALFactory.java:295)
> at
> org.apache.hadoop.hbase.master.region.MasterRegion.createWAL(MasterRegion.java:200)
> at
> org.apache.hadoop.hbase.master.region.MasterRegion.open(MasterRegion.java:255)
> at
> org.apache.hadoop.hbase.master.region.MasterRegion.create(MasterRegion.java:336)
> at
> org.apache.hadoop.hbase.master.region.MasterRegionFactory.create(MasterRegionFactory.java:104)
> at
> org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:846)
> at
> org.apache.hadoop.hbase.master.HMaster.startActiveMasterManager(HMaster.java:2175)
> at
> org.apache.hadoop.hbase.master.HMaster.lambda$run$0(HMaster.java:520)
> at java.lang.Thread.run(Thread.java:750)
> 2023-05-15 06:00:35,378 ERROR [master/Host1:61300:becomeActiveMaster]
> master.HMaster: * ABORTING master Host1,61300,1684130431341: Unhandled
> exception. Starting shutdown. *
> java.lang.IncompatibleClassChangeError: Found interface
> org.apache.hadoop.hdfs.protocol.HdfsFileStatus, but class was expected
> at
> org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.createOutput(FanOutOneBlockAsyncDFSOutputHelper.java:535)
> at
> org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper.access$400(FanOutOneBlockAsyncDFSOutputHelper.java:112)
> at
> org.apache.hadoop.hbase.io.asyncfs.FanOutOneBlockAsyncDFSOutputHelper$8.doCall(FanOutOneBlockAsyncDFSOu
[jira] [Updated] (AMBARI-25941) Ambari grafana ams-hbase-home dashboard values are wrong
[ https://issues.apache.org/jira/browse/AMBARI-25941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25941: - Description: I have installed only one ambari metrics collector, so there is only one region server, but ams-hbase-home dashboard is showing as 3.8. Similarly other metrics also in this dashboard are wrong !image-2023-05-15-20-31-45-499.png! was: I am installed only one ambari metrics collector, so there is only one region server, but ams-hbase-home dashboard is showing as 3.8. Similarly other metrics also in this dashboard are wrong !image-2023-05-15-20-31-45-499.png! > Ambari grafana ams-hbase-home dashboard values are wrong > > > Key: AMBARI-25941 > URL: https://issues.apache.org/jira/browse/AMBARI-25941 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics > Environment: Ambari trunk(3.0.0.0-SNAPSHOT) > Ambari metrics master(3.1.0-SNAPSHOT) > Bigtop 3.2.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: image-2023-05-15-20-31-45-499.png > > > I have installed only one ambari metrics collector, so there is only one > region server, but ams-hbase-home dashboard is showing as 3.8. > Similarly other metrics also in this dashboard are wrong > !image-2023-05-15-20-31-45-499.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] [Created] (AMBARI-25943) Hive metastore is not publishing metrics
Mohammad Arshad created AMBARI-25943: Summary: Hive metastore is not publishing metrics Key: AMBARI-25943 URL: https://issues.apache.org/jira/browse/AMBARI-25943 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: metrics-3.0.0 Environment: Ambari trunk(3.0.0.0-SNAPSHOT) Ambari metrics master(3.1.0-SNAPSHOT) Bigtop 3.2.0, Hive 3.1.3 Reporter: Mohammad Arshad Assignee: Mohammad Arshad Attachments: image-2023-05-17-08-59-22-472.png In Ambari Web UI by default following configurations are there !image-2023-05-17-08-59-22-472.png|thumbnail! Inspite of above configuration hive metastore is not emitting the 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] [Commented] (AMBARI-25943) Hive metastore is not publishing metrics
[ https://issues.apache.org/jira/browse/AMBARI-25943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723331#comment-17723331 ] Mohammad Arshad commented on AMBARI-25943: -- hive.service.metrics.hadoop2.component is configured but hive code is not using this configuration. Hive code to be changed to fix the issue > Hive metastore is not publishing metrics > > > Key: AMBARI-25943 > URL: https://issues.apache.org/jira/browse/AMBARI-25943 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 > Environment: Ambari trunk(3.0.0.0-SNAPSHOT) > Ambari metrics master(3.1.0-SNAPSHOT) > Bigtop 3.2.0, Hive 3.1.3 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: image-2023-05-17-08-59-22-472.png > > > In Ambari Web UI by default following configurations are there > !image-2023-05-17-08-59-22-472.png|thumbnail! > Inspite of above configuration hive metastore is not emitting the 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] [Created] (AMBARI-25944) Update dashboard definition when dashboard version is changed
Mohammad Arshad created AMBARI-25944: Summary: Update dashboard definition when dashboard version is changed Key: AMBARI-25944 URL: https://issues.apache.org/jira/browse/AMBARI-25944 Project: Ambari Issue Type: Bug Reporter: Mohammad Arshad Assignee: Mohammad Arshad Currently when ambari-metrics grafana starts, it updates dashboard definition only if ambari version is changed. dashboard definition should also be updated if dashboard version is 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-25944) Update dashboard definition when dashboard version is changed
[ https://issues.apache.org/jira/browse/AMBARI-25944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25944: - Component/s: ambari-metrics > Update dashboard definition when dashboard version is changed > - > > Key: AMBARI-25944 > URL: https://issues.apache.org/jira/browse/AMBARI-25944 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > > Currently when ambari-metrics grafana starts, it updates dashboard definition > only if ambari version is changed. > dashboard definition should also be updated if dashboard version is 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] [Commented] (AMBARI-25944) Update dashboard definition when dashboard version is changed
[ https://issues.apache.org/jira/browse/AMBARI-25944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723812#comment-17723812 ] Mohammad Arshad commented on AMBARI-25944: -- To solve above problem like ambari version we should also add dashboard version as tag and during the ambari-metrics-grafana start compare the dashboard version as well same as the ambari version is being compared. > Update dashboard definition when dashboard version is changed > - > > Key: AMBARI-25944 > URL: https://issues.apache.org/jira/browse/AMBARI-25944 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > > Currently when ambari-metrics grafana starts, it updates dashboard definition > only if ambari version is changed. > dashboard definition should also be updated if dashboard version is 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] [Commented] (AMBARI-25944) Update dashboard definition when dashboard version is changed
[ https://issues.apache.org/jira/browse/AMBARI-25944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723814#comment-17723814 ] Mohammad Arshad commented on AMBARI-25944: -- After implementation the looks like this: !screenshot-1.png! > Update dashboard definition when dashboard version is changed > - > > Key: AMBARI-25944 > URL: https://issues.apache.org/jira/browse/AMBARI-25944 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: screenshot-1.png > > > Currently when ambari-metrics grafana starts, it updates dashboard definition > only if ambari version is changed. > dashboard definition should also be updated if dashboard version is 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-25944) Update dashboard definition when dashboard version is changed
[ https://issues.apache.org/jira/browse/AMBARI-25944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25944: - Attachment: screenshot-1.png > Update dashboard definition when dashboard version is changed > - > > Key: AMBARI-25944 > URL: https://issues.apache.org/jira/browse/AMBARI-25944 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: screenshot-1.png > > > Currently when ambari-metrics grafana starts, it updates dashboard definition > only if ambari version is changed. > dashboard definition should also be updated if dashboard version is 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] [Commented] (AMBARI-25944) Update dashboard definition when dashboard version is changed
[
https://issues.apache.org/jira/browse/AMBARI-25944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723816#comment-17723816
]
Mohammad Arshad commented on AMBARI-25944:
--
During the ambari-metrics-grafana start following message is logged
{noformat}
2023-05-18 07:10:18,751 - Dashboard definition for AMS HBase - RegionServers
with tags: ['3.0.0.0', '6', 'ams-hbase', 'builtin'] will be updated as the
dashboard version is changed to 7
{noformat}
> Update dashboard definition when dashboard version is changed
> -
>
> Key: AMBARI-25944
> URL: https://issues.apache.org/jira/browse/AMBARI-25944
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Attachments: screenshot-1.png
>
>
> Currently when ambari-metrics grafana starts, it updates dashboard definition
> only if ambari version is changed.
> dashboard definition should also be updated if dashboard version is 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] [Created] (AMBARI-25945) Sync batch size in ambari metrics collector and ams hbase
Mohammad Arshad created AMBARI-25945:
Summary: Sync batch size in ambari metrics collector and ams hbase
Key: AMBARI-25945
URL: https://issues.apache.org/jira/browse/AMBARI-25945
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: metrics-3.0.0
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
In metrics collector phoenix batch size is 1, but in ams hbase batch size
is 5000. Because of this following warning message is constantly getting logged
{noformat}
2023-05-19 05:49:04,899 WARN
[RpcServer.default.FPBQ.Fifo.handler=28,queue=1,port=61320]
regionserver.RSRpcServices: Large batch operation detected (greater than 5000)
(HBASE-18023). Requested Number of Rows: 5690 Client: ams//IP first region in
multi=METRIC_RECORD_MINUTE_UUID,,1684154511984.1a0cc25ec53f3475ff282a47dc9d03b7.
2023-05-19 05:50:05,136 WARN
[RpcServer.default.FPBQ.Fifo.handler=21,queue=0,port=61320]
regionserver.RSRpcServices: Large batch operation detected (greater than 5000)
(HBASE-18023). Requested Number of Rows: 1 Client: ams//IP first region in
multi=METRIC_AGGREGATE_UUID,,1684154515075.77371e2960a2ce70bb15d223338ba893.
{noformat}
To fix this problem, either we should decrease phoenix batch size in collector
in increase batch size in ams hbase.
I propose to increase the batch size in ams hbase
--
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-25940) Ambari grafana ambari-server-jvm dashboard loading fails
[
https://issues.apache.org/jira/browse/AMBARI-25940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25940:
-
Attachment: screenshot-1.png
> Ambari grafana ambari-server-jvm dashboard loading fails
>
>
> Key: AMBARI-25940
> URL: https://issues.apache.org/jira/browse/AMBARI-25940
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Attachments: screenshot-1.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Installed hadoop cluster using ambari. Used following version of components
> Ambari trunk(3.0.0.0-SNAPSHOT)
> Ambari metrics master(3.1.0-SNAPSHOT)
> Bigtop 3.2.0
> Opened grafana link, opened
> ambari-server-jvm(http://host1:3000/d/ehbY5d84z/ambari-server-jvm?orgId=1)
> dashboard, observed following error
> {code:java}
> An unexpected error happened
> Details
> TypeError: Cannot read properties of null (reading 'text')
> at t
> (http://host1:3000/public/build/8310.56f209a52d089da1c262.js:8878:3025)
> at g
> (http://host1:3000/public/build/9512.8fae0c667bb767d8cfd1.js:2:1042468)
> at div
> at en
> (http://host1:3000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:150)
> {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] [Commented] (AMBARI-25940) Ambari grafana ambari-server-jvm dashboard loading fails
[
https://issues.apache.org/jira/browse/AMBARI-25940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17734215#comment-17734215
]
Mohammad Arshad commented on AMBARI-25940:
--
After the changes ambari-server-jvm dashboard loads successfully
!screenshot-1.png!
> Ambari grafana ambari-server-jvm dashboard loading fails
>
>
> Key: AMBARI-25940
> URL: https://issues.apache.org/jira/browse/AMBARI-25940
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Attachments: screenshot-1.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Installed hadoop cluster using ambari. Used following version of components
> Ambari trunk(3.0.0.0-SNAPSHOT)
> Ambari metrics master(3.1.0-SNAPSHOT)
> Bigtop 3.2.0
> Opened grafana link, opened
> ambari-server-jvm(http://host1:3000/d/ehbY5d84z/ambari-server-jvm?orgId=1)
> dashboard, observed following error
> {code:java}
> An unexpected error happened
> Details
> TypeError: Cannot read properties of null (reading 'text')
> at t
> (http://host1:3000/public/build/8310.56f209a52d089da1c262.js:8878:3025)
> at g
> (http://host1:3000/public/build/9512.8fae0c667bb767d8cfd1.js:2:1042468)
> at div
> at en
> (http://host1:3000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:150)
> {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-25941) Ambari grafana ams-hbase-home dashboard values are wrong
[ https://issues.apache.org/jira/browse/AMBARI-25941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25941: - Attachment: screenshot-1.png > Ambari grafana ams-hbase-home dashboard values are wrong > > > Key: AMBARI-25941 > URL: https://issues.apache.org/jira/browse/AMBARI-25941 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics > Environment: Ambari trunk(3.0.0.0-SNAPSHOT) > Ambari metrics master(3.1.0-SNAPSHOT) > Bigtop 3.2.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: image-2023-05-15-20-31-45-499.png, screenshot-1.png > > > I have installed only one ambari metrics collector, so there is only one > region server, but ams-hbase-home dashboard is showing as 3.8. > Similarly other metrics also in this dashboard are wrong > !image-2023-05-15-20-31-45-499.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] [Commented] (AMBARI-25941) Ambari grafana ams-hbase-home dashboard values are wrong
[ https://issues.apache.org/jira/browse/AMBARI-25941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17734233#comment-17734233 ] Mohammad Arshad commented on AMBARI-25941: -- Data is wrong because wrong data source is used. It is not Ambari Metrics data source but instead it is using -Grafana- data source, I think which is generating some random data !screenshot-1.png! > Ambari grafana ams-hbase-home dashboard values are wrong > > > Key: AMBARI-25941 > URL: https://issues.apache.org/jira/browse/AMBARI-25941 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics > Environment: Ambari trunk(3.0.0.0-SNAPSHOT) > Ambari metrics master(3.1.0-SNAPSHOT) > Bigtop 3.2.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: image-2023-05-15-20-31-45-499.png, screenshot-1.png > > > I have installed only one ambari metrics collector, so there is only one > region server, but ams-hbase-home dashboard is showing as 3.8. > Similarly other metrics also in this dashboard are wrong > !image-2023-05-15-20-31-45-499.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] [Commented] (AMBARI-25941) Ambari grafana ams-hbase-home dashboard values are wrong
[
https://issues.apache.org/jira/browse/AMBARI-25941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735158#comment-17735158
]
Mohammad Arshad commented on AMBARI-25941:
--
ambari-metrics plugin loading is failed, that is why ambari metrics data source
is not available
{noformat}
logger=plugin.loader t=2023-06-19T17:16:13.302431806Z level=info msg="Plugin
registered" pluginID=input
logger=plugin.loader t=2023-06-19T17:16:13.302975813Z level=warn msg="Skipping
loading plugin due to problem with signature" pluginID=ambari-metrics
status=unsigned {noformat}
> Ambari grafana ams-hbase-home dashboard values are wrong
>
>
> Key: AMBARI-25941
> URL: https://issues.apache.org/jira/browse/AMBARI-25941
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
> Environment: Ambari trunk(3.0.0.0-SNAPSHOT)
> Ambari metrics master(3.1.0-SNAPSHOT)
> Bigtop 3.2.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Attachments: image-2023-05-15-20-31-45-499.png, screenshot-1.png
>
>
> I have installed only one ambari metrics collector, so there is only one
> region server, but ams-hbase-home dashboard is showing as 3.8.
> Similarly other metrics also in this dashboard are wrong
> !image-2023-05-15-20-31-45-499.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] [Created] (AMBARI-25957) Ambari Metrics Grafana Datasource plugin is not working
Mohammad Arshad created AMBARI-25957: Summary: Ambari Metrics Grafana Datasource plugin is not working Key: AMBARI-25957 URL: https://issues.apache.org/jira/browse/AMBARI-25957 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: metrics-3.0.0 Reporter: Mohammad Arshad Assignee: Mohammad Arshad Attachments: image-2023-06-20-12-27-00-113.png Ambari Metrics Grafana Datasource plugin is not working. Data is blank in dashboards, following errors are logged in browser console !image-2023-06-20-12-27-00-113.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] [Commented] (AMBARI-25957) Ambari Metrics Grafana Datasource plugin is not working
[ https://issues.apache.org/jira/browse/AMBARI-25957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735161#comment-17735161 ] Mohammad Arshad commented on AMBARI-25957: -- Seems AMBARI-20391 fixed this issue in branch-2. We should take that change in metrics master branch as well. > Ambari Metrics Grafana Datasource plugin is not working > --- > > Key: AMBARI-25957 > URL: https://issues.apache.org/jira/browse/AMBARI-25957 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: image-2023-06-20-12-27-00-113.png > > > Ambari Metrics Grafana Datasource plugin is not working. Data is blank in > dashboards, following errors are logged in browser console > > !image-2023-06-20-12-27-00-113.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-25941) Ambari grafana ams-hbase-home dashboard values are wrong
[ https://issues.apache.org/jira/browse/AMBARI-25941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25941: - Attachment: image-2023-06-20-13-33-14-546.png > Ambari grafana ams-hbase-home dashboard values are wrong > > > Key: AMBARI-25941 > URL: https://issues.apache.org/jira/browse/AMBARI-25941 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics > Environment: Ambari trunk(3.0.0.0-SNAPSHOT) > Ambari metrics master(3.1.0-SNAPSHOT) > Bigtop 3.2.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: image-2023-05-15-20-31-45-499.png, > image-2023-06-20-13-33-14-546.png, screenshot-1.png > > > I have installed only one ambari metrics collector, so there is only one > region server, but ams-hbase-home dashboard is showing as 3.8. > Similarly other metrics also in this dashboard are wrong > !image-2023-05-15-20-31-45-499.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] [Commented] (AMBARI-25941) Ambari grafana ams-hbase-home dashboard values are wrong
[ https://issues.apache.org/jira/browse/AMBARI-25941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735173#comment-17735173 ] Mohammad Arshad commented on AMBARI-25941: -- After fix, following configuration gets added by default and ambari metrics data source plugin is loaded successfully !image-2023-06-20-13-33-14-546.png! > Ambari grafana ams-hbase-home dashboard values are wrong > > > Key: AMBARI-25941 > URL: https://issues.apache.org/jira/browse/AMBARI-25941 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics > Environment: Ambari trunk(3.0.0.0-SNAPSHOT) > Ambari metrics master(3.1.0-SNAPSHOT) > Bigtop 3.2.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: image-2023-05-15-20-31-45-499.png, > image-2023-06-20-13-33-14-546.png, screenshot-1.png > > > I have installed only one ambari metrics collector, so there is only one > region server, but ams-hbase-home dashboard is showing as 3.8. > Similarly other metrics also in this dashboard are wrong > !image-2023-05-15-20-31-45-499.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-25941) Metrics Grafana Datasource plugin is not loading
[ https://issues.apache.org/jira/browse/AMBARI-25941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25941: - Summary: Metrics Grafana Datasource plugin is not loading (was: Ambari grafana ams-hbase-home dashboard values are wrong) > Metrics Grafana Datasource plugin is not loading > > > Key: AMBARI-25941 > URL: https://issues.apache.org/jira/browse/AMBARI-25941 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics > Environment: Ambari trunk(3.0.0.0-SNAPSHOT) > Ambari metrics master(3.1.0-SNAPSHOT) > Bigtop 3.2.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: image-2023-05-15-20-31-45-499.png, > image-2023-06-20-13-33-14-546.png, screenshot-1.png > > > I have installed only one ambari metrics collector, so there is only one > region server, but ams-hbase-home dashboard is showing as 3.8. > Similarly other metrics also in this dashboard are wrong > !image-2023-05-15-20-31-45-499.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-25957) Ambari Metrics Grafana Datasource plugin is not working
[ https://issues.apache.org/jira/browse/AMBARI-25957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25957: - Attachment: image-2023-06-20-16-36-00-878.png > Ambari Metrics Grafana Datasource plugin is not working > --- > > Key: AMBARI-25957 > URL: https://issues.apache.org/jira/browse/AMBARI-25957 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: image-2023-06-20-12-27-00-113.png, > image-2023-06-20-16-36-00-878.png > > > Ambari Metrics Grafana Datasource plugin is not working. Data is blank in > dashboards, following errors are logged in browser console > > !image-2023-06-20-12-27-00-113.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] [Commented] (AMBARI-25957) Ambari Metrics Grafana Datasource plugin is not working
[ https://issues.apache.org/jira/browse/AMBARI-25957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735248#comment-17735248 ] Mohammad Arshad commented on AMBARI-25957: -- After fix, ambari metrics data source working fine. Fetched data from collector successfully. !image-2023-06-20-16-36-00-878.png! > Ambari Metrics Grafana Datasource plugin is not working > --- > > Key: AMBARI-25957 > URL: https://issues.apache.org/jira/browse/AMBARI-25957 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: image-2023-06-20-12-27-00-113.png, > image-2023-06-20-16-36-00-878.png > > > Ambari Metrics Grafana Datasource plugin is not working. Data is blank in > dashboards, following errors are logged in browser console > > !image-2023-06-20-12-27-00-113.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-25957) Ambari Metrics Grafana Datasource is not working
[ https://issues.apache.org/jira/browse/AMBARI-25957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25957: - Summary: Ambari Metrics Grafana Datasource is not working (was: Ambari Metrics Grafana Datasource plugin is not working) > Ambari Metrics Grafana Datasource is not working > > > Key: AMBARI-25957 > URL: https://issues.apache.org/jira/browse/AMBARI-25957 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: image-2023-06-20-12-27-00-113.png, > image-2023-06-20-16-36-00-878.png > > > Ambari Metrics Grafana Datasource plugin is not working. Data is blank in > dashboards, following errors are logged in browser console > > !image-2023-06-20-12-27-00-113.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] [Commented] (AMBARI-25944) Update dashboard definition when dashboard version is changed
[ https://issues.apache.org/jira/browse/AMBARI-25944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735254#comment-17735254 ] Mohammad Arshad commented on AMBARI-25944: -- Thanks [~vjasani] for reviewing and merging the PR. > Update dashboard definition when dashboard version is changed > - > > Key: AMBARI-25944 > URL: https://issues.apache.org/jira/browse/AMBARI-25944 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Fix For: 2.8.0 > > Attachments: screenshot-1.png > > Time Spent: 20m > Remaining Estimate: 0h > > Currently when ambari-metrics grafana starts, it updates dashboard definition > only if ambari version is changed. > dashboard definition should also be updated if dashboard version is 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-25945) Sync batch size in ambari metrics collector and ams hbase
[
https://issues.apache.org/jira/browse/AMBARI-25945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25945:
-
Description:
In metrics collector phoenix batch size is 1, but in ams hbase batch size
is 5000. Because of this following warning message is constantly getting logged
{noformat}
2023-05-19 05:49:04,899 WARN
[RpcServer.default.FPBQ.Fifo.handler=28,queue=1,port=61320]
regionserver.RSRpcServices: Large batch operation detected (greater than 5000)
(HBASE-18023). Requested Number of Rows: 5690 Client: ams//IP first region in
multi=METRIC_RECORD_MINUTE_UUID,,1684154511984.1a0cc25ec53f3475ff282a47dc9d03b7.
2023-05-19 05:50:05,136 WARN
[RpcServer.default.FPBQ.Fifo.handler=21,queue=0,port=61320]
regionserver.RSRpcServices: Large batch operation detected (greater than 5000)
(HBASE-18023). Requested Number of Rows: 1 Client: ams//IP first region in
multi=METRIC_AGGREGATE_UUID,,1684154515075.77371e2960a2ce70bb15d223338ba893.
{noformat}
To fix this problem, either we should decrease phoenix batch size in collector
or increase batch size in ams hbase.
I propose to increase the batch size in ams hbase
was:
In metrics collector phoenix batch size is 1, but in ams hbase batch size
is 5000. Because of this following warning message is constantly getting logged
{noformat}
2023-05-19 05:49:04,899 WARN
[RpcServer.default.FPBQ.Fifo.handler=28,queue=1,port=61320]
regionserver.RSRpcServices: Large batch operation detected (greater than 5000)
(HBASE-18023). Requested Number of Rows: 5690 Client: ams//IP first region in
multi=METRIC_RECORD_MINUTE_UUID,,1684154511984.1a0cc25ec53f3475ff282a47dc9d03b7.
2023-05-19 05:50:05,136 WARN
[RpcServer.default.FPBQ.Fifo.handler=21,queue=0,port=61320]
regionserver.RSRpcServices: Large batch operation detected (greater than 5000)
(HBASE-18023). Requested Number of Rows: 1 Client: ams//IP first region in
multi=METRIC_AGGREGATE_UUID,,1684154515075.77371e2960a2ce70bb15d223338ba893.
{noformat}
To fix this problem, either we should decrease phoenix batch size in collector
in increase batch size in ams hbase.
I propose to increase the batch size in ams hbase
> Sync batch size in ambari metrics collector and ams hbase
> -
>
> Key: AMBARI-25945
> URL: https://issues.apache.org/jira/browse/AMBARI-25945
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
>
> In metrics collector phoenix batch size is 1, but in ams hbase batch size
> is 5000. Because of this following warning message is constantly getting
> logged
> {noformat}
> 2023-05-19 05:49:04,899 WARN
> [RpcServer.default.FPBQ.Fifo.handler=28,queue=1,port=61320]
> regionserver.RSRpcServices: Large batch operation detected (greater than
> 5000) (HBASE-18023). Requested Number of Rows: 5690 Client: ams//IP first
> region in
> multi=METRIC_RECORD_MINUTE_UUID,,1684154511984.1a0cc25ec53f3475ff282a47dc9d03b7.
> 2023-05-19 05:50:05,136 WARN
> [RpcServer.default.FPBQ.Fifo.handler=21,queue=0,port=61320]
> regionserver.RSRpcServices: Large batch operation detected (greater than
> 5000) (HBASE-18023). Requested Number of Rows: 1 Client: ams//IP first
> region in
> multi=METRIC_AGGREGATE_UUID,,1684154515075.77371e2960a2ce70bb15d223338ba893.
> {noformat}
> To fix this problem, either we should decrease phoenix batch size in
> collector or increase batch size in ams hbase.
> I propose to increase the batch size in ams hbase
--
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-25945) Sync batch size in ambari metrics collector and ams hbase
[
https://issues.apache.org/jira/browse/AMBARI-25945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25945:
-
Attachment: image-2023-06-20-18-36-37-450.png
> Sync batch size in ambari metrics collector and ams hbase
> -
>
> Key: AMBARI-25945
> URL: https://issues.apache.org/jira/browse/AMBARI-25945
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Attachments: image-2023-06-20-18-36-37-450.png
>
>
> In metrics collector phoenix batch size is 1, but in ams hbase batch size
> is 5000. Because of this following warning message is constantly getting
> logged
> {noformat}
> 2023-05-19 05:49:04,899 WARN
> [RpcServer.default.FPBQ.Fifo.handler=28,queue=1,port=61320]
> regionserver.RSRpcServices: Large batch operation detected (greater than
> 5000) (HBASE-18023). Requested Number of Rows: 5690 Client: ams//IP first
> region in
> multi=METRIC_RECORD_MINUTE_UUID,,1684154511984.1a0cc25ec53f3475ff282a47dc9d03b7.
> 2023-05-19 05:50:05,136 WARN
> [RpcServer.default.FPBQ.Fifo.handler=21,queue=0,port=61320]
> regionserver.RSRpcServices: Large batch operation detected (greater than
> 5000) (HBASE-18023). Requested Number of Rows: 1 Client: ams//IP first
> region in
> multi=METRIC_AGGREGATE_UUID,,1684154515075.77371e2960a2ce70bb15d223338ba893.
> {noformat}
> To fix this problem, either we should decrease phoenix batch size in
> collector or increase batch size in ams hbase.
> I propose to increase the batch size in ams hbase
--
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-25945) Sync batch size in ambari metrics collector and ams hbase
[
https://issues.apache.org/jira/browse/AMBARI-25945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735282#comment-17735282
]
Mohammad Arshad commented on AMBARI-25945:
--
Added hbase.rpc.rows.warning.threshold in section Advanced ams-hbase-site with
default value as 1
!image-2023-06-20-18-36-37-450.png!
> Sync batch size in ambari metrics collector and ams hbase
> -
>
> Key: AMBARI-25945
> URL: https://issues.apache.org/jira/browse/AMBARI-25945
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Attachments: image-2023-06-20-18-36-37-450.png
>
>
> In metrics collector phoenix batch size is 1, but in ams hbase batch size
> is 5000. Because of this following warning message is constantly getting
> logged
> {noformat}
> 2023-05-19 05:49:04,899 WARN
> [RpcServer.default.FPBQ.Fifo.handler=28,queue=1,port=61320]
> regionserver.RSRpcServices: Large batch operation detected (greater than
> 5000) (HBASE-18023). Requested Number of Rows: 5690 Client: ams//IP first
> region in
> multi=METRIC_RECORD_MINUTE_UUID,,1684154511984.1a0cc25ec53f3475ff282a47dc9d03b7.
> 2023-05-19 05:50:05,136 WARN
> [RpcServer.default.FPBQ.Fifo.handler=21,queue=0,port=61320]
> regionserver.RSRpcServices: Large batch operation detected (greater than
> 5000) (HBASE-18023). Requested Number of Rows: 1 Client: ams//IP first
> region in
> multi=METRIC_AGGREGATE_UUID,,1684154515075.77371e2960a2ce70bb15d223338ba893.
> {noformat}
> To fix this problem, either we should decrease phoenix batch size in
> collector or increase batch size in ams hbase.
> I propose to increase the batch size in ams hbase
--
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-25958) Ambari metrics returns Infinity when rate transformation is used
Mohammad Arshad created AMBARI-25958:
Summary: Ambari metrics returns Infinity when rate transformation
is used
Key: AMBARI-25958
URL: https://issues.apache.org/jira/browse/AMBARI-25958
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: metrics-3.0.0
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
rate metrics for example jvm.JvmMetrics.GcTimeMillis._rate some times give
value as Infinity. This is incorrect.
For example invoking below URL returned Infinity along with other values
http://{\{HOST_PORT}}/ws/v1/timeline/metrics?metricNames=jvm.JvmMetrics.GcTimeMillis._rate&precision=seconds&grouped=true&startTime=1686815115333&appId=hbase&endTime=1686815945333
Output:
{noformat}
1686796983505:679
1686797040051: 0.8214285714285714
1686797040144:"Infinity"
1686797042427:55
1686797043504:2027
1686797100144:"Infinity"
1686797102426:55{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] [Commented] (AMBARI-25958) Ambari metrics returns Infinity when rate transformation is used
[
https://issues.apache.org/jira/browse/AMBARI-25958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735323#comment-17735323
]
Mohammad Arshad commented on AMBARI-25958:
--
When time interval is less than 1000 ms following code in class
org.apache.ambari.metrics.core.timeline.HBaseTimelineMetricsService is causing
division by 0
{code:java}
Double rate = isDiff ? diff : (diff / TimeUnit.MILLISECONDS.toSeconds(step));
timeValueEntry.setValue(rate);
{code}
When step is less than 1000, TimeUnit.MILLISECONDS.toSeconds(step)) returns 0,
resulting in devision by 0 which give value Infinity
> Ambari metrics returns Infinity when rate transformation is used
>
>
> Key: AMBARI-25958
> URL: https://issues.apache.org/jira/browse/AMBARI-25958
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
>
> rate metrics for example jvm.JvmMetrics.GcTimeMillis._rate some times give
> value as Infinity. This is incorrect.
> For example invoking below URL returned Infinity along with other values
> http://{\{HOST_PORT}}/ws/v1/timeline/metrics?metricNames=jvm.JvmMetrics.GcTimeMillis._rate&precision=seconds&grouped=true&startTime=1686815115333&appId=hbase&endTime=1686815945333
>
> Output:
> {noformat}
> 1686796983505:679
> 1686797040051: 0.8214285714285714
> 1686797040144:"Infinity"
> 1686797042427:55
> 1686797043504:2027
> 1686797100144:"Infinity"
> 1686797102426:55{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] [Created] (AMBARI-25959) Ambari Metrics Grafana rpm missing some grafana tarball files
Mohammad Arshad created AMBARI-25959: Summary: Ambari Metrics Grafana rpm missing some grafana tarball files Key: AMBARI-25959 URL: https://issues.apache.org/jira/browse/AMBARI-25959 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: metrics-3.0.0 Reporter: Mohammad Arshad Assignee: Mohammad Arshad grafana-9.3.2.linux-amd64.tar.gz is extracted in folder ambari-metrics-grafana/target/grafana/grafana-9.3.2 then all files inside grafana-9.3.2 are used while building the rpm. But while extracting grafana-9.3.2.linux-amd64.tar.gz some files are getting extracted in inside ambari-metrics-grafana/target/grafana which then are not part of the rpm Grafana tarball extraction script to be changed so all files are placed inside correct folder. -- 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-25960) Add component grafana dashboards in ambari metrics
Mohammad Arshad created AMBARI-25960: Summary: Add component grafana dashboards in ambari metrics Key: AMBARI-25960 URL: https://issues.apache.org/jira/browse/AMBARI-25960 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: metrics-3.0.0 Reporter: Mohammad Arshad Assignee: Mohammad Arshad Component grafana dashboards are missing from ambari-metrics 3.0.0 These dashboards are available in ambari branch-2 ambari metrics and are really useful. Add back all BIGTO supported component grafana dashboards from ambari branch-2 to ambari trunk -- 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-25960) Add component grafana dashboards in ambari metrics
[ https://issues.apache.org/jira/browse/AMBARI-25960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735645#comment-17735645 ] Mohammad Arshad commented on AMBARI-25960: -- After the fix, all component dashboards are available !image-2023-06-21-15-35-39-217.png! > Add component grafana dashboards in ambari metrics > -- > > Key: AMBARI-25960 > URL: https://issues.apache.org/jira/browse/AMBARI-25960 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: image-2023-06-21-15-35-39-217.png > > Time Spent: 10m > Remaining Estimate: 0h > > Component grafana dashboards are missing from ambari-metrics 3.0.0 > These dashboards are available in ambari branch-2 ambari metrics and are > really useful. > Add back all BIGTO supported component grafana dashboards from ambari > branch-2 to ambari trunk > -- 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-25960) Add component grafana dashboards in ambari metrics
[ https://issues.apache.org/jira/browse/AMBARI-25960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Arshad updated AMBARI-25960: - Attachment: image-2023-06-21-15-35-39-217.png > Add component grafana dashboards in ambari metrics > -- > > Key: AMBARI-25960 > URL: https://issues.apache.org/jira/browse/AMBARI-25960 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Attachments: image-2023-06-21-15-35-39-217.png > > Time Spent: 10m > Remaining Estimate: 0h > > Component grafana dashboards are missing from ambari-metrics 3.0.0 > These dashboards are available in ambari branch-2 ambari metrics and are > really useful. > Add back all BIGTO supported component grafana dashboards from ambari > branch-2 to ambari trunk > -- 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-25962) Host apps metadata is not synced to other collectors when multiple metrics collectors are installed
Mohammad Arshad created AMBARI-25962:
Summary: Host apps metadata is not synced to other collectors when
multiple metrics collectors are installed
Key: AMBARI-25962
URL: https://issues.apache.org/jira/browse/AMBARI-25962
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: metrics-3.0.0
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
Host apps metadata is not synced to other collectors when multiple metrics
collectors are installed.
*Steps to reproduce the issue:*
# Install ambari metrics with two collector C1 and C2
# Submit following metrics through collector C1
{code:java}
{
"metrics": [
{
"metricname": "cpu",
"appid": "skywalking",
"hostname": "hostXYZ",
"starttime": 1687849289558,
"metrics": {
"1687849289558": 100,
"1687849295558": 200
}
}
]
}
{code}
# http://COLLECTOR_C1_HOST:6188/ws/v1/timeline/metrics/hosts API call returns
{noformat}
{
"hostXYZ": [
"datanode",
"HOST",
"namenode",
"skywalking",
"ams-hbase"
],
...
}
{noformat}
This is as expected.
# http://COLLECTOR_C2_HOST:6188/ws/v1/timeline/metrics/hosts API call returns
{noformat}
{
"hostXYZ": [
"datanode",
"HOST",
"namenode",
"ams-hbase"
],
...
}
{noformat}
This output indicates that new appid skywalking is not getting synced to other
collector C2. This new appid is not getting synced even after 5 minutes which
is the default ambari metrics metadata sync 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-25962) Host apps metadata is not synced to other collectors when multiple collectors are installed
[
https://issues.apache.org/jira/browse/AMBARI-25962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25962:
-
Summary: Host apps metadata is not synced to other collectors when multiple
collectors are installed (was: Host apps metadata is not synced to other
collectors when multiple metrics collectors are installed)
> Host apps metadata is not synced to other collectors when multiple collectors
> are installed
> ---
>
> Key: AMBARI-25962
> URL: https://issues.apache.org/jira/browse/AMBARI-25962
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Critical
>
> Host apps metadata is not synced to other collectors when multiple metrics
> collectors are installed.
> *Steps to reproduce the issue:*
> # Install ambari metrics with two collector C1 and C2
> # Submit following metrics through collector C1
> {code:java}
> {
> "metrics": [
> {
> "metricname": "cpu",
> "appid": "skywalking",
> "hostname": "hostXYZ",
> "starttime": 1687849289558,
> "metrics": {
> "1687849289558": 100,
> "1687849295558": 200
> }
> }
> ]
> }
> {code}
> # http://COLLECTOR_C1_HOST:6188/ws/v1/timeline/metrics/hosts API call returns
> {noformat}
> {
> "hostXYZ": [
> "datanode",
> "HOST",
> "namenode",
> "skywalking",
> "ams-hbase"
> ],
> ...
> }
> {noformat}
> This is as expected.
> # http://COLLECTOR_C2_HOST:6188/ws/v1/timeline/metrics/hosts API call returns
> {noformat}
> {
> "hostXYZ": [
> "datanode",
> "HOST",
> "namenode",
> "ams-hbase"
> ],
> ...
> }
> {noformat}
> This output indicates that new appid skywalking is not getting synced to
> other collector C2. This new appid is not getting synced even after 5 minutes
> which is the default ambari metrics metadata sync 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] [Created] (AMBARI-25963) Metrics metadata sync problem, accessing metrics which got created though other collector throws NPE
Mohammad Arshad created AMBARI-25963:
Summary: Metrics metadata sync problem, accessing metrics which
got created though other collector throws NPE
Key: AMBARI-25963
URL: https://issues.apache.org/jira/browse/AMBARI-25963
Project: Ambari
Issue Type: Bug
Affects Versions: metrics-3.0.0
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
Metrics metadata sync problem, accessing metrics which got created though other
collector throws NPE
*Steps to reproduce the issue:*
# Install ambari metrics with two collectors C1 and C2
# Submit following metrics through collector C1
{code:java}
{
"metrics": [
{
"metricname": "cpu",
"appid": "skywalking",
"hostname": "hostXYZ",
"starttime": 1687944230477,
"metrics": {
"1687944230477": 100,
"1687944430477": 200
}
}
]
}
{code}
#
http://COLLECTOR_C2_HOST:6188/ws/v1/timeline/metrics?metricNames=cpu&appId=skywalking&hostname=hostXYZ
API call returns
{noformat}
{
"exception": "NullPointerException",
"javaClassName": "java.lang.NullPointerException"
}
{noformat}
In collector C2 log file following message is logged
{code}
2023-06-28 09:40:24,592 ERROR
org.apache.ambari.metrics.core.timeline.discovery.TimelineMetricMetadataManager:
TimelineMetricMetadataKey is null for : [7, 73, 67, -94, 19, -102, 82, 114,
100, -66, -22, 79, -51, -107, -73, 64, -36, -72, -42, -103]
2023-06-28 09:40:24,594 WARN
org.apache.hadoop.yarn.webapp.GenericExceptionHandler: INTERNAL_SERVER_ERROR
java.lang.NullPointerException
at
org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor.getLastTimelineMetricFromResultSet(PhoenixHBaseAccessor.java:457)
at
org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor.getLatestMetricRecords(PhoenixHBaseAccessor.java:1150)
at
org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor.getMetricRecords(PhoenixHBaseAccessor.java:966)
at
org.apache.ambari.metrics.core.timeline.HBaseTimelineMetricsService.getTimelineMetrics(HBaseTimelineMetricsService.java:294)
at
org.apache.ambari.metrics.webapp.TimelineWebServices.getTimelineMetrics(TimelineWebServices.java:267)
{code}
Same behaviour is there even after 5 minutes which is the default ambari
metrics metadata sync 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] [Created] (AMBARI-25966) Ambari branch-2.7 CI is consistently failing
Mohammad Arshad created AMBARI-25966:
Summary: Ambari branch-2.7 CI is consistently failing
Key: AMBARI-25966
URL: https://issues.apache.org/jira/browse/AMBARI-25966
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Reporter: Mohammad Arshad
Ambari branch-2.7 CI is consistently failing. It fails while building ambari
metrics.
Following build command is failing
{noformat}
mvn -T 3C install -DskipSurefireTests -DskipPythonTests
-Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
-Dmaven.artifact.threads=10
{noformat}
Above command fails with following error
{noformat}
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 15.300 s]
[INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.268 s]
[INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 10.231 s]
[INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... SUCCESS [ 4.942 s]
[INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [ 4.901 s]
[INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 4.949 s]
[INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 5.982 s]
[INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... SUCCESS [ 5.943 s]
[INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [ 57.918 s]
[INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 1.842 s]
[INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 7.128 s]
[INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... SUCCESS [ 20.437 s]
[INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 01:24 min (Wall Clock)
[INFO] Finished at: 2023-07-12T18:27:23Z
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.6.0:copy-dependencies
(default) on project ambari-metrics-timelineservice: Excluding every artifact
inside 'test' resolution scope means excluding everything: you probably want
includeScope='compile', read parameters documentation for detailed explanations
-> [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-metrics-timelineservice
{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] [Commented] (AMBARI-25966) Ambari branch-2.7 CI is consistently failing
[
https://issues.apache.org/jira/browse/AMBARI-25966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743502#comment-17743502
]
Mohammad Arshad commented on AMBARI-25966:
--
I tried executing same build command locally, it is passing.
Any idea what else we can check on this?
Anybody who have CI write access, can you please run CI with debug enabled.
> Ambari branch-2.7 CI is consistently failing
>
>
> Key: AMBARI-25966
> URL: https://issues.apache.org/jira/browse/AMBARI-25966
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Priority: Major
>
> Ambari branch-2.7 CI is consistently failing. It fails while building ambari
> metrics.
> Following build command is failing
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10
> {noformat}
> Above command fails with following error
> {noformat}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 15.300
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.268
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 10.231
> s]
> [INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... SUCCESS [ 4.942
> s]
> [INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [ 4.901
> s]
> [INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 4.949
> s]
> [INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 5.982
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... SUCCESS [ 5.943
> s]
> [INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [ 57.918
> s]
> [INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 1.842
> s]
> [INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 7.128
> s]
> [INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... SUCCESS [ 20.437
> s]
> [INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 01:24 min (Wall Clock)
> [INFO] Finished at: 2023-07-12T18:27:23Z
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.6.0:copy-dependencies
> (default) on project ambari-metrics-timelineservice: Excluding every artifact
> inside 'test' resolution scope means excluding everything: you probably want
> includeScope='compile', read parameters documentation for detailed
> explanations -> [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-metrics-timelineservice
> {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] [Commented] (AMBARI-25966) Ambari branch-2.7 CI is consistently failing
[
https://issues.apache.org/jira/browse/AMBARI-25966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17744218#comment-17744218
]
Mohammad Arshad commented on AMBARI-25966:
--
Thanks [~brahmareddy] for enabling the debug log.
In my local code changed maven-dependency-plugin version to 3.5.0 then metrics
build started failing with the same error as CI error.
I think in CI environment some how higher version of maven-dependency-plugin
is used. Restricted the version to 2.8, as this is version used by other
modules, to solve this problem. Raised PR.
> Ambari branch-2.7 CI is consistently failing
>
>
> Key: AMBARI-25966
> URL: https://issues.apache.org/jira/browse/AMBARI-25966
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Ambari branch-2.7 CI is consistently failing. It fails while building ambari
> metrics.
> Following build command is failing
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10
> {noformat}
> Above command fails with following error
> {noformat}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 15.300
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.268
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 10.231
> s]
> [INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... SUCCESS [ 4.942
> s]
> [INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [ 4.901
> s]
> [INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 4.949
> s]
> [INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 5.982
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... SUCCESS [ 5.943
> s]
> [INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [ 57.918
> s]
> [INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 1.842
> s]
> [INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 7.128
> s]
> [INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... SUCCESS [ 20.437
> s]
> [INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 01:24 min (Wall Clock)
> [INFO] Finished at: 2023-07-12T18:27:23Z
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.6.0:copy-dependencies
> (default) on project ambari-metrics-timelineservice: Excluding every artifact
> inside 'test' resolution scope means excluding everything: you probably want
> includeScope='compile', read parameters documentation for detailed
> explanations -> [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-metrics-timelineservice
> {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] [Comment Edited] (AMBARI-25966) Ambari branch-2.7 CI is consistently failing
[
https://issues.apache.org/jira/browse/AMBARI-25966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17744218#comment-17744218
]
Mohammad Arshad edited comment on AMBARI-25966 at 7/18/23 2:36 PM:
---
Thanks [~brahmareddy] for enabling the debug log.
In my local code changed maven-dependency-plugin version to 3.6.0 then metrics
build started failing with the same error as CI error.
In CI environment some how 3.6.0 maven-dependency-plugin version is used.
Restricted the version to 2.8, as this is version used by other modules, to
solve this problem. Raised PR.
was (Author: arshad.mohammad):
Thanks [~brahmareddy] for enabling the debug log.
In my local code changed maven-dependency-plugin version to 3.5.0 then metrics
build started failing with the same error as CI error.
I think in CI environment some how higher version of maven-dependency-plugin
is used. Restricted the version to 2.8, as this is version used by other
modules, to solve this problem. Raised PR.
> Ambari branch-2.7 CI is consistently failing
>
>
> Key: AMBARI-25966
> URL: https://issues.apache.org/jira/browse/AMBARI-25966
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Ambari branch-2.7 CI is consistently failing. It fails while building ambari
> metrics.
> Following build command is failing
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10
> {noformat}
> Above command fails with following error
> {noformat}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 15.300
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.268
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 10.231
> s]
> [INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... SUCCESS [ 4.942
> s]
> [INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [ 4.901
> s]
> [INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 4.949
> s]
> [INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 5.982
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... SUCCESS [ 5.943
> s]
> [INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [ 57.918
> s]
> [INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 1.842
> s]
> [INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 7.128
> s]
> [INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... SUCCESS [ 20.437
> s]
> [INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 01:24 min (Wall Clock)
> [INFO] Finished at: 2023-07-12T18:27:23Z
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.6.0:copy-dependencies
> (default) on project ambari-metrics-timelineservice: Excluding every artifact
> inside 'test' resolution scope means excluding everything: you probably want
> includeScope='compile', read parameters documentation for detailed
> explanations -> [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-metrics-timelineservice
> {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] [Assigned] (AMBARI-25966) Ambari branch-2.7 CI is consistently failing
[
https://issues.apache.org/jira/browse/AMBARI-25966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad reassigned AMBARI-25966:
Assignee: Mohammad Arshad
> Ambari branch-2.7 CI is consistently failing
>
>
> Key: AMBARI-25966
> URL: https://issues.apache.org/jira/browse/AMBARI-25966
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Ambari branch-2.7 CI is consistently failing. It fails while building ambari
> metrics.
> Following build command is failing
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10
> {noformat}
> Above command fails with following error
> {noformat}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 15.300
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.268
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 10.231
> s]
> [INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... SUCCESS [ 4.942
> s]
> [INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [ 4.901
> s]
> [INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 4.949
> s]
> [INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 5.982
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... SUCCESS [ 5.943
> s]
> [INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [ 57.918
> s]
> [INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 1.842
> s]
> [INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 7.128
> s]
> [INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... SUCCESS [ 20.437
> s]
> [INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 01:24 min (Wall Clock)
> [INFO] Finished at: 2023-07-12T18:27:23Z
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.6.0:copy-dependencies
> (default) on project ambari-metrics-timelineservice: Excluding every artifact
> inside 'test' resolution scope means excluding everything: you probably want
> includeScope='compile', read parameters documentation for detailed
> explanations -> [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-metrics-timelineservice
> {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] [Commented] (AMBARI-25966) Ambari branch-2.7 CI is consistently failing
[
https://issues.apache.org/jira/browse/AMBARI-25966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17744311#comment-17744311
]
Mohammad Arshad commented on AMBARI-25966:
--
I analysed bit more, branch-2.7 CI is using maven 3.9.3. When I build
branch-2.7 ambari metrics with maven 3.9.3, build is failing with same error as
CI. So this maven version is making the difference.
Same behaviour is there with Ambari metrics master code as well. If ambari
metrics master repository is built with maven 3.9.3, build is failing with same
error as error in CI. This indicates that metrics master branch CI must not be
running with 3.9.3 maven version that is why master branch CI is running
without failure.
> Ambari branch-2.7 CI is consistently failing
>
>
> Key: AMBARI-25966
> URL: https://issues.apache.org/jira/browse/AMBARI-25966
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Ambari branch-2.7 CI is consistently failing. It fails while building ambari
> metrics.
> Following build command is failing
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10
> {noformat}
> Above command fails with following error
> {noformat}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 15.300
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.268
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 10.231
> s]
> [INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... SUCCESS [ 4.942
> s]
> [INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [ 4.901
> s]
> [INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 4.949
> s]
> [INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 5.982
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... SUCCESS [ 5.943
> s]
> [INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [ 57.918
> s]
> [INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 1.842
> s]
> [INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 7.128
> s]
> [INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... SUCCESS [ 20.437
> s]
> [INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 01:24 min (Wall Clock)
> [INFO] Finished at: 2023-07-12T18:27:23Z
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.6.0:copy-dependencies
> (default) on project ambari-metrics-timelineservice: Excluding every artifact
> inside 'test' resolution scope means excluding everything: you probably want
> includeScope='compile', read parameters documentation for detailed
> explanations -> [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-metrics-timelineservice
> {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] [Commented] (AMBARI-25966) Ambari branch-2.7 CI is consistently failing
[
https://issues.apache.org/jira/browse/AMBARI-25966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17744338#comment-17744338
]
Mohammad Arshad commented on AMBARI-25966:
--
maven-dependency-plugin is used in many other modules, but in all the modules
either version is mentioned or is not present. That is why build
is not failing in other modules.
Only ambari-metrics-timelineservice module have not configured version, also it
has config. So change is required only in
ambari-metrics-timelineservice module.
> Ambari branch-2.7 CI is consistently failing
>
>
> Key: AMBARI-25966
> URL: https://issues.apache.org/jira/browse/AMBARI-25966
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Fix For: 2.7.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Ambari branch-2.7 CI is consistently failing. It fails while building ambari
> metrics.
> Following build command is failing
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10
> {noformat}
> Above command fails with following error
> {noformat}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 15.300
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.268
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 10.231
> s]
> [INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... SUCCESS [ 4.942
> s]
> [INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [ 4.901
> s]
> [INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 4.949
> s]
> [INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 5.982
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... SUCCESS [ 5.943
> s]
> [INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [ 57.918
> s]
> [INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 1.842
> s]
> [INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 7.128
> s]
> [INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... SUCCESS [ 20.437
> s]
> [INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 01:24 min (Wall Clock)
> [INFO] Finished at: 2023-07-12T18:27:23Z
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.6.0:copy-dependencies
> (default) on project ambari-metrics-timelineservice: Excluding every artifact
> inside 'test' resolution scope means excluding everything: you probably want
> includeScope='compile', read parameters documentation for detailed
> explanations -> [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-metrics-timelineservice
> {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] [Commented] (AMBARI-25966) Ambari branch-2.7 CI is consistently failing
[
https://issues.apache.org/jira/browse/AMBARI-25966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17744339#comment-17744339
]
Mohammad Arshad commented on AMBARI-25966:
--
Thanks [~brahmareddy] for reviewing and committing the PR
> Ambari branch-2.7 CI is consistently failing
>
>
> Key: AMBARI-25966
> URL: https://issues.apache.org/jira/browse/AMBARI-25966
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Fix For: 2.7.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Ambari branch-2.7 CI is consistently failing. It fails while building ambari
> metrics.
> Following build command is failing
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10
> {noformat}
> Above command fails with following error
> {noformat}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 15.300
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.268
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 10.231
> s]
> [INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... SUCCESS [ 4.942
> s]
> [INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [ 4.901
> s]
> [INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 4.949
> s]
> [INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 5.982
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... SUCCESS [ 5.943
> s]
> [INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [ 57.918
> s]
> [INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 1.842
> s]
> [INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 7.128
> s]
> [INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... SUCCESS [ 20.437
> s]
> [INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 01:24 min (Wall Clock)
> [INFO] Finished at: 2023-07-12T18:27:23Z
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.6.0:copy-dependencies
> (default) on project ambari-metrics-timelineservice: Excluding every artifact
> inside 'test' resolution scope means excluding everything: you probably want
> includeScope='compile', read parameters documentation for detailed
> explanations -> [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-metrics-timelineservice
> {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] [Created] (AMBARI-25974) Branch-2.7 metrics build is failing because some dependency versions are not available
Mohammad Arshad created AMBARI-25974:
Summary: Branch-2.7 metrics build is failing because some
dependency versions are not available
Key: AMBARI-25974
URL: https://issues.apache.org/jira/browse/AMBARI-25974
Project: Ambari
Issue Type: Bug
Affects Versions: 2.7.7
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
{noformat}
mvn -T 3C install -DskipSurefireTests -DskipPythonTests
-Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
-Dmaven.artifact.threads=10 -X
{noformat}
{code:java}
[INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 43.509 s]
[INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.837 s]
[INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 29.457 s]
[INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... FAILURE [01:38 min]
[INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [01:01 min]
[INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 54.448 s]
[INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 54.939 s]
[INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... FAILURE [ 9.393 s]
[INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [06:29 min]
[INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 2.709 s]
[INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 4.659 s]
[INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... FAILURE [01:55 min]
[INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 07:43 min (Wall Clock)
[INFO] Finished at: 2023-07-22T15:15:35Z
[INFO]
[ERROR] Failed to execute goal on project ambari-metrics-storm-sink-legacy:
Could not resolve dependencies for project
org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The following
artifacts could not be resolved:
org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
(https://repo.hortonworks.com/content/groups/public/) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
on project ambari-metrics-storm-sink-legacy: Could not resolve dependencies for
project org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
following artifacts could not be resolved:
org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
(https://repo.hortonworks.com/content/groups/public/)
{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] [Commented] (AMBARI-25974) Branch-2.7 metrics build is failing because some dependency versions are not available
[
https://issues.apache.org/jira/browse/AMBARI-25974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746372#comment-17746372
]
Mohammad Arshad commented on AMBARI-25974:
--
Detailed log
{code:java}
INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 43.509 s]
[INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.837 s]
[INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 29.457 s]
[INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... FAILURE [01:38 min]
[INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [01:01 min]
[INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 54.448 s]
[INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 54.939 s]
[INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... FAILURE [ 9.393 s]
[INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [06:29 min]
[INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 2.709 s]
[INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 4.659 s]
[INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... FAILURE [01:55 min]
[INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 07:43 min (Wall Clock)
[INFO] Finished at: 2023-07-22T15:15:35Z
[INFO]
[ERROR] Failed to execute goal on project ambari-metrics-storm-sink-legacy:
Could not resolve dependencies for project
org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The following
artifacts could not be resolved:
org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
(https://repo.hortonworks.com/content/groups/public/) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
on project ambari-metrics-storm-sink-legacy: Could not resolve dependencies for
project org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
following artifacts could not be resolved:
org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
(https://repo.hortonworks.com/content/groups/public/)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies
(LifecycleDependencyResolver.java:243)
at
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies
(LifecycleDependencyResolver.java:136)
at
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved
(MojoExecutor.java:355)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:313)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:159)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:105)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:193)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call
(MultiThreadedBuilder.java:180)
at java.util.concurrent.FutureTask.run (FutureTask.java:266)
at java.util.concurrent.Executors$RunnableAdapter.call (Executors.java:511)
at java.util.concurrent.FutureTask.run (FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker
(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:624)
at java.lang.Thread.run (Thread.java:750)
Caused by: org.apache.maven.project.DependencyResolutionException: Could not
resolve dependencies for project
org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The following
artifacts could not be resolved:
org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
(https://repo.hortonworks.com/content/groups/public/)
at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve
(
[jira] [Commented] (AMBARI-25960) Add component grafana dashboards in ambari metrics
[ https://issues.apache.org/jira/browse/AMBARI-25960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746423#comment-17746423 ] Mohammad Arshad commented on AMBARI-25960: -- Thanks [~brahmareddy] for reviewing and merging the PR. > Add component grafana dashboards in ambari metrics > -- > > Key: AMBARI-25960 > URL: https://issues.apache.org/jira/browse/AMBARI-25960 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Fix For: 2.8.0 > > Attachments: image-2023-06-21-15-35-39-217.png > > Time Spent: 50m > Remaining Estimate: 0h > > Component grafana dashboards are missing from ambari-metrics 3.0.0 > These dashboards are available in ambari branch-2 ambari metrics and are > really useful. > Add back all BIGTO supported component grafana dashboards from ambari > branch-2 to ambari trunk > -- 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-25957) Ambari Metrics Grafana Datasource is not working
[ https://issues.apache.org/jira/browse/AMBARI-25957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746425#comment-17746425 ] Mohammad Arshad commented on AMBARI-25957: -- Thanks [~brahmareddy] for reviewing and merging the PR. > Ambari Metrics Grafana Datasource is not working > > > Key: AMBARI-25957 > URL: https://issues.apache.org/jira/browse/AMBARI-25957 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Labels: pull-request-available > Fix For: metrics-3.1.0 > > Attachments: image-2023-06-20-12-27-00-113.png, > image-2023-06-20-16-36-00-878.png > > > Ambari Metrics Grafana Datasource plugin is not working. Data is blank in > dashboards, following errors are logged in browser console > > !image-2023-06-20-12-27-00-113.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] [Commented] (AMBARI-25959) Ambari Metrics Grafana rpm missing some grafana tarball files
[ https://issues.apache.org/jira/browse/AMBARI-25959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746426#comment-17746426 ] Mohammad Arshad commented on AMBARI-25959: -- Thanks [~brahmareddy] for reviewing and merging the PR. > Ambari Metrics Grafana rpm missing some grafana tarball files > - > > Key: AMBARI-25959 > URL: https://issues.apache.org/jira/browse/AMBARI-25959 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Labels: pull-request-available > Fix For: metrics-3.1.0 > > > grafana-9.3.2.linux-amd64.tar.gz is extracted in folder > ambari-metrics-grafana/target/grafana/grafana-9.3.2 then all files inside > grafana-9.3.2 are used while building the rpm. But while extracting > grafana-9.3.2.linux-amd64.tar.gz some files are getting extracted in inside > ambari-metrics-grafana/target/grafana which then are not part of the rpm > > Grafana tarball extraction script to be changed so all files are placed > inside correct folder. > -- 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-25940) Ambari grafana ambari-server-jvm dashboard loading fails
[
https://issues.apache.org/jira/browse/AMBARI-25940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746510#comment-17746510
]
Mohammad Arshad commented on AMBARI-25940:
--
Thanks [~brahmareddy] for reviewing and merging the PR
> Ambari grafana ambari-server-jvm dashboard loading fails
>
>
> Key: AMBARI-25940
> URL: https://issues.apache.org/jira/browse/AMBARI-25940
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Fix For: 2.8.0
>
> Attachments: screenshot-1.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Installed hadoop cluster using ambari. Used following version of components
> Ambari trunk(3.0.0.0-SNAPSHOT)
> Ambari metrics master(3.1.0-SNAPSHOT)
> Bigtop 3.2.0
> Opened grafana link, opened
> ambari-server-jvm(http://host1:3000/d/ehbY5d84z/ambari-server-jvm?orgId=1)
> dashboard, observed following error
> {code:java}
> An unexpected error happened
> Details
> TypeError: Cannot read properties of null (reading 'text')
> at t
> (http://host1:3000/public/build/8310.56f209a52d089da1c262.js:8878:3025)
> at g
> (http://host1:3000/public/build/9512.8fae0c667bb767d8cfd1.js:2:1042468)
> at div
> at en
> (http://host1:3000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:150)
> {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] [Commented] (AMBARI-25945) Sync batch size in ambari metrics collector and ams hbase
[
https://issues.apache.org/jira/browse/AMBARI-25945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746530#comment-17746530
]
Mohammad Arshad commented on AMBARI-25945:
--
Thanks [~vjasani] for reviewing and merging this PR
> Sync batch size in ambari metrics collector and ams hbase
> -
>
> Key: AMBARI-25945
> URL: https://issues.apache.org/jira/browse/AMBARI-25945
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: image-2023-06-20-18-36-37-450.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In metrics collector phoenix batch size is 1, but in ams hbase batch size
> is 5000. Because of this following warning message is constantly getting
> logged
> {noformat}
> 2023-05-19 05:49:04,899 WARN
> [RpcServer.default.FPBQ.Fifo.handler=28,queue=1,port=61320]
> regionserver.RSRpcServices: Large batch operation detected (greater than
> 5000) (HBASE-18023). Requested Number of Rows: 5690 Client: ams//IP first
> region in
> multi=METRIC_RECORD_MINUTE_UUID,,1684154511984.1a0cc25ec53f3475ff282a47dc9d03b7.
> 2023-05-19 05:50:05,136 WARN
> [RpcServer.default.FPBQ.Fifo.handler=21,queue=0,port=61320]
> regionserver.RSRpcServices: Large batch operation detected (greater than
> 5000) (HBASE-18023). Requested Number of Rows: 1 Client: ams//IP first
> region in
> multi=METRIC_AGGREGATE_UUID,,1684154515075.77371e2960a2ce70bb15d223338ba893.
> {noformat}
> To fix this problem, either we should decrease phoenix batch size in
> collector or increase batch size in ams hbase.
> I propose to increase the batch size in ams hbase
--
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-25941) Metrics Grafana Datasource plugin is not loading
[ https://issues.apache.org/jira/browse/AMBARI-25941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746529#comment-17746529 ] Mohammad Arshad commented on AMBARI-25941: -- Thanks [~vjasani] for reviewing and merging this PR > Metrics Grafana Datasource plugin is not loading > > > Key: AMBARI-25941 > URL: https://issues.apache.org/jira/browse/AMBARI-25941 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics > Environment: Ambari trunk(3.0.0.0-SNAPSHOT) > Ambari metrics master(3.1.0-SNAPSHOT) > Bigtop 3.2.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Fix For: 3.0.0 > > Attachments: image-2023-05-15-20-31-45-499.png, > image-2023-06-20-13-33-14-546.png, screenshot-1.png > > Time Spent: 20m > Remaining Estimate: 0h > > I have installed only one ambari metrics collector, so there is only one > region server, but ams-hbase-home dashboard is showing as 3.8. > Similarly other metrics also in this dashboard are wrong > !image-2023-05-15-20-31-45-499.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] [Created] (AMBARI-25975) Grafana upgrade to 9.x caused many issues in metrics grafana dashboards.
Mohammad Arshad created AMBARI-25975:
Summary: Grafana upgrade to 9.x caused many issues in metrics
grafana dashboards.
Key: AMBARI-25975
URL: https://issues.apache.org/jira/browse/AMBARI-25975
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: metrics-3.0.0
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
Attachments: image-2023-07-24-23-52-31-437.png
# Many dashboard for example hbase-regionservers, hdfs-home, hdfs-datanodes
etc. template loading is failing with error
{noformat}
An unexpected error happened
Details
TypeError: Cannot read properties of null (reading 'text')
at t (http://host13000/public/build/8310.56f209a52d089da1c262.js:8878:3025)
at g (http://host13000/public/build/9512.8fae0c667bb767d8cfd1.js:2:1042468)
at div
at en
(http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:150)
at div
at nn
(http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:1022)
at form
at div
at _a
(http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:449:4395)
{noformat}
# datasource.js is throwing error while populating data. for example yarn-queue
dashboard logs below error in browser console
!image-2023-07-24-23-52-31-437.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] [Created] (AMBARI-25976) Upgrade grafana to remediate CVEs
Mohammad Arshad created AMBARI-25976: Summary: Upgrade grafana to remediate CVEs Key: AMBARI-25976 URL: https://issues.apache.org/jira/browse/AMBARI-25976 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: metrics-3.0.0 Reporter: Mohammad Arshad Assignee: Mohammad Arshad Grafana Security Advisory https://grafana.com/blog/2023/02/28/grafana-security-release-new-versions-with-security-fixes-for-cve-2023-0594-cve-2023-0507-and-cve-2023-22462/ Upgrade grafana to latest 9.x available version 9.5.6 -- 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-25975) Grafana upgrade to 9.x caused many issues in metrics grafana dashboards.
[
https://issues.apache.org/jira/browse/AMBARI-25975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25975:
-
Attachment: screenshot-1.png
> Grafana upgrade to 9.x caused many issues in metrics grafana dashboards.
>
>
> Key: AMBARI-25975
> URL: https://issues.apache.org/jira/browse/AMBARI-25975
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Critical
> Attachments: image-2023-07-24-23-52-31-437.png, screenshot-1.png
>
>
> # Many dashboard for example hbase-regionservers, hdfs-home, hdfs-datanodes
> etc. template loading is failing with error
> {noformat}
> An unexpected error happened
> Details
> TypeError: Cannot read properties of null (reading 'text')
> at t (http://host13000/public/build/8310.56f209a52d089da1c262.js:8878:3025)
> at g
> (http://host13000/public/build/9512.8fae0c667bb767d8cfd1.js:2:1042468)
> at div
> at en
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:150)
> at div
> at nn
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:1022)
> at form
> at div
> at _a
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:449:4395)
> {noformat}
> # datasource.js is throwing error while populating data. for example
> yarn-queue dashboard logs below error in browser console
> !image-2023-07-24-23-52-31-437.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-25975) Grafana upgrade to 9.x caused many issues in metrics grafana dashboards.
[
https://issues.apache.org/jira/browse/AMBARI-25975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25975:
-
Attachment: screenshot-2.png
> Grafana upgrade to 9.x caused many issues in metrics grafana dashboards.
>
>
> Key: AMBARI-25975
> URL: https://issues.apache.org/jira/browse/AMBARI-25975
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Critical
> Attachments: image-2023-07-24-23-52-31-437.png, screenshot-1.png,
> screenshot-2.png
>
>
> # Many dashboard for example hbase-regionservers, hdfs-home, hdfs-datanodes
> etc. template loading is failing with error
> {noformat}
> An unexpected error happened
> Details
> TypeError: Cannot read properties of null (reading 'text')
> at t (http://host13000/public/build/8310.56f209a52d089da1c262.js:8878:3025)
> at g
> (http://host13000/public/build/9512.8fae0c667bb767d8cfd1.js:2:1042468)
> at div
> at en
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:150)
> at div
> at nn
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:1022)
> at form
> at div
> at _a
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:449:4395)
> {noformat}
> # datasource.js is throwing error while populating data. for example
> yarn-queue dashboard logs below error in browser console
> !image-2023-07-24-23-52-31-437.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] [Commented] (AMBARI-25975) Grafana upgrade to 9.x caused many issues in metrics grafana dashboards.
[
https://issues.apache.org/jira/browse/AMBARI-25975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746909#comment-17746909
]
Mohammad Arshad commented on AMBARI-25975:
--
After fix dashboards are displaying data properly
!screenshot-1.png!
!screenshot-2.png!
!screenshot-3.png!
> Grafana upgrade to 9.x caused many issues in metrics grafana dashboards.
>
>
> Key: AMBARI-25975
> URL: https://issues.apache.org/jira/browse/AMBARI-25975
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Critical
> Attachments: image-2023-07-24-23-52-31-437.png, screenshot-1.png,
> screenshot-2.png, screenshot-3.png
>
>
> # Many dashboard for example hbase-regionservers, hdfs-home, hdfs-datanodes
> etc. template loading is failing with error
> {noformat}
> An unexpected error happened
> Details
> TypeError: Cannot read properties of null (reading 'text')
> at t (http://host13000/public/build/8310.56f209a52d089da1c262.js:8878:3025)
> at g
> (http://host13000/public/build/9512.8fae0c667bb767d8cfd1.js:2:1042468)
> at div
> at en
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:150)
> at div
> at nn
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:1022)
> at form
> at div
> at _a
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:449:4395)
> {noformat}
> # datasource.js is throwing error while populating data. for example
> yarn-queue dashboard logs below error in browser console
> !image-2023-07-24-23-52-31-437.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-25975) Grafana upgrade to 9.x caused many issues in metrics grafana dashboards.
[
https://issues.apache.org/jira/browse/AMBARI-25975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25975:
-
Attachment: screenshot-3.png
> Grafana upgrade to 9.x caused many issues in metrics grafana dashboards.
>
>
> Key: AMBARI-25975
> URL: https://issues.apache.org/jira/browse/AMBARI-25975
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Critical
> Attachments: image-2023-07-24-23-52-31-437.png, screenshot-1.png,
> screenshot-2.png, screenshot-3.png
>
>
> # Many dashboard for example hbase-regionservers, hdfs-home, hdfs-datanodes
> etc. template loading is failing with error
> {noformat}
> An unexpected error happened
> Details
> TypeError: Cannot read properties of null (reading 'text')
> at t (http://host13000/public/build/8310.56f209a52d089da1c262.js:8878:3025)
> at g
> (http://host13000/public/build/9512.8fae0c667bb767d8cfd1.js:2:1042468)
> at div
> at en
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:150)
> at div
> at nn
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:102:1022)
> at form
> at div
> at _a
> (http://host13000/public/build/DashboardPage.16f8a9df531a716aa30a.js:449:4395)
> {noformat}
> # datasource.js is throwing error while populating data. for example
> yarn-queue dashboard logs below error in browser console
> !image-2023-07-24-23-52-31-437.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] [Created] (AMBARI-25977) Increase default value of phoenix.mutate.maxSizeBytes from 100 MB to 255 MB
Mohammad Arshad created AMBARI-25977:
Summary: Increase default value of phoenix.mutate.maxSizeBytes
from 100 MB to 255 MB
Key: AMBARI-25977
URL: https://issues.apache.org/jira/browse/AMBARI-25977
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: metrics-3.0.0
Reporter: Mohammad Arshad
Assignee: Mohammad Arshad
Default value of phoenix.mutate.maxSizeBytes is 104857600(100 MB). As number of
records in a batch by default are set to 1, some times this value is not
sufficient and collector fails, to store aggregated data, with following error
{code:java}
2023-07-25 11:21:21,500 WARN
org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Failed on insert
records to store : ERROR 730 (LIM02): MutationState size is bigger than maximum
allowed number of bytes, try upserting rows in smaller batches or using
autocommit on for deletes. maxMutationSizeBytes=104857600
mutationSizeBytes=104858209
2023-07-25 11:21:21,500 WARN
org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Metric that
cannot be stored :
[regionserver.Server.rpcScanRequestCount,hbase]{1690284077957=162.7735639506746,
1690284092957=105.90141339016705, 1690284107957=171.52342993691653,
1690284122957=133.09041926456285}
2023-07-25 11:21:21,597 WARN
org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Failed on insert
records to store : ERROR 730 (LIM02): MutationState size is bigger than maximum
allowed number of bytes, try upserting rows in smaller batches or using
autocommit on for deletes. maxMutationSizeBytes=104857600
mutationSizeBytes=104858964
2023-07-25 11:21:21,598 WARN
org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Metric that
cannot be stored :
[regionserver.WAL.SyncTime_median,hbase]{1690284077957=188.0381529206563,
1690284092957=154.30748048226928, 1690284107957=190.57156509009513,
1690284122957=195.3577965382318}
{code}
lets set phoenix.mutate.maxSizeBytes value to 267386880 (255 MB) to make it
more reasonable with batch size.
--
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-25976) Upgrade grafana to remediate CVEs
[ https://issues.apache.org/jira/browse/AMBARI-25976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746957#comment-17746957 ] Mohammad Arshad commented on AMBARI-25976: -- Thanks [~brahmareddy] for your review. Currently branch-2.7 is using grafana 6.x. We have to backport many jiras to upgrade to grafana 9.x. I will raise separate jira to address branch-2.7 grafana upgrade. > Upgrade grafana to remediate CVEs > - > > Key: AMBARI-25976 > URL: https://issues.apache.org/jira/browse/AMBARI-25976 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: metrics-3.0.0 >Reporter: Mohammad Arshad >Assignee: Mohammad Arshad >Priority: Major > Labels: pull-request-available > > Grafana Security Advisory > https://grafana.com/blog/2023/02/28/grafana-security-release-new-versions-with-security-fixes-for-cve-2023-0594-cve-2023-0507-and-cve-2023-22462/ > Upgrade grafana to latest 9.x available version 9.5.6 -- 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-25977) Increase default value of phoenix.mutate.maxSizeBytes from 100 MB to 255 MB
[
https://issues.apache.org/jira/browse/AMBARI-25977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mohammad Arshad updated AMBARI-25977:
-
Attachment: screenshot-1.png
> Increase default value of phoenix.mutate.maxSizeBytes from 100 MB to 255 MB
> ---
>
> Key: AMBARI-25977
> URL: https://issues.apache.org/jira/browse/AMBARI-25977
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Attachments: screenshot-1.png
>
>
> Default value of phoenix.mutate.maxSizeBytes is 104857600(100 MB). As number
> of records in a batch by default are set to 1, some times this value is
> not sufficient and collector fails, to store aggregated data, with following
> error
> {code:java}
> 2023-07-25 11:21:21,500 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Failed on
> insert records to store : ERROR 730 (LIM02): MutationState size is bigger
> than maximum allowed number of bytes, try upserting rows in smaller batches
> or using autocommit on for deletes. maxMutationSizeBytes=104857600
> mutationSizeBytes=104858209
> 2023-07-25 11:21:21,500 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Metric that
> cannot be stored :
> [regionserver.Server.rpcScanRequestCount,hbase]{1690284077957=162.7735639506746,
> 1690284092957=105.90141339016705, 1690284107957=171.52342993691653,
> 1690284122957=133.09041926456285}
> 2023-07-25 11:21:21,597 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Failed on
> insert records to store : ERROR 730 (LIM02): MutationState size is bigger
> than maximum allowed number of bytes, try upserting rows in smaller batches
> or using autocommit on for deletes. maxMutationSizeBytes=104857600
> mutationSizeBytes=104858964
> 2023-07-25 11:21:21,598 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Metric that
> cannot be stored :
> [regionserver.WAL.SyncTime_median,hbase]{1690284077957=188.0381529206563,
> 1690284092957=154.30748048226928, 1690284107957=190.57156509009513,
> 1690284122957=195.3577965382318}
> {code}
> lets set phoenix.mutate.maxSizeBytes value to 267386880 (255 MB) to make it
> more reasonable with batch size.
--
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-25977) Increase default value of phoenix.mutate.maxSizeBytes from 100 MB to 255 MB
[
https://issues.apache.org/jira/browse/AMBARI-25977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747022#comment-17747022
]
Mohammad Arshad commented on AMBARI-25977:
--
After fix, by default phoenix.mutate.maxSizeBytes is configured to 267386880
!screenshot-1.png!
> Increase default value of phoenix.mutate.maxSizeBytes from 100 MB to 255 MB
> ---
>
> Key: AMBARI-25977
> URL: https://issues.apache.org/jira/browse/AMBARI-25977
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: metrics-3.0.0
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
> Attachments: screenshot-1.png
>
>
> Default value of phoenix.mutate.maxSizeBytes is 104857600(100 MB). As number
> of records in a batch by default are set to 1, some times this value is
> not sufficient and collector fails, to store aggregated data, with following
> error
> {code:java}
> 2023-07-25 11:21:21,500 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Failed on
> insert records to store : ERROR 730 (LIM02): MutationState size is bigger
> than maximum allowed number of bytes, try upserting rows in smaller batches
> or using autocommit on for deletes. maxMutationSizeBytes=104857600
> mutationSizeBytes=104858209
> 2023-07-25 11:21:21,500 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Metric that
> cannot be stored :
> [regionserver.Server.rpcScanRequestCount,hbase]{1690284077957=162.7735639506746,
> 1690284092957=105.90141339016705, 1690284107957=171.52342993691653,
> 1690284122957=133.09041926456285}
> 2023-07-25 11:21:21,597 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Failed on
> insert records to store : ERROR 730 (LIM02): MutationState size is bigger
> than maximum allowed number of bytes, try upserting rows in smaller batches
> or using autocommit on for deletes. maxMutationSizeBytes=104857600
> mutationSizeBytes=104858964
> 2023-07-25 11:21:21,598 WARN
> org.apache.ambari.metrics.core.timeline.PhoenixHBaseAccessor: Metric that
> cannot be stored :
> [regionserver.WAL.SyncTime_median,hbase]{1690284077957=188.0381529206563,
> 1690284092957=154.30748048226928, 1690284107957=190.57156509009513,
> 1690284122957=195.3577965382318}
> {code}
> lets set phoenix.mutate.maxSizeBytes value to 267386880 (255 MB) to make it
> more reasonable with batch size.
--
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-25974) Branch-2.7 metrics build is failing because some dependency versions are not available
[
https://issues.apache.org/jira/browse/AMBARI-25974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747285#comment-17747285
]
Mohammad Arshad commented on AMBARI-25974:
--
Compilation is failing because zookeeper 3.4.6.2.3.0.0-2557 and storm
0.10.0.2.3.0.0-2557 is no more available in hortonworks repository
https://repo.hortonworks.com/content/groups/public
> Branch-2.7 metrics build is failing because some dependency versions are not
> available
> --
>
> Key: AMBARI-25974
> URL: https://issues.apache.org/jira/browse/AMBARI-25974
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.7
>Reporter: Mohammad Arshad
>Assignee: Mohammad Arshad
>Priority: Major
>
> {noformat}
> mvn -T 3C install -DskipSurefireTests -DskipPythonTests
> -Dmaven.test.failure.ignore -DskipTests -Dfindbugs.skip -Drat.skip
> -Dmaven.artifact.threads=10 -X
> {noformat}
> {code:java}
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ 43.509
> s]
> [INFO] ambari-metrics 2.7.8.0.0 ... SUCCESS [ 0.837
> s]
> [INFO] Ambari Metrics Common 2.7.8.0.0 SUCCESS [ 29.457
> s]
> [INFO] Ambari Metrics Hadoop Sink 2.7.8.0.0 ... FAILURE [01:38
> min]
> [INFO] Ambari Metrics Flume Sink 2.7.8.0.0 SUCCESS [01:01
> min]
> [INFO] Ambari Metrics Kafka Sink 2.7.8.0.0 SUCCESS [ 54.448
> s]
> [INFO] Ambari Metrics Storm Sink 2.7.8.0.0 SUCCESS [ 54.939
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) 2.7.8.0.0 ... FAILURE [ 9.393
> s]
> [INFO] Ambari Metrics Collector 2.7.8.0.0 . FAILURE [06:29
> min]
> [INFO] Ambari Metrics Monitor 2.7.8.0.0 ... SUCCESS [ 2.709
> s]
> [INFO] Ambari Metrics Grafana 2.7.8.0.0 ... SUCCESS [ 4.659
> s]
> [INFO] Ambari Metrics Host Aggregator 2.7.8.0.0 ... FAILURE [01:55
> min]
> [INFO] Ambari Metrics Assembly 2.7.8.0.0 .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 07:43 min (Wall Clock)
> [INFO] Finished at: 2023-07-22T15:15:35Z
> [INFO]
>
> [ERROR] Failed to execute goal on project ambari-metrics-storm-sink-legacy:
> Could not resolve dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project ambari-metrics-storm-sink-legacy: Could not resolve
> dependencies for project
> org.apache.ambari:ambari-metrics-storm-sink-legacy:jar:2.7.8.0.0: The
> following artifacts could not be resolved:
> org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 (absent): Could not find
> artifact org.apache.storm:storm-core:jar:0.10.0.2.3.0.0-2557 in apache-hadoop
> (https://repo.hortonworks.com/content/groups/public/)
> {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
