ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lysnichenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-18663) Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
Date Fri, 21 Oct 2016 15:48:58 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-18663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dmitry Lysnichenko updated AMBARI-18663:
----------------------------------------
    Component/s: ambari-server

> Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
> ---------------------------------------------------------------------
>
>                 Key: AMBARI-18663
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18663
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>         Attachments: AMBARI-18663.patch
>
>
> STR:
> 1)Deploy old version cluster regarding environment (use public repo)
> 2)Enable AMS distr. mode
> 3)Make ambari only upgrade to 2.4.1.0
> Actual result:
> Storm becomes stopped by itself after upgrade from 2.2.1.0 to 2.4.1.0
> {code}
> supervisor.log
> 2016-09-01 21:51:48.996 o.a.s.c.ConnectionState [ERROR] Connection timed out for connection
string (host:2181,host:2181,host:2181/storm) and timeout (15000) / elapsed (18214)
> org.apache.storm.curator.CuratorConnectionLossException: KeeperErrorCode = ConnectionLoss
> at org.apache.storm.curator.ConnectionState.checkTimeouts(ConnectionState.java:195) [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at org.apache.storm.curator.ConnectionState.getZooKeeper(ConnectionState.java:87) [storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at org.apache.storm.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:115)
[storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.performBackgroundOperation(CuratorFrameworkImpl.java:821)
[storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.backgroundOperationsLoop(CuratorFrameworkImpl.java:807)
[storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at org.apache.storm.curator.framework.imps.CuratorFrameworkImpl.access$300(CuratorFrameworkImpl.java:63)
[storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at org.apache.storm.curator.framework.imps.CuratorFrameworkImpl$4.call(CuratorFrameworkImpl.java:267)
[storm-core-0.10.0.2.4.2.0-258.jar:0.10.0.2.4.2.0-258]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [?:1.7.0_67]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [?:1.7.0_67]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [?:1.7.0_67]
> at java.lang.Thread.run(Thread.java:745) [?:1.7.0_67]
> 2016-09-01 21:51:49.000 b.s.d.supervisor [INFO] d0050058-970d-4faa-8170-b8d9b0515baf
still hasn't started
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message