Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
2.4.0
-
None
Description
This issue is result of storm site being scattered between Storm service and AMS service.
Its highly recommended to avoid such scattering of config sites across services. Doing so requires special handling on FE and generates lots of new flows that needs to be tested.
storm site should only belong and be packaged inside Storm service. If there are some configs of storm-site that needs to be added if AMS is present then stack advisor can be leveraged to achieve that objective
Attachments
Attachments
Issue Links
- links to
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12838567/AMBARI-18857.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 2 new or modified test files.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed unit tests in ambari-server.
Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/9239//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/9239//console
This message is automatically generated.