-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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.
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
Add ExitOnOutOfMemoryError to java connectors and bump versions #10256
Add ExitOnOutOfMemoryError to java connectors and bump versions #10256
Conversation
/test connector=connectors/destination-azure-blob-storage
|
/test connector=connectors/destination-gcs
|
/test connector=connectors/source-mysql
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure why the gcs test failed. will try to repro locally, but I don't think it blocks this PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clutch!
Seeing the scope of this PR makes it feel like we should figure out how to inherit these JVM options across connectors! Definitely not a right now thing. Just an observation.
@cgardens there is sort of an existing issue to take care of that, which was created when we added the max RAM percentage flag originally: https://github.com/airbytehq/airbyte-internal-issues/issues/264 |
/publish connector=connectors/destination-azure-blob-storage
|
/publish connector=connectors/destination-bigquery-denormalized
|
/publish connector=connectors/destination-bigquery
|
/publish connector=connectors/destination-cassandra
|
/publish connector=connectors/destination-clickhouse-strict-encrypt
|
/publish connector=connectors/destination-clickhouse
|
/publish connector=connectors/destination-csv
|
/publish connector=connectors/destination-databricks
|
/publish connector=connectors/destination-dev-null
|
/publish connector=connectors/destination-dynamodb
|
/publish connector=connectors/destination-elasticsearch
|
state of the world:
|
@lmossman, by the way, we no longer need to update the version in those json definition files (e.g. |
In the future, it is probably better to merge in the changes first, and publish the connectors in separate PRs. Having one PR to update so many connectors is very messy. For example, none of the changelog is updated in the connector documentation. Also some of the connectors have been published with this PR, but the change is not merged, which can block other PRs trying to update the same connectors. |
/publish connector=connectors/destination-gcs
|
wahoo! thanks for pushing it across the finish line. |
+1 . agreed with liren. |
See context here: https://airbytehq-team.slack.com/archives/C02U46QK5C3/p1644534663479069?thread_ts=1644532106.854279&cid=C02U46QK5C3
We have connectors that are hanging due to the java thread throwing an OutOfMemoryError, but the pod not actually failing. Adding this flag will cause the process to exit, correctly closing the pod and surfacing the OOM issue faster.