Hi Imesh, On Sun, Feb 1, 2015 at 12:06 AM, Imesh Gunaratne <im...@apache.org> wrote:
> Hi Devs, > > I see an issue with topology hierarchy locking behaviour. The problem is > that topology lock objects are created at the time services and clusters > are created. IMO this is error prone, now with the latest codebase I can > see error logs saying "topology lock not found". Ideally locks should > always be created on demand. > Can you explain a bit more about how this behavior is error prone? The logic was that each time a cluster/service/app is added/removed, we should be creating/removing the relevant lock(s). If that is not correctly happening we need to check where that is not happening and fix it. > > Thanks > > > -- > Imesh Gunaratne > > Technical Lead, WSO2 > Committer & PMC Member, Apache Stratos > > -- > Thanks and Regards, > > Isuru H. > +94 716 358 048* <http://wso2.com/>* > > > * <http://wso2.com/>* > > >
