[
https://issues.apache.org/jira/browse/HBASE-25440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17254254#comment-17254254
]
Michael Stack commented on HBASE-25440:
---------------------------------------
Setting the iptables rule doesn't help these it seems:
{code}
21:29:14 [INFO] --- exec-maven-plugin:1.6.0:exec
(make-sure-validation-files-are-in-sync) @ hbase-shaded-check-invariants ---
21:29:14 [ERROR] Command execution failed.
java.io.IOException: Stream closed
at java.lang.ProcessBuilder$NullOutputStream.write (ProcessBuilder.java:433)
at java.io.OutputStream.write (OutputStream.java:116)
at java.io.BufferedOutputStream.flushBuffer (BufferedOutputStream.java:82)
at java.io.BufferedOutputStream.flush (BufferedOutputStream.java:140)
at java.io.FilterOutputStream.close (FilterOutputStream.java:158)
at org.apache.commons.exec.DefaultExecutor.closeProcessStreams
(DefaultExecutor.java:306)
at org.apache.commons.exec.DefaultExecutor.executeInternal
(DefaultExecutor.java:387)
at org.apache.commons.exec.DefaultExecutor.execute
(DefaultExecutor.java:166)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:804)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:751)
at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:313)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
{code}
> create-release fails download of artifacts on gcp
> -------------------------------------------------
>
> Key: HBASE-25440
> URL: https://issues.apache.org/jira/browse/HBASE-25440
> Project: HBase
> Issue Type: Improvement
> Components: create-release
> Reporter: Michael Stack
> Priority: Major
>
> Noticed this running test release-candidate builds up on gcp. The build fails
> as we fail to download artifacts ("Connection reset"). For example:
> {code}
> 2020-12-23T16:49:05Z Command FAILED. Check full logs for details.
> 16:49:05 [ERROR] Failed to execute goal on project hbase-metrics: Could not
> resolve dependencies for project
> org.apache.hbase:hbase-metrics:jar:2.4.1-rm_test_gcp: Failed to collect
> dependencies at io.dropwizard.metrics:metrics-core:jar:3.2.6: Failed to read
> artifact descriptor for io.dropwizard.metrics:metrics-core:jar:3.2.6: Could
> not transfer artifact io.dropwizard.metrics:metrics-core:pom:3.2.6 from/to
> central (https://repo.maven.apache.org/maven2): Transfer failed for
> https://repo.maven.apache.org/maven2/io/dropwizard/metrics/metrics-core/3.2.6/metrics-core-3.2.6.pom:
> Connection reset -> [Help 1]
> {code}
> If I rerun, we usually move beyond the above but might fail later on another
> artifact.
> HBASE-25438 updates the mvn used building to 3.6.3 which is supposed to have
> a better wagon plugin but it doesn't seem to help (I tried turning off wagon
> pooling and upping retries but probably no good when the connection reset)
> This looks related... trying it.
> https://stackoverflow.com/questions/65349648/why-does-my-maven-dependency-fetching-fail-with-a-connection-reset-when-running
> I'm on debian when above happens:
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
