Fix issues that ElasticSearchSink may retry indefinitely on exception

[allenxwang]

ElasticSearchSink will automatically re-enqueue messages if the batch failed due to an exception. It is discovered that a NullPointerException might be thrown which causes the indefinitely retries on the batch. Also, it will by default sleep 60 seconds before re-enqueuing which causes huge delay during the retry cycles.

The pull request tries to address the following issue:

• The behavior of automatic re-enqueue is made configurable and is turned off by default
• Retry will be done by RestClient automatically and the times of retry is explicitly configured. Previously retry is not properly enabled because POST is used and RestClient does not automatically retry on POST upon ReadTimeout.
• Sleep behavior is turned off by default and must be explicitly configured to enable.

[cloudbees-pull-request-builder]

NetflixOSS » suro » suro-pull-requests #64 SUCCESS This pull request looks good

[cloudbees-pull-request-builder]

suro-pull-requests #232 SUCCESS This pull request looks good

[cloudbees-pull-request-builder]

NetflixOSS » suro » suro-pull-requests #65 SUCCESS This pull request looks good

[stevenzwu]

LGTM

[cloudbees-pull-request-builder]

suro-pull-requests #233 FAILURE Looks like there's a problem with this pull request