[CI][Packaging][Release] Jobs that run on ARM self-hosted runners are flaky and failing with communication lost

[raulcd]

Describe the bug, including details regarding any error messages, version, and platform.

The k8s self-hosted runners solution is slightly flaky lately. See for example:

• centos-9-stream-arm64
• ubuntu-jammy-arm64
• ubuntu-noble-arm64

The error:

The self-hosted runner: k8s-runners-linux-arm-8g6tn-gpmc7 lost communication with the server.

I am seeing this happening on the maintenance branch for the release too.

Component(s)

Continuous Integration, Packaging, Release

[raulcd]

cc @assignUser

[assignUser]

Will investigate

[assignUser]

This type of error usually happens when the runner pod gets oom or cpu killed, did we increase the feature set that's build or something like that, that might increase memory or cpu use?

[kou]

https://github.com/apache/arrow/pull/44348 may be related. It enables Azure file system.

[kou]

Can we increase assigned resources for the runner?

[assignUser]

Ah yeah that could do it, I'll see what I can do.

[assignUser]

The runner resources where increased, should take effect soon!

[raulcd]

We have moved from self-hosted ARM runners to GitHub hosted runners. We can close this issue now. Thanks for working on this in the past @assignUser