[
https://issues.apache.org/jira/browse/ATLAS-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17288413#comment-17288413
]
Kevin Risden commented on ATLAS-4163:
-------------------------------------
[~sarath] thanks for triggering the precommit. It looks like it failed, but
with no error - just like it stopped.
The end of the log message is:
{code:java}
...
[INFO] <<< jetty-maven-plugin:9.3.14.v20161028:deploy-war (start-jetty) <
validate @ hbase-bridge <<<
[INFO]
[INFO]
[INFO] --- jetty-maven-plugin:9.3.14.v20161028:deploy-war (start-jetty) @
hbase-bridge ---
[INFO] Logging initialized @5359609ms
[INFO] Configuring Jetty for project: Apache Atlas Hbase Bridge
[INFO] Context path = /
[INFO] Tmp directory =
/home/jenkins/jenkins-agent/workspace/Atlas/PreCommit-ATLAS-Build-Test/addons/hbase-bridge/target/tmp
[INFO] Web defaults = org/eclipse/jetty/webapp/webdefault.xml
[INFO] Web overrides = none
[INFO] jetty-9.3.14.v20161028
log4j:WARN No appenders could be found for logger
(org.apache.curator.framework.state.ConnectionStateManager).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
info.
{code}
I know ASF Jenkins had some issues a few days ago so maybe thats related? I
didn't look too much closer. I didn't see a way to retrigger the build either.
> Upgrade elasticsearch version to 6.8.14
> ---------------------------------------
>
> Key: ATLAS-4163
> URL: https://issues.apache.org/jira/browse/ATLAS-4163
> Project: Atlas
> Issue Type: Task
> Affects Versions: 2.1.0
> Reporter: Kevin Risden
> Priority: Minor
> Attachments: ATLAS-4163.patch
>
>
> ATLAS-4052 upgraded to Elasticsearch 6.8.3 which isn't the latest. There are
> some CVEs associated with Elasticsearch 6.8.3 and so should upgrade to 6.8.14
> which is the latest as of Feb 2021.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
