kolla-mesos

ZK lock path should be separated from state nodes

Bug #1557480 reported by Proskurin Kirill
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-mesos
Fix Released
Undecided
Proskurin Kirill

Bug Description

Since ZK lock check is just a sort of current child nodes, if we put "lock node" at the same level as a "state node" we will end with something like:

/node/lock1
/node/lock2
/node/lock3
/node/.done

and .done always will be below, so lock will never be acquired.

Proskurin Kirill (kproskurin)
Changed in kolla-mesos:
assignee: nobody → Proskurin Kirill (kproskurin)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-mesos (master)

Fix proposed to branch: master
Review: https://review.openstack.org/292877

Changed in kolla-mesos:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-mesos (master)

Reviewed: https://review.openstack.org/292877
Committed: https://git.openstack.org/cgit/openstack/kolla-mesos/commit/?id=ce77fdd420dd739b565a8139ae4899d544f23d20
Submitter: Jenkins
Branch: master

commit ce77fdd420dd739b565a8139ae4899d544f23d20
Author: Proskurin Kirill <email address hidden>
Date: Tue Mar 15 11:55:27 2016 +0000

    Create separate ZK lock nodes

    Change-Id: I46e2e407b22ff1c487337489610faa4ba0ad6b10
    Closes-Bug: #1557480

Changed in kolla-mesos:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.