[jira] [Assigned] (LIVY-690) Exclude curator in thrift server pom to avoid conflict jars
[ https://issues.apache.org/jira/browse/LIVY-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao reassigned LIVY-690: Assignee: Yiheng Wang > Exclude curator in thrift server pom to avoid conflict jars > --- > > Key: LIVY-690 > URL: https://issues.apache.org/jira/browse/LIVY-690 > Project: Livy > Issue Type: Bug > Components: Thriftserver >Affects Versions: 0.6.0 >Reporter: Yiheng Wang >Assignee: Yiheng Wang >Priority: Major > Fix For: 0.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently, thrift server has a dependency of curator-client:2.12.0 through > the hive service. After the build, a curator-client-2.12.0.jar file will be > generated in the jars folder. It is conflicted with the > curator-client-2.7.1.jar file, which is used by livy server. > We observed that in some JDK, the curator-client-2.12.0.jar is loaded before > the curator-client-2.7.1.jar, and will crash the recovery enabled livy server. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (LIVY-690) Exclude curator in thrift server pom to avoid conflict jars
[ https://issues.apache.org/jira/browse/LIVY-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-690. -- Resolution: Fixed Issue resolved by pull request 239 [https://github.com/apache/incubator-livy/pull/239] > Exclude curator in thrift server pom to avoid conflict jars > --- > > Key: LIVY-690 > URL: https://issues.apache.org/jira/browse/LIVY-690 > Project: Livy > Issue Type: Bug > Components: Thriftserver >Affects Versions: 0.6.0 >Reporter: Yiheng Wang >Priority: Major > Fix For: 0.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently, thrift server has a dependency of curator-client:2.12.0 through > the hive service. After the build, a curator-client-2.12.0.jar file will be > generated in the jars folder. It is conflicted with the > curator-client-2.7.1.jar file, which is used by livy server. > We observed that in some JDK, the curator-client-2.12.0.jar is loaded before > the curator-client-2.7.1.jar, and will crash the recovery enabled livy server. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (LIVY-688) Error message of LivyClient only keep outer stackTrace but discard cause's stackTrace
[ https://issues.apache.org/jira/browse/LIVY-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao reassigned LIVY-688: Assignee: weiwenda > Error message of LivyClient only keep outer stackTrace but discard cause's > stackTrace > - > > Key: LIVY-688 > URL: https://issues.apache.org/jira/browse/LIVY-688 > Project: Livy > Issue Type: Improvement > Components: RSC >Affects Versions: 0.6.0 >Reporter: weiwenda >Assignee: weiwenda >Priority: Trivial > Fix For: 0.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > 1. SparkSession maybe failed when initialize ExternalCatalog at sometime. As > SparkSession call _SharedState.reflect_ to instance an ExternalCatalog, any > exception happened during this process will wrapped by > InvocationTargetException. > IllegalArgumentException > └──InvocationTargetException > └──the indeed Exception > 2. org.apache.livy.rsc.Utils.stackTraceAsString only keep > IllegalArgumentException's stackTrace but discard the indeed Exception's > stackTrace and message, which makes the final > java.util.concurrent.ExecutionException's message ambiguous. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (LIVY-688) Error message of LivyClient only keep outer stackTrace but discard cause's stackTrace
[ https://issues.apache.org/jira/browse/LIVY-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saisai Shao resolved LIVY-688. -- Fix Version/s: 0.7.0 Resolution: Fixed Issue resolved by pull request 237 [https://github.com/apache/incubator-livy/pull/237] > Error message of LivyClient only keep outer stackTrace but discard cause's > stackTrace > - > > Key: LIVY-688 > URL: https://issues.apache.org/jira/browse/LIVY-688 > Project: Livy > Issue Type: Improvement > Components: RSC >Affects Versions: 0.6.0 >Reporter: weiwenda >Priority: Trivial > Fix For: 0.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > 1. SparkSession maybe failed when initialize ExternalCatalog at sometime. As > SparkSession call _SharedState.reflect_ to instance an ExternalCatalog, any > exception happened during this process will wrapped by > InvocationTargetException. > IllegalArgumentException > └──InvocationTargetException > └──the indeed Exception > 2. org.apache.livy.rsc.Utils.stackTraceAsString only keep > IllegalArgumentException's stackTrace but discard the indeed Exception's > stackTrace and message, which makes the final > java.util.concurrent.ExecutionException's message ambiguous. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (LIVY-691) Duplicate jars in assembly jar folder
Yiheng Wang created LIVY-691: Summary: Duplicate jars in assembly jar folder Key: LIVY-691 URL: https://issues.apache.org/jira/browse/LIVY-691 Project: Livy Issue Type: Bug Reporter: Yiheng Wang We found some jars of different version will be generated both in the assembly jar folder. It may cause some problem if there's some API incompatible. So far we found -rw-r--r-- 1 root root 966102 Sep 29 14:53 apache-jsp-8.0.33.jar -rw-r--r-- 1 root root11012 Sep 29 14:53 apache-jsp-9.3.24.v20180605.jar ... -rw-r--r-- 1 root root38015 Sep 29 14:53 commons-logging-1.0.4.jar -rw-r--r-- 1 root root61829 Sep 29 14:52 commons-logging-1.2.jar ... -rw-r--r-- 1 root root 177131 Sep 29 14:52 jetty-util-6.1.26.jar -rw-r--r-- 1 root root 458642 Sep 29 14:52 jetty-util-9.3.24.v20180605.jar ... -rw-r--r-- 1 root root50493 Sep 29 14:53 jsp-api-2.0.jar -rw-r--r-- 1 root root 100636 Sep 29 14:52 jsp-api-2.1.jar ... -rw-r--r-- 1 root root 1208356 Sep 29 14:53 netty-3.7.0.Final.jar -rw-r--r-- 1 root root 1330219 Sep 29 14:52 netty-3.9.9.Final.jar -- This message was sent by Atlassian Jira (v8.3.4#803005)
