Comment 1 for bug 1162977

Revision history for this message
Khai Do (zaro0508) wrote :

I'm seeing something a little different between steps 9 & 10. The functions are not exactly correct.

functions from step #7:
31 50.46.196.80 master-manager : stop:15.185.117.66
32 50.46.196.80 master-exec-0 : build:pear build:pear:!ubuntu build:guava build:grapefruit build:grapefruit:air
33 50.46.196.80 oneiric-668621-exec-0 : build:peach build:peach:linux build:lemon build:lemon:linux&&gcc build:kiwi:ubuntu build:kiwi build:kiwi:centos build:guava build:apple build:apple:oneiric-668621
34 50.46.196.80 precise-668665-exec-0 : build:tangerine:torrent build:tangerine build:tangerine:centos build:pear build:pear:!ubuntu build:peach build:peach:linux build:kiwi build:mango build:kiwi:ubuntu build:mango:torrent build:guava build:kiwi:centos

functions from step #10:
32 50.46.196.80 - : stop:15.185.117.66
31 50.46.196.80 - : build:grapefruit:air build:pear:!ubuntu build:pear build:guava build:grapefruit
33 50.46.196.80 - : build:apple:oneiric-668621 build:kiwi build:lemon build:apple build:kiwi:ubuntu build:guava build:lemon:linux&&gcc build:peach:linux build:peach build:kiwi:centos
34 50.46.196.80 - : build:kiwi build:mango build:kiwi:ubuntu build:mango:torrent build:guava build:tangerine:centos build:kiwi:centos build:tangerine:torrent build:pear:!ubuntu build:pear build:tangerine build:peach:linux build:peach

The functions seem to be correct, however the worker IDs seemed to have dropped off. My initial hunch is that this is a problem with the underlying gearman-java library that does the work to re-establish a lost connection with the server. I will investigate to see wether this is indeed the problem. Will also investigate options for making the connection more robust.