I get the following error with HDF 3.0.1 when deploying an application.
I'm on a single server that uses a proxy.
I can see it is a known error but no real work around -
The issue is STORM-2598. But Storm 1.2.0 is not out yet. Help!
Topology submission failed due to: java.lang.Exception: Topology could not be deployed successfully: storm deploy command failed with Exception in thread "main" java.lang.RuntimeException: org.eclipse.aether.resolution.DependencyResolutionException: Failed to read artifact descriptor for org.apache.kafka:kafka-clients:jar:0.10.2.1
I believe the fix will be provided to HDF 3.0.2. Before the version comes out, you can try out workaround below:
.m2directory in 'storm' user's home directory.
.m2directory in 'storm' user's home directory, and apply 1.a.
Please note that artifacts (jar/pom) should be placed along with metafile (_remote.repositories), and the repository name should be either 'hwx-public' or 'hwx-private' unless it came from maven public repository.
The best bet is pulling artifacts via SAM with internet access, so that artifacts are downloaded to maven local and repository name in _remote.repositories is properly set (important!). Then copies downloaded artifacts (in maven local) to the machines which don’t have internet access.
I am getting the same issue even in HDF 3.2.0.
I am running HDF on a CentOS cluster with limited internet access. I activated the Proxy for SAM but it doesn't change anything.
Thanks for the response. Any indication to when 3.0.2 is to be released?
We don't have internet access, except via a proxy, so we can't get a list of jars and poms required. Any chance of doing a `ls` and sending those, or is that pushing things?
Sorry I missed this, and we've announced HDF 3.0.2 4 days ago.
Hope this helps!
ps. Please vote my answer and mark as selected to make question answered. Thanks!