You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@heron.apache.org by GitBox <gi...@apache.org> on 2019/04/26 09:47:37 UTC

[GitHub] [incubator-heron] Vxider opened a new issue #3247: Failed to submit topology to standalone cluster

Vxider opened a new issue #3247: Failed to submit topology to standalone cluster
URL: https://github.com/apache/incubator-heron/issues/3247
 
 
   Hi, I am setting up a four node standalone cluster following the [official document](https://apache.github.io/incubator-heron/docs/operators/deployment/schedulers/standalone/).
   
   I got the successful startup message
   
   ```
   heron-admin standalone cluster start                                    4.26 ⏱
   [2019-04-26 17:31:53 +0000] [INFO]: Roles:
   [2019-04-26 17:31:53 +0000] [INFO]:  - Master Servers: ['10Gdell125']
   [2019-04-26 17:31:53 +0000] [INFO]:  - Slave Servers: ['10Gdell124', '10Gdell125', '10Gdell126', '10Gdell127']
   [2019-04-26 17:31:53 +0000] [INFO]:  - Zookeeper Servers: ['10Gdell127:12181', '10Gdell126:12181', '10Gdell125:12181', '10Gdell124:12181']
   [2019-04-26 17:31:53 +0000] [INFO]: Updating config files...
   [2019-04-26 17:31:53 +0000] [INFO]: Distributing heron package to nodes (this might take a while)...
   [2019-04-26 17:32:18 +0000] [INFO]: Server: 10Gdell124
   [2019-04-26 17:32:18 +0000] [INFO]: Server: 10Gdell125
   [2019-04-26 17:32:18 +0000] [INFO]: Server: 10Gdell126
   [2019-04-26 17:32:18 +0000] [INFO]: Server: 10Gdell127
   [2019-04-26 17:32:23 +0000] [INFO]: Done distributing packages
   [2019-04-26 17:32:23 +0000] [INFO]: Starting master on 10Gdell125
   [2019-04-26 17:32:24 +0000] [INFO]: Done starting masters
   [2019-04-26 17:32:24 +0000] [INFO]: Starting slave on 10Gdell124
   [2019-04-26 17:32:24 +0000] [INFO]: Starting slave on 10Gdell125
   [2019-04-26 17:32:24 +0000] [INFO]: Starting slave on 10Gdell126
   [2019-04-26 17:32:24 +0000] [INFO]: Starting slave on 10Gdell127
   [2019-04-26 17:32:24 +0000] [INFO]: Done starting slaves
   [2019-04-26 17:32:26 +0000] [INFO]: Starting Heron API Server on 10Gdell125
   [2019-04-26 17:32:26 +0000] [INFO]: Waiting for apiserver to come up... 0
   [2019-04-26 17:32:27 +0000] [INFO]: Waiting for apiserver to come up... 1
   [2019-04-26 17:32:28 +0000] [INFO]: Waiting for apiserver to come up... 2
   [2019-04-26 17:32:29 +0000] [INFO]: Waiting for apiserver to come up... 3
   [2019-04-26 17:32:30 +0000] [INFO]: Waiting for apiserver to come up... 4
   [2019-04-26 17:32:31 +0000] [INFO]: Waiting for apiserver to come up... 5
   [2019-04-26 17:32:32 +0000] [INFO]: Waiting for apiserver to come up... 6
   [2019-04-26 17:32:33 +0000] [INFO]: Waiting for apiserver to come up... 7
   [2019-04-26 17:32:34 +0000] [INFO]: Waiting for apiserver to come up... 8
   [2019-04-26 17:32:35 +0000] [INFO]: Waiting for apiserver to come up... 9
   [2019-04-26 17:32:36 +0000] [INFO]: Waiting for apiserver to come up... 10
   [2019-04-26 17:32:37 +0000] [INFO]: Done starting Heron API Server
   [2019-04-26 17:32:37 +0000] [INFO]: Starting Heron Tools on 10Gdell125
   [2019-04-26 17:32:37 +0000] [INFO]: Waiting for heron-tools to come up... 0
   [2019-04-26 17:32:38 +0000] [INFO]: Done starting Heron Tools
   [2019-04-26 17:32:38 +0000] [INFO]: Heron standalone cluster complete!
   ```
   
   And I have set the `server_url` using the following command
   
   ```
   heron config standalone set service_url http://10Gdell125:9000
   ```
   
   But I cannot submit topology to the cluster
   
   ```
   [2019-04-26 17:35:08 +0000] [ERROR]: HTTPConnectionPool(host='10gdell125', port=9000): Max retries exceeded with url: /api/v1/topologies (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x2249e10>: Failed to establish a new connection: [Errno 111] Connection refused',))
   [2019-04-26 17:35:08 +0000] [ERROR]: Failed to launch topology 'twitterSkew'
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services