You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Sanjay Awasthi (JIRA)" <ji...@apache.org> on 2018/02/02 10:17:00 UTC
[jira] [Resolved] (STORM-2927) Storm supervisor displaying message
"kill: sending signal to 23543 failed: No such process"
[ https://issues.apache.org/jira/browse/STORM-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanjay Awasthi resolved STORM-2927.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.1.1
I changed the storm.yaml entry messaging.transport from backtype.storm.messaging.netty.Context to org.apache.storm.messaging.netty.Context .
> Storm supervisor displaying message "kill: sending signal to 23543 failed: No such process"
> -------------------------------------------------------------------------------------------
>
> Key: STORM-2927
> URL: https://issues.apache.org/jira/browse/STORM-2927
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-opentsdb
> Affects Versions: 1.1.1
> Reporter: Sanjay Awasthi
> Priority: Major
> Fix For: 1.1.1
>
>
> I started storm cluster and all one nimbus and two supervisors started fine and I could view them fine on "Storm UI" then I deployed example topology "storm-opentsdb-2.0.0-SNAPSHOT.jar", it is successfully deployed on the cluster but after few minutes supervisor console displays message and no data is inserted in Opentsdb.
> kill: sending signal to 23543 failed: No such process
> kill: sending signal to 23615 failed: No such process
> kill: sending signal to 23612 failed: No such process
> kill: sending signal to 23706 failed: No such process
> kill: sending signal to 23776 failed: No such process.
> The same topology run perfectly fine in Local Cluster mode and inserts data in Opentsdb.
> To resolve this issue I killed the toplogy, killed the nimbus and supervisor nodes. I manuall deleted files under "storm.local.dir: "/tmp/storm-data"" and also deleted the files in zookeeper znode /storm. Again started the cluster and deployed the same topology but got the same error.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)