CGRU Forum

Hi.
Hm, i just sent a job with a block with no tasks and afserver has not hung.
( i`ve also committed "invalUd" fix).
So our sever is working for about a week with a reduced threads stack with no hung.

Hi. Wake-on-lan states: 1. Free for enough time, ("free" and "time" are configured in a farm setup). 2. Server adds a wakeonlan task in a system job. 3. System job task goes on a ready afrender, puts render node to WOL Falling state, this state you can see in GUI. 4. Afrender con...

Hi.
It will be useful to create a pull request on GutHub for such issues.
https://github.com/CGRU/cgru

Hi.
It will be useful to create a pull request on GutHub for such issues.
https://github.com/CGRU/cgru

Now server thread to process client connections stack size is configurable, by default is 32768:
https://github.com/CGRU/cgru/commit/dbb ... 9b7098R196
And I also running such afserver at work, to watch stability.

Hi.
Now reduced stack size is committed:
https://github.com/CGRU/cgru/commit/ba1 ... 099cdbc1eb
Tomorrow I will launch such afserver at work.

We need at least one more solution as epoll is Linux only (not even UNIX). Later we can add to config what method to choose on Linux. Anyway the most coding work is to change afserver architecture. Now it accepts new connection and raises one thread for it. The thread reads, than do something, that ...

Hi. If you have af_task_update_timeout and af_task_stop_timeout, this means that afrender stopped to send any info about the task. So after parser "self.error=True" afrender killed this task, and just forget about the task, it did not send to afserver that is PBR, and server still thinks t...

But reducing stack is a temporary (but at seems that working) solution. It is not good architecture to use blocking sockets and raise a thread for each. The best way to raise 1 thread once to for all client sockets in a non-blocking manner. Many thanks to eliemichel as he already developed it here: ...

Hi. Now new stack size for threads is not committed. I just checking it on a testing platform. Yesterday it solved jobs all day long with 400 afrenders with no hung. So i think that reducing stack size is a solution of this problem. Now i planning to make stack size parameter in thread class. And ra...