Slicer goes to completed status when there was a timeout error from ES

[kstaken]

We had a job that went straight to completed status when the slicer had a timeout error connecting to the ES cluster. Didn't appear to be any retries.

{"name":"teraslice","hostname":"nodename","pid":164,"ex_id":"4ad04950-0f7f-42c2-a8dc-69012bd86a82","module":"slicer","level":50,"msg":"Error: Request Timeout after 120000ms\n    at /app/source/node_modules/teraslice/node_modules/terafoundation/node_modules/elasticsearch/src/lib/transport.js:336:15\n    at null.<anonymous> (/app/source/node_modules/teraslice/node_modules/terafoundation/node_modules/elasticsearch/src/lib/transport.js:365:7)\n    at Timer.listOnTimeout (timers.js:92:15)","time":"2017-09-14T21:41:32.057Z","v":0}
    {"name":"teraslice","hostname":"nodename","pid":164,"ex_id":"4ad04950-0f7f-42c2-a8dc-69012bd86a82","module":"slicer","level":50,"msg":"error while getting next slice Error: Request Timeout after 120000ms\n    at /app/source/node_modules/teraslice/node_modules/terafoundation/node_modules/elasticsearch/src/lib/transport.js:336:15\n    at null.<anonymous> (/app/source/node_modules/teraslice/node_modules/terafoundation/node_modules/elasticsearch/src/lib/transport.js:365:7)\n    at Timer.listOnTimeout (timers.js:92:15)","time":"2017-09-14T21:41:32.059Z","v":0}