[jira] [Resolved] (AIRFLOW-3527) Cloud SQL proxy with UNIX sockets might lead to too long socket path

["Kaxil Naik (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AIRFLOW-3527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kaxil Naik resolved AIRFLOW-3527.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.10.2

> Cloud SQL proxy with UNIX sockets might lead to too long socket path
> --------------------------------------------------------------------
>
>                 Key: AIRFLOW-3527
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3527
>             Project: Apache Airflow
>          Issue Type: Bug
>            Reporter: Jarek Potiuk
>            Priority: Major
>             Fix For: 1.10.2
>
>
> Currently Cloud SQL Proxy with UNIX sockets creates the proxy dir in /tmp/\{UDID1}/folder - which in case of postgres and long instance names might lead to too long name of UNIX socket (the path length for socket is limited to 108 characters in Linux). [http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/sys_un.h.html#tag_13_67_04]
> However in case instance name is long enough that leads to too long path (which turns to be fairly short - instance names can often exceed 20-30 characters)  and a cryptic "invalid path name" error. Therefor we need to 
> 1) generate the path with shorter random number prefix. 8 characters should be random enough + we can check if the generated path did not exist already and generate another one if that's the case.
> 2) fail validation in case the generated path is too long and propose a solution (shorter names or switching to TCP).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)