Another more recent issue related to force push and Hadoop: https://issues.apache.org/jira/browse/INFRA-13902
I think ZooKeeper git project should be configured to disable force push by default for all branches. I believe the force push was not currently configured as disabled otherwise I would not succeed on force pushing which leads to an observable inconsistent state for branch-3.4. I'll follow up with INFRA once we restore the linearizability of branch-3.4. On Tue, Apr 18, 2017 at 12:40 PM, Patrick Hunt <[email protected]> wrote: > fwiw some background on what other teams have done: > https://issues.apache.org/jira/browse/INFRA-11236 > > Patrick > > On Tue, Apr 18, 2017 at 10:23 AM, Michael Han <[email protected]> wrote: > > > I did a forced push on branch-3.4 this morning to remove a bad commit > that > > breaks the build of branch-3.4. I wasn't aware that forced push should be > > avoided until Pat Hunt reminds me. > > After force push I noticed some inconsistency state of top ref for > > branch-3.4, and I am following up with INFRA on this [1]. > > > > Apologize for any inconvenience caused. Please let me know if you observe > > other problems caused by the change of the state for branch-3.4. > > > > [1] https://issues.apache.org/jira/browse/INFRA-13916 > > -- > > Cheers > > Michael. > > > -- Cheers Michael.
