+1 @Sean Owen <sro...@gmail.com> I do not have this issue: [info] SparkSQLEnvSuite: 19:45:15.430 WARN org.apache.hadoop.util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable 19:45:56.366 WARN org.apache.hadoop.hive.conf.HiveConf: HiveConf of name hive.stats.jdbc.timeout does not exist 19:45:56.367 WARN org.apache.hadoop.hive.conf.HiveConf: HiveConf of name hive.stats.retries.wait does not exist 19:45:59.395 WARN org.apache.hadoop.hive.metastore.ObjectStore: Version information not found in metastore. hive.metastore.schema.verification is not enabled so recording the schema version 2.3.0 19:45:59.395 WARN org.apache.hadoop.hive.metastore.ObjectStore: setMetaStoreSchemaVersion called but recording version is disabled: version = 2.3.0, comment = Set by MetaStore root@10.169.161.219 19:45:59.411 WARN org.apache.hadoop.hive.metastore.ObjectStore: Failed to get database default, returning NoSuchObjectException [info] - SPARK-29604 external listeners should be initialized with Spark classloader (45 seconds, 249 milliseconds) 19:46:00.067 WARN org.apache.spark.sql.hive.thriftserver.SparkSQLEnvSuite:
===== POSSIBLE THREAD LEAK IN SUITE o.a.s.sql.hive.thriftserver.SparkSQLEnvSuite, thread names: rpc-boss-3-1, derby.rawStoreDaemon, com.google.common.base.internal.Finalizer, Keep-Alive-Timer, Timer-3, BoneCP-keep-alive-scheduler, shuffle-boss-6-1, BoneCP-pool-watch-thread ===== [info] ScalaTest [info] Run completed in 46 seconds, 676 milliseconds. [info] Total number of tests run: 1 [info] Suites: completed 1, aborted 0 [info] Tests: succeeded 1, failed 0, canceled 0, ignored 0, pending 0 [info] All tests passed. On Tue, Feb 23, 2021 at 9:38 AM Sean Owen <sro...@gmail.com> wrote: > +1 LGTM, same results as last time. Does anyone see the error below? It is > probably env-specific as the Jenkins jobs don't hit this. Just checking. > > SPARK-29604 external listeners should be initialized with Spark > classloader *** FAILED *** > java.lang.RuntimeException: [download failed: > tomcat#jasper-compiler;5.5.23!jasper-compiler.jar, download failed: > tomcat#jasper-runtime;5.5.23!jasper-runtime.jar, download failed: > commons-el#commons-el;1.0!commons-el.jar, download failed: > org.apache.hive#hive-exec;2.3.7!hive-exec.jar] > at > org.apache.spark.deploy.SparkSubmitUtils$.resolveMavenCoordinates(SparkSubmit.scala:1420) > at > org.apache.spark.sql.hive.client.IsolatedClientLoader$.$anonfun$downloadVersion$2(IsolatedClientLoader.scala:122) > at org.apache.spark.sql.catalyst.util.package$.quietly(package.scala:42) > at > org.apache.spark.sql.hive.client.IsolatedClientLoader$.downloadVersion(IsolatedClientLoader.scala:122) > at > org.apache.spark.sql.hive.client.IsolatedClientLoader$.liftedTree1$1(IsolatedClientLoader.scala:64) > at > org.apache.spark.sql.hive.client.IsolatedClientLoader$.forVersion(IsolatedClientLoader.scala:63) > at > org.apache.spark.sql.hive.HiveUtils$.newClientForMetadata(HiveUtils.scala:439) > at > org.apache.spark.sql.hive.HiveUtils$.newClientForMetadata(HiveUtils.scala:352) > at > org.apache.spark.sql.hive.HiveExternalCatalog.client$lzycompute(HiveExternalCatalog.scala:71) > at > org.apache.spark.sql.hive.HiveExternalCatalog.client(HiveExternalCatalog.scala:70) > > On Mon, Feb 22, 2021 at 12:57 AM Hyukjin Kwon <gurwls...@gmail.com> wrote: > >> Please vote on releasing the following candidate as Apache Spark version >> 3.1.1. >> >> The vote is open until February 24th 11PM PST and passes if a majority +1 >> PMC votes are cast, with a minimum of 3 +1 votes. >> >> [ ] +1 Release this package as Apache Spark 3.1.1 >> [ ] -1 Do not release this package because ... >> >> To learn more about Apache Spark, please see http://spark.apache.org/ >> >> The tag to be voted on is v3.1.1-rc3 (commit >> 1d550c4e90275ab418b9161925049239227f3dc9): >> https://github.com/apache/spark/tree/v3.1.1-rc3 >> >> The release files, including signatures, digests, etc. can be found at: >> <https://dist.apache.org/repos/dist/dev/spark/v3.1.1-rc1-bin/> >> https://dist.apache.org/repos/dist/dev/spark/v3.1.1-rc3-bin/ >> >> Signatures used for Spark RCs can be found in this file: >> https://dist.apache.org/repos/dist/dev/spark/KEYS >> >> The staging repository for this release can be found at: >> https://repository.apache.org/content/repositories/orgapachespark-1367 >> >> The documentation corresponding to this release can be found at: >> https://dist.apache.org/repos/dist/dev/spark/v3.1.1-rc3-docs/ >> >> The list of bug fixes going into 3.1.1 can be found at the following URL: >> https://s.apache.org/41kf2 >> >> This release is using the release script of the tag v3.1.1-rc3. >> >> FAQ >> >> =================== >> What happened to 3.1.0? >> =================== >> >> There was a technical issue during Apache Spark 3.1.0 preparation, and it >> was discussed and decided to skip 3.1.0. >> Please see >> https://spark.apache.org/news/next-official-release-spark-3.1.1.html for >> more details. >> >> ========================= >> How can I help test this release? >> ========================= >> >> If you are a Spark user, you can help us test this release by taking >> an existing Spark workload and running on this release candidate, then >> reporting any regressions. >> >> If you're working in PySpark you can set up a virtual env and install >> the current RC via "pip install >> https://dist.apache.org/repos/dist/dev/spark/v3.1.1-rc3-bin/pyspark-3.1.1.tar.gz >> " >> and see if anything important breaks. >> In the Java/Scala, you can add the staging repository to your projects >> resolvers and test >> with the RC (make sure to clean up the artifact cache before/after so >> you don't end up building with an out of date RC going forward). >> >> =========================================== >> What should happen to JIRA tickets still targeting 3.1.1? >> =========================================== >> >> The current list of open tickets targeted at 3.1.1 can be found at: >> https://issues.apache.org/jira/projects/SPARK and search for "Target >> Version/s" = 3.1.1 >> >> Committers should look at those and triage. Extremely important bug >> fixes, documentation, and API tweaks that impact compatibility should >> be worked on immediately. Everything else please retarget to an >> appropriate release. >> >> ================== >> But my bug isn't fixed? >> ================== >> >> In order to make timely releases, we will typically not hold the >> release unless the bug in question is a regression from the previous >> release. That being said, if there is something which is a regression >> that has not been correctly targeted please ping me or a committer to >> help target the issue. >> >>
