Sahara cluster stuck in waiting "resource could not be found"

asked 2014-12-03 14:33:50 -0500

mohan yang gravatar image

updated 2014-12-03 18:44:01 -0500

smaffulli gravatar image

Hello: When lucking a hadoop closer using sahara, the cluster's status stuck in waiting status, and after about an hour, the cluster change in to ERROR. The instances can be launched, and all name node and data nodes are in "running" status.

We are using image "sahara-icehouse-vanilla-1.2.1-ubuntu-13.10.qcow2", and i've disabled the floating IP.

I noticed, while the cluster is "waiting", the scree-sahara.logs continues to do this:

2014-12-03 12:24:57.097 7961 INFO urllib3.connectionpool [-] Starting new HTTP connection (1): 10.0.20.250
2014-12-03 12:24:57.098 7961 DEBUG urllib3.connectionpool [-] Setting read timeout to None _make_request /usr/lib/python2.7/dist-packages/urllib3/connectionpool.py:375
2014-12-03 12:24:57.157 7961 DEBUG urllib3.connectionpool [-] "GET /v2/c82757       32c8dd4122ba26ffaf2cde3daa/servers/5d6c4c99-5d6f-423a-afa9-7e80d3185375 HTTP/1.1" 200 1706 _make_request /usr/lib/python2.7/dist-packages/urllib3/connectionpool.py:415

It just continues to generate these 3 lines of logs repeatedly. By the way, when the cluster change to "ERROR", the reason is :

2014-12-03 12:26:32.658 7961 ERROR sahara.service.ops [-] Error during operating cluster 'pingba' (reason: The resource could not be found. (HTTP 404))
edit retag flag offensive close merge delete

Comments

By the way, when the cluster change to "ERROR", the reason is : 2014-12-03 12:26:32.658 7961 ERROR sahara.service.ops [-] Error during operating cluster 'pingba' (reason: The resource could not be found. (HTTP 404))

mohan yang gravatar imagemohan yang ( 2014-12-03 14:37:59 -0500 )edit