Github user tzulitai commented on a diff in the pull request:

    https://github.com/apache/flink/pull/3358#discussion_r102647903
  
    --- Diff: 
flink-connectors/flink-connector-elasticsearch-base/src/main/java/org/apache/flink/streaming/connectors/elasticsearch/util/RetryRejectedExecutionFailureHandler.java
 ---
    @@ -0,0 +1,46 @@
    +/*
    + * Licensed to the Apache Software Foundation (ASF) under one
    + * or more contributor license agreements.  See the NOTICE file
    + * distributed with this work for additional information
    + * regarding copyright ownership.  The ASF licenses this file
    + * to you under the Apache License, Version 2.0 (the
    + * "License"); you may not use this file except in compliance
    + * with the License.  You may obtain a copy of the License at
    + *
    + *    http://www.apache.org/licenses/LICENSE-2.0
    + *
    + * Unless required by applicable law or agreed to in writing, software
    + * distributed under the License is distributed on an "AS IS" BASIS,
    + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    + * See the License for the specific language governing permissions and
    + * limitations under the License.
    + */
    +
    +package org.apache.flink.streaming.connectors.elasticsearch.util;
    +
    +import 
org.apache.flink.streaming.connectors.elasticsearch.ActionRequestFailureHandler;
    +import org.apache.flink.streaming.connectors.elasticsearch.RequestIndexer;
    +import org.apache.flink.util.ExceptionUtils;
    +import org.elasticsearch.action.ActionRequest;
    +import 
org.elasticsearch.common.util.concurrent.EsRejectedExecutionException;
    +
    +/**
    + * An {@link ActionRequestFailureHandler} that re-adds requests that 
failed due to temporary
    + * {@link EsRejectedExecutionException}s (which means that Elasticsearch 
node queues are currently full),
    + * and fails for all other failures.
    + */
    +public class RetryRejectedExecutionFailureHandler implements 
ActionRequestFailureHandler {
    +
    +   private static final long serialVersionUID = -7423562912824511906L;
    +
    +   @Override
    +   public void onFailure(ActionRequest action, Throwable failure, int 
restStatusCode, RequestIndexer indexer) throws Throwable {
    +           if (ExceptionUtils.containsThrowable(failure, 
EsRejectedExecutionException.class)) {
    +                   indexer.add(action);
    --- End diff --
    
    Regarding the frequency of `EsRejectedExecutionException`, from my 
experience with ES before, they pop up a lot with under-resourced / configured 
ES clusters.
    
    It can flood logs if it isn't treated accordingly, but not logging them can 
be bad too because you'll know nothing about it, unless the sink eventually 
fails with it.
    
    We could also remove the failure logging from the `ElasticsearchSinkBase` 
and let the user be responsible for that, but I'm a bit undecided here. Open to 
suggestions for this!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to