You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2017/11/02 10:06:00 UTC

[jira] [Updated] (JENA-1413) jena-text-es integration tests sometimes fail

     [ https://issues.apache.org/jira/browse/JENA-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Seaborne updated JENA-1413:
--------------------------------
    Fix Version/s: Jena 3.6.0

> 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
>             Fix For: Jena 3.6.0
>
>
> 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)