[jira] [Updated] (AMBARI-25598) Fix a parameter error in the toString() of the ServiceComponentRequest file.
[ https://issues.apache.org/jira/browse/AMBARI-25598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] THOMAS TAO updated AMBARI-25598: Status: Open (was: Patch Available) > Fix a parameter error in the toString() of the ServiceComponentRequest file. > > > Key: AMBARI-25598 > URL: https://issues.apache.org/jira/browse/AMBARI-25598 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: THOMAS TAO >Priority: Minor > > In the tostring function of the ServiceComponentRequest file, the fourth > parameter of String.format() should be componentName instead of clusterName. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25598) Fix a parameter error in the toString() of the ServiceComponentRequest file.
[ https://issues.apache.org/jira/browse/AMBARI-25598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] THOMAS TAO updated AMBARI-25598: Status: Patch Available (was: Open) > Fix a parameter error in the toString() of the ServiceComponentRequest file. > > > Key: AMBARI-25598 > URL: https://issues.apache.org/jira/browse/AMBARI-25598 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: THOMAS TAO >Priority: Minor > > In the tostring function of the ServiceComponentRequest file, the fourth > parameter of String.format() should be componentName instead of clusterName. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25598) Fix a parameter error in the toString() of the ServiceComponentRequest file.
THOMAS TAO created AMBARI-25598: --- Summary: Fix a parameter error in the toString() of the ServiceComponentRequest file. Key: AMBARI-25598 URL: https://issues.apache.org/jira/browse/AMBARI-25598 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: THOMAS TAO In the tostring function of the ServiceComponentRequest file, the fourth parameter of String.format() should be componentName instead of clusterName. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25596) Multiple Ambari Unit Tests failing due to Address already in use
[
https://issues.apache.org/jira/browse/AMBARI-25596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-25596:
Labels: pull-request-available (was: )
> Multiple Ambari Unit Tests failing due to Address already in use
>
>
> Key: AMBARI-25596
> URL: https://issues.apache.org/jira/browse/AMBARI-25596
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Suraj Naik
>Priority: Minor
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Issue:
>
> {{Running org.apache.ambari.metrics.webapp.TestTimelineWebServicesTests run:
> 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.294 sec <<< FAILURE! -
> in
> org.apache.ambari.metrics.webapp.TestTimelineWebServicestestAbout(org.apache.ambari.metrics.webapp.TestTimelineWebServices)
>
> Time elapsed: 0.005 sec
> <<< ERROR!com.sun.jersey.test.framework.spi.container.TestContainerException:
> java.net.BindException: Address already in use
> at
> org.apache.ambari.metrics.webapp.TestTimelineWebServices.(TestTimelineWebServices.java:77)
> Caused by: java.net.BindException: Address already in useat
> org.apache.ambari.metrics.webapp.TestTimelineWebServices.(TestTimelineWebServices.java:77)
> testGetMetrics(org.apache.ambari.metrics.webapp.TestTimelineWebServices)
> Time elapsed: 0.001 sec <<<
> ERROR!com.sun.jersey.test.framework.spi.container.TestContainerException:
> java.net.BindException: Address already in use
> at
> org.apache.ambari.metrics.webapp.TestTimelineWebServices.(TestTimelineWebServices.java:77)
> Caused by: java.net.BindException: Address already in use
> at
> org.apache.ambari.metrics.webapp.TestTimelineWebServices.(TestTimelineWebServices.java:77)
> Results :Tests in
> error:TestTimelineWebServices.:77->JerseyTestBase.:27->JerseyTest.:217->JerseyTest.getContainer:342
> »
> TestContainerTestTimelineWebServices.:77->JerseyTestBase.:27->JerseyTest.:217->JerseyTest.getContainer:342
> » TestContainer}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (AMBARI-25596) Multiple Ambari Unit Tests failing due to Address already in use
[
https://issues.apache.org/jira/browse/AMBARI-25596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suraj Naik updated AMBARI-25596:
Summary: Multiple Ambari Unit Tests failing due to Address already in use
(was: TestTimelineWebServices.java failing due to address in use)
> Multiple Ambari Unit Tests failing due to Address already in use
>
>
> Key: AMBARI-25596
> URL: https://issues.apache.org/jira/browse/AMBARI-25596
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Suraj Naik
>Priority: Minor
>
> Issue:
>
> {{Running org.apache.ambari.metrics.webapp.TestTimelineWebServicesTests run:
> 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.294 sec <<< FAILURE! -
> in
> org.apache.ambari.metrics.webapp.TestTimelineWebServicestestAbout(org.apache.ambari.metrics.webapp.TestTimelineWebServices)
>
> Time elapsed: 0.005 sec
> <<< ERROR!com.sun.jersey.test.framework.spi.container.TestContainerException:
> java.net.BindException: Address already in use
> at
> org.apache.ambari.metrics.webapp.TestTimelineWebServices.(TestTimelineWebServices.java:77)
> Caused by: java.net.BindException: Address already in useat
> org.apache.ambari.metrics.webapp.TestTimelineWebServices.(TestTimelineWebServices.java:77)
> testGetMetrics(org.apache.ambari.metrics.webapp.TestTimelineWebServices)
> Time elapsed: 0.001 sec <<<
> ERROR!com.sun.jersey.test.framework.spi.container.TestContainerException:
> java.net.BindException: Address already in use
> at
> org.apache.ambari.metrics.webapp.TestTimelineWebServices.(TestTimelineWebServices.java:77)
> Caused by: java.net.BindException: Address already in use
> at
> org.apache.ambari.metrics.webapp.TestTimelineWebServices.(TestTimelineWebServices.java:77)
> Results :Tests in
> error:TestTimelineWebServices.:77->JerseyTestBase.:27->JerseyTest.:217->JerseyTest.getContainer:342
> »
> TestContainerTestTimelineWebServices.:77->JerseyTestBase.:27->JerseyTest.:217->JerseyTest.getContainer:342
> » TestContainer}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (AMBARI-25597) Apache Storm settings set from Ambari
[ https://issues.apache.org/jira/browse/AMBARI-25597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Threat Inter updated AMBARI-25597: -- Description: Hello, everyone. We installed Apache Storm using Ambari. Now we writing messages from Apache Storm into Elasticsearch. And sometimes we get errors with listener timeout: We want to increase this timeout, it should be not so difficult [https://stackoverflow.com/questions/51341806/elasticsearch-resthighlevelclient-listener-timeout-after-waiting-for-3] but we don't know how to do it using Ambari Can someone tell how to do it? was: Hello, everyone. We installed Apache Storm using Ambari. Now we writing messages from Apache Storm into Elasticsearch. And sometimes we get errors with listener timeout: !image-2020-11-30-14-04-14-104.png! We want to increase this timeout, it should be not so difficult [https://stackoverflow.com/questions/51341806/elasticsearch-resthighlevelclient-listener-timeout-after-waiting-for-3] but we don't know how to do it using Ambari Can someone tell how to do it? > Apache Storm settings set from Ambari > - > > Key: AMBARI-25597 > URL: https://issues.apache.org/jira/browse/AMBARI-25597 > Project: Ambari > Issue Type: Bug >Reporter: Threat Inter >Priority: Major > Attachments: image-2020-11-30-14-08-06-874.png > > > Hello, everyone. We installed Apache Storm using Ambari. Now we writing > messages from Apache Storm into Elasticsearch. And sometimes we get errors > with listener timeout: > > > We want to increase this timeout, it should be not so difficult > [https://stackoverflow.com/questions/51341806/elasticsearch-resthighlevelclient-listener-timeout-after-waiting-for-3] > but we don't know how to do it using Ambari > Can someone tell how to do it? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25597) Apache Storm settings set from Ambari
[ https://issues.apache.org/jira/browse/AMBARI-25597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Threat Inter updated AMBARI-25597: -- Attachment: image-2020-11-30-14-08-06-874.png > Apache Storm settings set from Ambari > - > > Key: AMBARI-25597 > URL: https://issues.apache.org/jira/browse/AMBARI-25597 > Project: Ambari > Issue Type: Bug >Reporter: Threat Inter >Priority: Major > Attachments: image-2020-11-30-14-08-06-874.png > > > Hello, everyone. We installed Apache Storm using Ambari. Now we writing > messages from Apache Storm into Elasticsearch. And sometimes we get errors > with listener timeout: > > > We want to increase this timeout, it should be not so difficult > [https://stackoverflow.com/questions/51341806/elasticsearch-resthighlevelclient-listener-timeout-after-waiting-for-3] > but we don't know how to do it using Ambari > Can someone tell how to do it? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25597) Apache Storm settings set from Ambari
[ https://issues.apache.org/jira/browse/AMBARI-25597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Threat Inter updated AMBARI-25597: -- Description: Hello, everyone. We installed Apache Storm using Ambari. Now we writing messages from Apache Storm into Elasticsearch. And sometimes we get errors with listener timeout: !image-2020-11-30-14-08-06-874.png! We want to increase this timeout, it should be not so difficult [https://stackoverflow.com/questions/51341806/elasticsearch-resthighlevelclient-listener-timeout-after-waiting-for-3] but we don't know how to do it using Ambari Can someone tell how to do it? was: Hello, everyone. We installed Apache Storm using Ambari. Now we writing messages from Apache Storm into Elasticsearch. And sometimes we get errors with listener timeout: We want to increase this timeout, it should be not so difficult [https://stackoverflow.com/questions/51341806/elasticsearch-resthighlevelclient-listener-timeout-after-waiting-for-3] but we don't know how to do it using Ambari Can someone tell how to do it? > Apache Storm settings set from Ambari > - > > Key: AMBARI-25597 > URL: https://issues.apache.org/jira/browse/AMBARI-25597 > Project: Ambari > Issue Type: Bug >Reporter: Threat Inter >Priority: Major > Attachments: image-2020-11-30-14-08-06-874.png > > > Hello, everyone. We installed Apache Storm using Ambari. Now we writing > messages from Apache Storm into Elasticsearch. And sometimes we get errors > with listener timeout: > !image-2020-11-30-14-08-06-874.png! > > We want to increase this timeout, it should be not so difficult > [https://stackoverflow.com/questions/51341806/elasticsearch-resthighlevelclient-listener-timeout-after-waiting-for-3] > but we don't know how to do it using Ambari > Can someone tell how to do it? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25597) Apache Storm settings set from Ambari
Threat Inter created AMBARI-25597: - Summary: Apache Storm settings set from Ambari Key: AMBARI-25597 URL: https://issues.apache.org/jira/browse/AMBARI-25597 Project: Ambari Issue Type: Bug Reporter: Threat Inter Hello, everyone. We installed Apache Storm using Ambari. Now we writing messages from Apache Storm into Elasticsearch. And sometimes we get errors with listener timeout: !image-2020-11-30-14-04-14-104.png! We want to increase this timeout, it should be not so difficult [https://stackoverflow.com/questions/51341806/elasticsearch-resthighlevelclient-listener-timeout-after-waiting-for-3] but we don't know how to do it using Ambari Can someone tell how to do it? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMBARI-25596) TestTimelineWebServices.java failing due to address in use
[
https://issues.apache.org/jira/browse/AMBARI-25596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17240569#comment-17240569
]
Suraj Naik commented on AMBARI-25596:
-
Please review my code.
> TestTimelineWebServices.java failing due to address in use
> --
>
> Key: AMBARI-25596
> URL: https://issues.apache.org/jira/browse/AMBARI-25596
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Reporter: Suraj Naik
>Priority: Minor
>
> Issue:
>
> {{Running org.apache.ambari.metrics.webapp.TestTimelineWebServicesTests run:
> 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.294 sec <<< FAILURE! -
> in
> org.apache.ambari.metrics.webapp.TestTimelineWebServicestestAbout(org.apache.ambari.metrics.webapp.TestTimelineWebServices)
>
> Time elapsed: 0.005 sec
> <<< ERROR!com.sun.jersey.test.framework.spi.container.TestContainerException:
> java.net.BindException: Address already in use
> at
> org.apache.ambari.metrics.webapp.TestTimelineWebServices.(TestTimelineWebServices.java:77)
> Caused by: java.net.BindException: Address already in useat
> org.apache.ambari.metrics.webapp.TestTimelineWebServices.(TestTimelineWebServices.java:77)
> testGetMetrics(org.apache.ambari.metrics.webapp.TestTimelineWebServices)
> Time elapsed: 0.001 sec <<<
> ERROR!com.sun.jersey.test.framework.spi.container.TestContainerException:
> java.net.BindException: Address already in use
> at
> org.apache.ambari.metrics.webapp.TestTimelineWebServices.(TestTimelineWebServices.java:77)
> Caused by: java.net.BindException: Address already in use
> at
> org.apache.ambari.metrics.webapp.TestTimelineWebServices.(TestTimelineWebServices.java:77)
> Results :Tests in
> error:TestTimelineWebServices.:77->JerseyTestBase.:27->JerseyTest.:217->JerseyTest.getContainer:342
> »
> TestContainerTestTimelineWebServices.:77->JerseyTestBase.:27->JerseyTest.:217->JerseyTest.getContainer:342
> » TestContainer}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (AMBARI-25596) TestTimelineWebServices.java failing due to address in use
Suraj Naik created AMBARI-25596:
---
Summary: TestTimelineWebServices.java failing due to address in use
Key: AMBARI-25596
URL: https://issues.apache.org/jira/browse/AMBARI-25596
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Reporter: Suraj Naik
Issue:
{{Running org.apache.ambari.metrics.webapp.TestTimelineWebServicesTests run: 2,
Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.294 sec <<< FAILURE! - in
org.apache.ambari.metrics.webapp.TestTimelineWebServicestestAbout(org.apache.ambari.metrics.webapp.TestTimelineWebServices)
Time elapsed: 0.005 sec
<<< ERROR!com.sun.jersey.test.framework.spi.container.TestContainerException:
java.net.BindException: Address already in use
at
org.apache.ambari.metrics.webapp.TestTimelineWebServices.(TestTimelineWebServices.java:77)
Caused by: java.net.BindException: Address already in useat
org.apache.ambari.metrics.webapp.TestTimelineWebServices.(TestTimelineWebServices.java:77)
testGetMetrics(org.apache.ambari.metrics.webapp.TestTimelineWebServices)
Time elapsed: 0.001 sec <<<
ERROR!com.sun.jersey.test.framework.spi.container.TestContainerException:
java.net.BindException: Address already in use
at
org.apache.ambari.metrics.webapp.TestTimelineWebServices.(TestTimelineWebServices.java:77)
Caused by: java.net.BindException: Address already in use
at
org.apache.ambari.metrics.webapp.TestTimelineWebServices.(TestTimelineWebServices.java:77)
Results :Tests in
error:TestTimelineWebServices.:77->JerseyTestBase.:27->JerseyTest.:217->JerseyTest.getContainer:342
»
TestContainerTestTimelineWebServices.:77->JerseyTestBase.:27->JerseyTest.:217->JerseyTest.getContainer:342
» TestContainer}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
