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