[jira] [Work logged] (GOBBLIN-1648) Avoid Gobblin Cluster Manager downtime during DB failover

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GOBBLIN-1648?focusedWorklogId=771521&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-771521 ]

ASF GitHub Bot logged work on GOBBLIN-1648:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 17/May/22 18:53
            Start Date: 17/May/22 18:53
    Worklog Time Spent: 10m 
      Work Description: phet opened a new pull request, #3509:
URL: https://github.com/apache/gobblin/pull/3509

   Dear Gobblin maintainers,
   
   Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
   
   ### JIRA
   - [ ] My PR addresses the following [Gobblin JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
       - https://issues.apache.org/jira/browse/GOBBLIN-1648
   
   ### Description
   - [ ] Here are some details about my PR, including screenshots (if applicable):
   
   To avoid Gobblin Cluster Manager downtime, observed during DB failover (when the currently connected instance which was active becomes a follower), detect once the connection on hand becomes read-only.  Enforce verification when this happens, so we know to create new, replacement connections (to a read-write host).
   
   There was one code path where this wasn't happening.  in addition, add logging to trace when the validation query was successfully initialized, in case the code we believe to be executing is not in fact.
   
   ### Tests
   - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
   
   
   ### Commits
   - [ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
       1. Subject is separated from body by a blank line
       2. Subject is limited to 50 characters
       3. Subject does not end with a period
       4. Subject uses the imperative mood ("add", not "adding")
       5. Body wraps at 72 characters
       6. Body explains "what" and "why", not "how"
   
   




Issue Time Tracking
-------------------

            Worklog Id:     (was: 771521)
    Remaining Estimate: 0h
            Time Spent: 10m

> Avoid Gobblin Cluster Manager downtime during DB failover
> ---------------------------------------------------------
>
>                 Key: GOBBLIN-1648
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1648
>             Project: Apache Gobblin
>          Issue Type: Task
>          Components: gobblin-cluster
>            Reporter: Kip Kohn
>            Assignee: Hung Tran
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When the DB fails over (so the currently connected instance which was active becomes a follower), the connection on hand becomes read-only.  Enforce verification when this happens, so we know to create new, replacement connections (to a read-write host).



--
This message was sent by Atlassian Jira
(v8.20.7#820007)