Skip to content

Dataproc - Unable to upgrade to 5.4.0 libraries-bom #2942

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

Closed
lesv opened this issue May 19, 2020 · 10 comments
Closed

Dataproc - Unable to upgrade to 5.4.0 libraries-bom #2942

lesv opened this issue May 19, 2020 · 10 comments
Assignees
Labels
api: dataproc Issues related to the Dataproc API. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. 🚨 This issue needs some love. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@lesv
Copy link
Contributor

lesv commented May 19, 2020

Found in #2937
https://source.cloud.google.com/results/invocations/f7079bef-8021-4a51-b88a-24740f041202/targets/cloud-devrel%2Fjava%2Fjava-docs-samples%2Fjava11%2Fpresubmit/log

Java 11

------------------------------------------------------------
- testing dataproc
------------------------------------------------------------

[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 299.771 s <<< FAILURE! - in InstantiateInlineWorkflowTemplateTest
[ERROR] InstantiateInlineWorkflowTemplateTest.instanstiateInlineWorkflowTest  Time elapsed: 299.769 s  <<< ERROR!
java.util.concurrent.CancellationException: Task was cancelled.
	at com.google.common.util.concurrent.AbstractFuture.cancellationExceptionWithCause(AbstractFuture.java:1388)
	at com.google.common.util.concurrent.AbstractFuture.getDoneValue(AbstractFuture.java:562)
	at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:545)
	at com.google.common.util.concurrent.FluentFuture$TrustedFuture.get(FluentFuture.java:86)
	at com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:62)
	at com.google.api.gax.longrunning.OperationFutureImpl.get(OperationFutureImpl.java:127)
	at InstantiateInlineWorkflowTemplate.instantiateInlineWorkflowTemplate(InstantiateInlineWorkflowTemplate.java:111)
	at InstantiateInlineWorkflowTemplateTest.instanstiateInlineWorkflowTest(InstantiateInlineWorkflowTemplateTest.java:59)

@bradmiro @stephaniewang526 PTAL

@lesv lesv added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. api: dataproc Issues related to the Dataproc API. labels May 19, 2020
@bradmiro
Copy link
Contributor

@chingor13 are you familiar with any issues regarding LROs timing out at five minutes? I'm able to repeat this error consistently only when using the Java client library.

@bradmiro
Copy link
Contributor

Seems to be a breaking change as of Dataproc 0.121.0

@yoshi-automation yoshi-automation added 🚨 This issue needs some love. and removed 🚨 This issue needs some love. labels May 26, 2020
@bradmiro
Copy link
Contributor

bradmiro commented Jun 4, 2020

Still working on this... the cause has been identified. The timeouts on the client changed in this release, figuring out if this can be fixed or if it needs to be fixed in the sample.

@bradmiro
Copy link
Contributor

bradmiro commented Jun 9, 2020

Should be fixed in the next release.

@bradmiro
Copy link
Contributor

bradmiro commented Jun 10, 2020

This appears fixed via a local test with the latest Java-Dataproc release - 0.122.3

@lesv
Copy link
Contributor Author

lesv commented Jun 11, 2020

@bradmiro Can you request an update to GoogleAPIs/google-cloud-bom to the correct version so this get's fixed?

@lesv
Copy link
Contributor Author

lesv commented Jun 11, 2020

@elharo FYI so you can follow the issue.

@lesv
Copy link
Contributor Author

lesv commented Jun 11, 2020

@bradmiro It's actually googleapis/java-cloud-bom

@meredithslota
Copy link
Contributor

#2937 looks merged — is this fixed?

@lesv
Copy link
Contributor Author

lesv commented Jun 18, 2020

Appears to have been fixed in #3187

Thank you everyone!

@lesv lesv closed this as completed Jun 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: dataproc Issues related to the Dataproc API. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. 🚨 This issue needs some love. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

4 participants