[ https://issues.apache.org/jira/browse/IMPALA-7120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16501236#comment-16501236 ]
Philip Zeyliger commented on IMPALA-7120: ----------------------------------------- I've had the mixed fortune of running into a similar thing in the past. Somewhere in our dependency chain, we depend on {{org.glassfish:javax.el}} but don't specify a version or specify a version range. This causes Maven to iterate through any defined \{{<repository>}}ies to look for versions that would match the restrictions. If any of the remote repositories is down, it dies. In a previous incarnation, Impala would reach out to Cloudera's private repositories, which had been erroneously specified in Sentry's poms. I thought I had fixed this both by fixing Sentry and by pinning the version in: {code:java} <dependencyManagement> <dependencies> <!-- Pin org.glassfish:javax.el explicitly. HBase depends on this indirectly, and it's configured with a range of versions. This causes Maven to talk to all configured repositories, leading both to a lot of chattiness, and also failures if one of the repositories is unavailable. --> <dependency> <groupId>org.glassfish</groupId> <artifactId>javax.el</artifactId> <version>3.0.1-b08</version> </dependency> </dependencies> </dependencyManagement>{code} Based on debug output (running maven with {{-X}}), this takes effect, but it looks like it still talks to remote servers, though I wasn't able to see the exact URL you saw downloading. I'd say let's track this one for a little bit longer. There are heavy-weight ways to tackle this too like setting up a Maven mirror, but it's kind of unpleasant. > GVD failed talking to oss.sonatype.org "Bad Gateway" > ---------------------------------------------------- > > Key: IMPALA-7120 > URL: https://issues.apache.org/jira/browse/IMPALA-7120 > Project: IMPALA > Issue Type: Bug > Components: Infrastructure > Affects Versions: Impala 3.1.0 > Reporter: Tim Armstrong > Assignee: Tim Armstrong > Priority: Critical > Labels: broken-build, flaky > > https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/2368/ > I'm not sure what would cause this. > {noformat} > 22:56:20 ] [WARNING] Could not transfer metadata > com.cloudera.cdh:cdh-root:6.x-SNAPSHOT/maven-metadata.xml from/to > ${distMgmtSnapshotsId} (${distMgmtSnapshotsUrl}): Cannot access > ${distMgmtSnapshotsUrl} with type default using the available connector > factories: BasicRepositoryConnectorFactory > 22:56:20 ] [WARNING] Could not transfer metadata > org.glassfish:javax.el/maven-metadata.xml from/to sonatype-nexus-snapshots > (https://oss.sonatype.org/content/repositories/snapshots): Failed to transfer > file: > https://oss.sonatype.org/content/repositories/snapshots/org/glassfish/javax.el/maven-metadata.xml. > Return code is: 502 , ReasonPhrase:Bad Gateway. > 22:56:20 ] > > > > [WARNING] Could not transfer metadata > org.glassfish:javax.el:3.0.1-b06-SNAPSHOT/maven-metadata.xml from/to > sonatype-nexus-snapshots > (https://oss.sonatype.org/content/repositories/snapshots): Failed to transfer > file: > https://oss.sonatype.org/content/repositories/snapshots/org/glassfish/javax.el/3.0.1-b06-SNAPSHOT/maven-metadata.xml. > Return code is: 502 , ReasonPhrase:Bad Gateway. > 22:56:20 ] [WARNING] Failure to transfer > org.glassfish:javax.el:3.0.1-b06-SNAPSHOT/maven-metadata.xml from > https://oss.sonatype.org/content/repositories/snapshots was cached in the > local repository, resolution will not be reattempted until the update > interval of sonatype-nexus-snapshots has elapsed or updates are forced. > Original error: Could not transfer metadata > org.glassfish:javax.el:3.0.1-b06-SNAPSHOT/maven-metadata.xml from/to > sonatype-nexus-snapshots > (https://oss.sonatype.org/content/repositories/snapshots): Failed to transfer > file: > https://oss.sonatype.org/content/repositories/snapshots/org/glassfish/javax.el/3.0.1-b06-SNAPSHOT/maven-metadata.xml. > Return code is: 502 , ReasonPhrase:Bad Gateway. > 22:56:20 ] > > > > [WARNING] Could not transfer metadata > org.glassfish:javax.el:3.0.1-b07-SNAPSHOT/maven-metadata.xml from/to > sonatype-nexus-snapshots > (https://oss.sonatype.org/content/repositories/snapshots): Failed to transfer > file: > https://oss.sonatype.org/content/repositories/snapshots/org/glassfish/javax.el/3.0.1-b07-SNAPSHOT/maven-metadata.xml. > Return code is: 502 , ReasonPhrase:Bad Gateway. > 22:56:20 ] [WARNING] Failure to transfer > org.glassfish:javax.el:3.0.1-b07-SNAPSHOT/maven-metadata.xml from > https://oss.sonatype.org/content/repositories/snapshots was cached in the > local repository, resolution will not be reattempted until the update > interval of sonatype-nexus-snapshots has elapsed or updates are forced. > Original error: Could not transfer metadata > org.glassfish:javax.el:3.0.1-b07-SNAPSHOT/maven-metadata.xml from/to > sonatype-nexus-snapshots > (https://oss.sonatype.org/content/repositories/snapshots): Failed to transfer > file: > https://oss.sonatype.org/content/repositories/snapshots/org/glassfish/javax.el/3.0.1-b07-SNAPSHOT/maven-metadata.xml. > Return code is: 502 , ReasonPhrase:Bad Gateway. > {noformat} > [~philip] does this looks like something we could fix on our end? Or is it > just an outage on sonatype.org's end? -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org