Amazon Elasticsearch ElasticsearchIT takes 16 minutes to run

Description

  1. Crate an elasticsearch instance. You can use the free t2.micro. I also tested with m3.medium

  2. Change the Elasticsearch environment variable to point at the AWS Elasticsearch domain

  3. Run all unit test or just ElasticSearchIT
    It should take over 10 minutes to run. I have not yet run it in the debugger to where it is hanging.

  • The test eventually passes

  • All tests take very long ElasticsearchIndexMappingIT takes 107 seconds

Environment

Windows 10, Java 8, Amazon Elasticsearch, t2.micro, also tested with m3.medium

Activity

Show:
Sanne Grinovero
March 29, 2016, 11:45 AM

I'm assuming you are running the Hibernate Search test locally, connected to the t2.micro instance on AWS ?

I'll see what we can do to improve performance, but I don't think it will ever be efficient to run over a WAN connection which could span across continents. Not least t2.micro is really micro.

It's an interesting data point though, thanks!

Joe
March 29, 2016, 12:06 PM

I tried this with an m3.medium and got the same timing. Yeah, the WAN would be slow if it has a lot of calls or there is some kind of timing/timeout issue.

I can try running it from an EC2 instance inside AWS to see if the timing is different. That may take a couple days.

Gunnar Morling
May 3, 2016, 6:35 AM

Hey , any further insights on this by any chance?

Sanne Grinovero
May 21, 2016, 9:35 PM

Looks like AWS is currently running exclusively version 1.5.2 of Elasticsearch, which will fail several of our tests as we've been aiming at version 2.+

{"query":{"filtered":{"query":{"match_all":{,"filter":{"bool":{"must":[{"type":{"value":"org.hibernate.search.elasticsearch.test.filter.Driver"}},{"term":{"teacher":{"value":"andre","boost":1.0}}},{"term":{"score":5}}]}}}}}}}

We get:

term filter does not support [boost]

Sanne Grinovero
May 21, 2016, 10:10 PM

For the record, it took 23 minutes to run the tests for me. (running the tests from the /elasticsearch directory only).

I'm located in London UK, while the ES instance I've been using is a micro instance running on AWS in North Virginia (zone us-east-1) so I expect quite bad latency - in fact I measured about 440 milliseconds for a round trip.

I'll also set it up on our CI environment, which is located in a different AWS zone but also in North Virginia.. unfortunately some coding changes will be needed to allow injecting hostname overrides as a property, and to make it compatible with this ES version too (I got 85 test failures out of 464).

Assignee

Sanne Grinovero

Reporter

Joe

Labels

None

Suitable for new contributors

None

Pull Request

None

Feedback Requested

None

Components

Fix versions

Affects versions

Priority

Minor
Configure