Created on 08-08-2017 08:10 AM - edited 08-17-2019 09:33 PM
When i try to deploy a SAM application on HDF 3 enviroment i am getting the following error :
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
SAM log :
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
at org.apache.storm.submit.command.DependencyResolverMain.main(DependencyResolverMain.java:86)
Caused by: org.eclipse.aether.resolution.DependencyResolutionException: Failed to read artifact descriptor for org.apache.kafka:kafka-clients:jar:0.10.2.1
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:387)
at org.apache.storm.submit.dependency.DependencyResolver.resolve(DependencyResolver.java:95)
at org.apache.storm.submit.command.DependencyResolverMain.main(DependencyResolverMain.java:75)
Caused by: org.eclipse.aether.collection.DependencyCollectionException: Failed to read artifact descriptor for org.apache.kafka:kafka-clients:jar:0.10.2.1
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:208)
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:341)
... 2 more
Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.kafka:kafka-clients:jar:0.10.2.1
at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:329)
at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:217)
at org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:202)
... 3 more
Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not transfer artifact org.apache.kafka:kafka-clients:pom:0.10.2.1 from/to central (http://repo1.maven.org/maven2/
I guess it have something to do with this Sam property :
maven.repo.url : hwx-public^http://repo.hortonworks.com/content/groups/public/,hwx-private^http://nexus-private.hortonworks.com/...
I guess that SAM is trying to connect to maven to download some Dependencies , however i can't have internet access on my server , is there any workaround ?
Thanks in advance
Created 08-08-2017 05:39 PM
Can you predownload or put in a proxy.
Perhaps build an example code and copy over all the local JARS from .mvn repo
Created 09-01-2017 06:21 PM
@Timothy Spann I wish someone could see my post. I think It's a bug.
Based on HDF Release Notes the Storm version is 1.1.0, and this version 1.1.0 does not have proxy URL feature which can be seen in Storm 1.0.4.
From this page (https://github.com/apache/storm/releases), The Release time of Strom v 1.1.0 is earler than Storm 1.0.4.
Created 09-04-2017 03:10 AM
Sorry there was a miss on Storm side to not pulling necessary patch (STORM-2598) to HDF 3.0.0 version line of Storm. The patch is also not released via Apache Storm officially (targeted to 1.2.0).
Please try out workaround below:
.m2
directory in 'storm' user's home directory..m2
directory in 'storm' user's home directory, and apply 1.a.I just filed the issue and try to provide a patch shortly.
Created 09-05-2017 06:02 AM
I cannot solve the problem by this method. And please advise. Thanks.
Created 09-08-2017 05:48 PM
Upgrade the the newest version
Created 09-12-2017 10:03 AM
Which version will fix this issue?
Created 10-10-2017 11:13 PM
I provided the patch and now I believe the fix will be provided to HDF 3.0.2.
You can still try out workaround via my above instruction, but during placing artifacts you need to check artifacts (jar/pom) are placed along with metafile (_remote.repositories), and the repository name is 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.
Created 05-28-2018 12:41 PM
Hi all,
I'm using version 3.1.0 of HDF and I have the exact same issue when following the tutorial, step 3, part 4 "Click on the start button to deploy the topology".
I am using the container version of HDF and my host is a Centos 7 running behind a proxy.
I tried to reproduce the steps described by Jungtaek Lim, but I do not have either any .m2 repository nor a "local-repo" repository in any folder of my container.
I do, however have a "local-repo" file on /tmp/hsperfdata_streamline/local-repo, but I don't understand how I should manually add artefacts to the installation.
Any suggestions would be of great help. Thanks in advance.
Regards,
Yannick
Created 05-30-2018 07:53 AM
We are facing the same issue. Please help.