[ 
https://issues.apache.org/jira/browse/STORM-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16820391#comment-16820391
 ] 

Stig Rohde Døssing commented on STORM-3382:
-------------------------------------------

Your log shows that Nimbus shut your topology down.

{code}
16298 [main] INFO  o.a.s.d.nimbus - Delaying event :remove for 30 secs for 
CopyTopology-1-1555494535
16311 [main] INFO  o.a.s.d.nimbus - Adding topo to history log: 
CopyTopology-1-1555494535
16317 [main] INFO  o.a.s.d.nimbus - Shutting down master
{code}

I would check your Nimbus log to figure out why Nimbus is closing your topology.

Also are you running your topology in a LocalCluster? I'm wondering why else 
your supervisor would be shutting down

{code}
20676 [main] INFO  o.a.s.d.s.Supervisor - Shutting down supervisor 
68950b84-1856-4001-b742-005b2bbd40f8
{code}

> ERROR o.a.s.d.s.ReadClusterState - Failed to Sync Supervisor, while reading 
> the file size of 30 GB
> --------------------------------------------------------------------------------------------------
>
>                 Key: STORM-3382
>                 URL: https://issues.apache.org/jira/browse/STORM-3382
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-core
>    Affects Versions: 1.2.2
>         Environment: Prod
>            Reporter: antarix bhardwaj
>            Priority: Major
>         Attachments: logs.txt
>
>
> We are reading the contents of a file from S3 via spout. 
> When we are reading a small file like 30KB or so, the spout works fine.
> But when we read the file of size 40 GB approx the topology fails with the 
> error, ERROR o.a.s.d.s.ReadClusterState - Failed to Sync Supervisor. And the 
> thread is interrupted.
> Please finds the logs attached.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to