Joe Plunkett wrote:
> If i "stop" the node then "start" the node, it comes back to life for another
> pass
> or two, but invariably, does not run for that long (certainly not the all
> night/work time runs that my other two nodes are capable of)..
>
> Note I didn't notice until reading the other post, but stopping and starting
> the
> node also seems to leave many transcode processes running on that node.
> Alternatively if when the node is in the "running" state (but not actually
> running), if i kill the older transcode process, the status on the cluster
> control
> immediately begins to show status again.
This is a bug. Stopping nodes just doesn't work as expected for know.
This will be fixed for the next release.
Regards,
Jörn
--
$a=$a[8][67][9][0][42][214][82][78][0][50][69][68][69][82][0][73][78][0]
[65][0][20][16][0][68][73][77][69][78][83][73][79][78][65][76][0][65][82
][82][65][89]=sub{sub _($){print$_[@z]}($z,$i)=@_;(++$i)while!$z->[$i];$
s+=$i;_ chr($i+32);$s!=2292&&&$a($z->[$i],$c>>$e)};&$a(\@a,$d<<$f);_"\n"
pgpGi5CkfHHYq.pgp
Description: PGP signature
|