[
https://issues.apache.org/jira/browse/JENA-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16226164#comment-16226164
]
ASF GitHub Bot commented on JENA-1413:
--------------------------------------
Github user kinow commented on the issue:
https://github.com/apache/jena/pull/301
Sounds like a good idea. I got a build on Windows stuck, in one of the
-text projects. After sending a CTRL+C, noticed a pending java process. Looking
at the command line, I could see it had some elasticsearch mention in it.
Killed manually, and executed the `-Pdev` and `-Pbootstrap` to build the
project. Wonder if this would fix the issue I had?
> 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)
