xBis7 opened a new pull request, #51586:
URL: https://github.com/apache/airflow/pull/51586

   <!--
    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.
    -->
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of an existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   We are using Airflow with Kubernetes and we are occasionally experiencing 
failures due to DNS resolution blips. These failures are temporary and usually 
take mere seconds to go away.
   
   The failure is occurring while a new db connection is required and Airflow 
performs a DNS lookup on the db hostname.
   
   This can be resolved by retrying to establish the DB connection but there 
are better approaches.
   
   This patch is adding a config flag that enables a db discovery check. If the 
option is turned on, we run a `socket.getaddrinfo(...)` on the db hostname to 
see if it can be resolved.
   
   This approach is chosen for the following reasons
   * `socket.getaddrinfo(...)` is less expensive and much faster than retrying 
to create a new session
   * not all kinds of DNS errors are temporary and must be retried.
     * e.g. a wrong value on the database config option `sql_alchemy_conn` is 
also a DNS error but it shouldn't be retried 
     * in case of an exception, the error that we get from 
`socket.getaddrinfo(...)` carries an error code which can be used for  
distinguishing between the different DNS errors
     * `create_session()` will give us an exception with the same error message 
but no other info
     * the error code is more reliable than the error message which might be 
prone to changes during a new version update of the component that is 
generating it
   
   I've added a unit test and an integration test. The integration test hasn't 
been added under the `integration` package because it doesn't need any 
integration other than a db backend. The code is db agnostic but for the test I 
used specifically a postgres backend because it's easier to just hardcode a 
postgres address.
   
   The check is turned off by default.
   
   
   <!-- Please keep an empty line above the dashes. -->
   ---
   **^ Add meaningful description above**
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in a 
newsfragment file, named `{pr_number}.significant.rst` or 
`{issue_number}.significant.rst`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to