Replies: 5 comments 1 reply
-
Why you use ozone 1.3.0? this installation worked before? |
Beta Was this translation helpful? Give feedback.
-
Here are a few reasons why we are using Ozone 1.3.0 as a client:
We encounter this problem while trying to combine Spark to perform large-scale parallel execution of individually executable data processing tasks. |
Beta Was this translation helpful? Give feedback.
-
Not an expert in this area, but I can help you in ensuring the basics are correct.
Following from this issue, I think Spark may have to use this jar:
Check if you have this jar in the classpath. |
Beta Was this translation helpful? Give feedback.
-
@kmizumar What's the latest on this, were you able to resolve the problem? @GeorgeJahad will you be able to help here? |
Beta Was this translation helpful? Give feedback.
-
Sorry, I'm not working on Ozone right now and don't have time to look. If it is the same problem as the one I was working on, then this is the key comment: In particular:
|
Beta Was this translation helpful? Give feedback.
-
Hello experts, I need your help.
Our spark driver fails to create an OzoneClient object with the following stack, after showing tons of
INFO RetryInvocationHandler: java.lang.IllegalStateException, while invoking $Proxy36.submitRequest over nodeId=om-06,nodeAddress=<REDACTED>:9862 after 499 failover attempts. Trying to failover immediately.
We're doing nothing special in creating the object and confirmed our
core-site.xml
andozone-site.xml
work fine with another simple Ozone Java API client.I suspect this is a kind of dependency problem.
Could anyone please shed light on this? How can we investigate the root cause of this issue?
#6549 looks similar, but I'm not confident.
Beta Was this translation helpful? Give feedback.
All reactions