Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

maven connection timeout in github action #3121

Closed
jixuan1989 opened this issue Apr 30, 2021 · 1 comment
Closed

maven connection timeout in github action #3121

jixuan1989 opened this issue Apr 30, 2021 · 1 comment

Comments

@jixuan1989
Copy link
Member

There are many CI failed because of connection timeout when maven downloads dependencies.

According to actions/runner-images#1499,
the most reasonable explanation is:
actions/runner-images#1499 (comment)

Maven creates long-living connections and if they are idle more than 4 minutes (while Maven is busy for a while) they became flushed from Azure VM Balancer’s SNAT, but RST packet is not sent to Maven (on VM side) or remote host (packages destination) so the socket is open but no data is sent over it.

And, Apache Pulsar gives a solution:
https://github.com/apache/pulsar/blob/master/.github/workflows/ci-unit.yaml
actions/runner-images#1499 (comment)
@github-actions
Copy link

Hi, this is your first issue in IoTDB project. Thanks for your report. Welcome to join the community!

This was referenced Apr 30, 2021
Merged
Merged
@cliu123 cliu123 mentioned this issue Jan 5, 2022
Merged
dacort added a commit to apache/incubator-livy that referenced this issue Mar 15, 2023
@dacort
Add MAVEN_OPTS to avoid timeouts[1] and ignore livy in m2 cache
b4b178b 
[1] apache/iotdb#3121
gyogal pushed a commit to apache/incubator-livy that referenced this issue Apr 8, 2023
@dacort
[LIVY-972] Add GitHub Action for CI image (#393)
da246ff 
* Add GitHub Action for CI image

* Update push action

* Add sample unit test

* Add matrix based on spark version

* Update spark version to be strings for proper comparison

* Fix syntax

* Add maven cache and integration tests

* Just use actions/cache

* Be more explicty with pom locations because container build is running as root. actions/runner#449

* Add MAVEN_OPTS to avoid timeouts[1] and ignore livy in m2 cache
[1] apache/iotdb#3121

* Update cache paths

* Add codecov
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jixuan1989