Docker Elasticsearch Bulk index timeout

I am running Elasticsearch 2.3 using the docker official builds. I am trying to bulk index a fairly large dataset. The dataset in question is abotu 700mb and on a non dockerized setup takes around 30 minutes. Around 24 hours ago I started the bulk index operation on the docker elasticsearch container. As of yet it still hasn’t completed, worse there is no load on the server which indicates it’s not even attempting to index.

I know the bulk indexing works because I can index a smaller dataset and it works without a problem.

  • docker-machine ls shows state timeout
  • Build ASP.NET Core 1.1 preview4 project in Docker-image microsoft/aspnetcore-build:1.1.0-msbuild
  • docker mysql connection via php
  • How to publish Docker on AWS from sbt-native-packager?
  • Use docker or custom AMI in Amazon ElasticBeanstalk
  • Is it recommended to run docker swarm on single node?
  • Is there any specific settings that I need to be aware of when indexing data over a certain size? or any way to check why it errored?

    Thanks in advance.

  • Docker compose error with docker-engine version
  • Docker Remote API does not list containers
  • What are mix and match attacks? (Docker - snapshot key)
  • Get all containers/images using docker-java client library [closed]
  • Chaos Monkey equivalent for Docker?
  • Dockerize ruby script that takes directories as input/output
  • One Solution collect form web for “Docker Elasticsearch Bulk index timeout”

    For any future people reading this, firstly Hello from the past!

    Secondly, elasticsearch has a default bulk maximum size of 100mb so make sure you’re requests (including posted files) are below that

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.