[
https://issues.apache.org/jira/browse/JENA-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225075#comment-16225075
]
ASF GitHub Bot commented on JENA-1413:
--------------------------------------
GitHub user osma opened a pull request:
https://github.com/apache/jena/pull/301
JENA-1413: increase Elasticsearch startup timeout to 60 seconds
This attempts to fix intermittent build problems with jena-text-es by
increasing the startup timeout.
See https://issues.apache.org/jira/browse/JENA-1413
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/osma/jena jena-1413-es-it-timeout
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/jena/pull/301.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #301
----
commit 2171ffee6ed5337a0645c436d0f7d5cea5e3d17f
Author: Osma Suominen <[email protected]>
Date: 2017-10-30T14:58:53Z
JENA-1413: increase Elasticsearch startup timeout to 60 seconds
----
> jena-text-es integration tests sometimes fail
> ---------------------------------------------
>
> Key: JENA-1413
> URL: https://issues.apache.org/jira/browse/JENA-1413
> Project: Apache Jena
> Issue Type: Bug
> Components: Text
> Affects Versions: Jena 3.5.0
> Environment: Ubuntu 16.04
> Slow machine (HDD, high load...)
> Reporter: Osma Suominen
> Assignee: Osma Suominen
> Priority: Minor
>
> The symptom is that the jena-text-es build fails with this error:
> [ERROR] Failed to execute goal
> com.github.alexcojocaru:elasticsearch-maven-plugin:5.2:runforked
> (start-elasticsearch) on project jena-text-es: Condition returned by method
> "waitToStart" in class
> com.github.alexcojocaru.mojo.elasticsearch.v2.client.Monitor was not
> fulfilled within 30 seconds. -> [Help 1]
> The problem seems to be that Elasticsearch starts up slowly and the
> elasticsearch-maven-plugin times out at 30 seconds.
> I found a way to trigger this by simulating high load using the stress
> utility:
> {noformat}
> $ stress --cpu 3 -i 3 -d 3
> stress: info: [29489] dispatching hogs: 3 cpu, 3 io, 0 vm, 3 hdd
> {noformat}
> Increasing the ES startup timeout should help. I will prepare a PR shortly.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
