I don't think this plugin is receiving development any longer, but I thought I'd record this issue for posterity.
This plugin should be raising a ReliableException for most errors that it encounters, but it is not.
For instance, when the connector tries to establish a connection to Elasticsearch, but that times out for some reason (maybe Elasticsearch is temporarily down), this connector should raise RetriableException. The connection is something that should be retried.
Since this connector plugin does not do that, all of the Tasks associated with the configured connector using this plugin will rapidly go into Failed state. The connector will show as Running, but with all tasks in Failed state, no data will ever flow. This requires human intervention to restart the connector.
Elasticsearch downtimes or network interruptions are going to happen, and this connector should be able to weather those without human intervention.
I don't think this plugin is receiving development any longer, but I thought I'd record this issue for posterity.
This plugin should be raising a ReliableException for most errors that it encounters, but it is not.
For instance, when the connector tries to establish a connection to Elasticsearch, but that times out for some reason (maybe Elasticsearch is temporarily down), this connector should raise RetriableException. The connection is something that should be retried.
Since this connector plugin does not do that, all of the Tasks associated with the configured connector using this plugin will rapidly go into Failed state. The connector will show as Running, but with all tasks in Failed state, no data will ever flow. This requires human intervention to restart the connector.
Elasticsearch downtimes or network interruptions are going to happen, and this connector should be able to weather those without human intervention.