[jira] [Updated] (STORM-3798) No nimbus leader participant host found, have you started your nimbus hosts?
[ https://issues.apache.org/jira/browse/STORM-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anandh kumar updated STORM-3798: Attachment: nimbus.log > No nimbus leader participant host found, have you started your nimbus hosts? > > > Key: STORM-3798 > URL: https://issues.apache.org/jira/browse/STORM-3798 > Project: Apache Storm > Issue Type: Bug > Components: storm-core >Affects Versions: 2.2.0 > Environment: CentOS 7.6 >Reporter: Anandh kumar >Priority: Major > Attachments: nimbus.log > > > I have setup the storm cluster in AWS environment with 6 node clusters. 1 > Master and 5 slave and the zookeeper are installed in 3 node clusters. > > When I shutdown zookeeper and storm nodes every day night and start in the > morning, When the machine boots up I have started all the nimbus and > supervisor and zookeeper service via supervisord. Once machine up all the > service are running but in the nimbus logs I am getting > "java.lang.RuntimeException: No nimbus leader participant host found, have > you started your nimbus hosts?" error. > > I have restarted zookeeper and nimbus also not working still getting this > error. Once I remove all the data from zookeeper data directly then restart > zookeeper and storm service then working fine. > Why I have to do this everyday when the machine starts up? how can I fix this > issue. When machine boot up all the service should work fine. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (STORM-3798) No nimbus leader participant host found, have you started your nimbus hosts?
Anandh kumar created STORM-3798: --- Summary: No nimbus leader participant host found, have you started your nimbus hosts? Key: STORM-3798 URL: https://issues.apache.org/jira/browse/STORM-3798 Project: Apache Storm Issue Type: Bug Components: storm-core Affects Versions: 2.2.0 Environment: CentOS 7.6 Reporter: Anandh kumar I have setup the storm cluster in AWS environment with 6 node clusters. 1 Master and 5 slave and the zookeeper are installed in 3 node clusters. When I shutdown zookeeper and storm nodes every day night and start in the morning, When the machine boots up I have started all the nimbus and supervisor and zookeeper service via supervisord. Once machine up all the service are running but in the nimbus logs I am getting "java.lang.RuntimeException: No nimbus leader participant host found, have you started your nimbus hosts?" error. I have restarted zookeeper and nimbus also not working still getting this error. Once I remove all the data from zookeeper data directly then restart zookeeper and storm service then working fine. Why I have to do this everyday when the machine starts up? how can I fix this issue. When machine boot up all the service should work fine. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (STORM-3685) Detect Loops in Topology at Submit
[
https://issues.apache.org/jira/browse/STORM-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17425334#comment-17425334
]
Roshan Naik commented on STORM-3685:
[~bipinprasad] & [~ethanli]
a very very late +1 on this approach of warning but not banning cycles.
Sometimes there is a need for cycles if downstream operators need to report
progress or send metadata to upstream operators. This can be used for flow
control where sources can be suspended/resumed based on progress notifications
from downstream operators. For example:
* For (event-time based) windowed joins, can be useful to synchronize streams
involved around event time boundaries. Allowing both streams to progress
without any flow controls can cause one stream to move far too ahead compared
to the other stream and that will lead to having too open windows opens for too
long... and thus lead to excessive memory consumption.
* The [Kappa+ Architecture|https://www.youtube.com/watch?v=4qSlsYogALo] uses
flow control on sources for enabling usecases like efficient backfills using
native streaming mode execution.
* As you know, technically, any topology with ACKing enabled has a cycle. And
{{topology.max.spout.pending}} is a form of flow control.
> Detect Loops in Topology at Submit
> --
>
> Key: STORM-3685
> URL: https://issues.apache.org/jira/browse/STORM-3685
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-client
>Reporter: Bipin Prasad
>Assignee: Bipin Prasad
>Priority: Major
> Fix For: 2.3.0
>
> Time Spent: 7h 40m
> Remaining Estimate: 0h
>
> Topology graph is expected to be a Directed Acyclic Graph (DAG). Detect
> cycles in DAG when Topology is submitted and prevent cycles in Topology.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
