Hi,
I just wanted to share a short video I made showing some of the new
features in Zuul that work with Gerrit's submitWholeTopic setting to
support testing and merging simultaneous dependencies. Take a look if
you haven't seen the new features.
https://www.youtube.com/watch?v=B64RbNwkIa4
-Jim
Hi Team,
We at Western digital IT team , is using Zuul version R4.1.0 .
We have come across an issue whereby the gearman becomes unresponsive without any issues with scheduler service .
We are using default gearman that comes bundles with zuul scheduler.
We have scheduler and executer/merger services running on separate vms.
We have come across the issue twice in 3 month’s time. Restarting zuul-scheduler service fixes the issue and zuul works as usual.
Please let us know if it is a known issue and if you have any solution for the same.
We will be happy to provide additional information if required.
Gearman log :
2022-10-27 03:21:22,155 ERROR gear.Server: Received unknown packet: <gear.Packet 0x7f58146fb860 type: UNKNOWN>
2022-10-27 03:21:22,155 ERROR gear.Server: Received unknown packet: <gear.Packet 0x7f58146d87b8 type: UNKNOWN>
2022-10-27 03:21:22,155 ERROR gear.Server: Received unknown packet: <gear.Packet 0x7f58146fb860 type: UNKNOWN>
2022-10-27 03:21:22,155 ERROR gear.Server: Received unknown packet: <gear.Packet 0x7f58146d87b8 type: UNKNOWN>
We were able to telnet to the gearman port on the scheduler host during this time of issue occurrence.
[root@uls-op-zuul4 zuul]# telnet 127.0.0.1<http://127.0.0.1> 4730
Trying 127.0.0.1<http://127.0.0.1>...
Connected to 127.0.0.1<http://127.0.0.1>.
The zuul webservice becomes unresponsive with the following error in log :
2022-10-27 05:27:22,387 DEBUG zuul.RPCClient: Submitting job zuul:tenant_list with data {}
2022-10-27 05:32:22,388 ERROR gear.Client.b'Zuul Web Server': Connection <gear.Connection 0x7f9f9a14be80 host: uls-op-zuul4.wdc.com<http://uls-op-zuul4.wdc.com> port: 4730> timed out waiting for a response to a submit job request: <gear.Job 0x7f9f88730fd0 handle: None name: zuul:tenant_list unique: 1666848442.3878057>
We can see the following error in scheduler log even though the scheduler service is up and running
2022-10-27 06:35:16,589 ERROR gear.Client.b'Zuul Merge Client': Connection <gear.Connection 0x7f58104de128 host: uls-op-zuul4.wdc.com<http://uls-op-zuul4.wdc.com> port: 4730> timed out waiting for a response to a submit job request: <gear.Job 0x7f578d950e80 handle: None name: merger:merge unique: 29be9ce958ef4d19b0e75e274c6dd741>
Regards,
Mithun Mistry
IT engineering , Western digital