landscape-bot
commented
9 years ago 
Repository health decreased by 0.27% when pulling 952fc8b on NullSoldier:wait-for-green into 13e0838 on Sparrho:master.
- 3 new problems were found (including 0 errors and 3 code smells).
- 3 problems were fixed (including 0 errors and 3 code smells).
I realized my other PR was great for fixing some of the flakes we encountered, but really we need to wait for the green status to avoid all the failures that can happen on production elasticsearch providers. Yellow status does not wait for all shards to finish replication, but green does!
This new solution will create all indices asynchronously and then wait on them all synchronously for a large perf boost. You will only see this error if you're using a properly configured cluster production cluster.