{"push_id":1176510585,"size":1,"distinct_size":1,"ref":"refs/heads/R3.0_ifmap","head":"3884d3e6604f75c15361b5b81d5af5e570ef5c55","before":"96347587dd653694c4ef538adeb178de92cb3006","commits":[{"sha":"3884d3e6604f75c15361b5b81d5af5e570ef5c55","author":{"name":"Nischal Sheth","email":"f3695c088f74f048a0592581cf8bf2e2bfb73369@juniper.net"},"message":"Use separate task for IFMap DB\n\nIn scaled setups it was observed that running the graph walker stalled\nbgp/xmpp peer join/leave processing.  This happens because graph walker\nruns in db::DBTable task, which is exclusive with bgp::PeerMembership.\nSince bgp::PeerMembership cannot run when graph walker is running, peer\njoin/leave processing gets delayed as well.\n\nAddress this by running all the IFMap server side code that used to run\nunder db::DBTable in a new db::IFMapTable task. Updated DB infra to use\na user specified task for a given DB. The default task is db::DBTable.\nEliminate use of static members to store task ids and fix both test and\nproduction code to initialize config DB with the new task.\n\nNote that agent IFMap code is unchanged.\n\nChange-Id: Id30c89840690e8f41ebf3b277eaedb150c09d123\nPartial-Bug: 1596089","distinct":true,"url":"https://api.github.com/repos/nischalsheth/contrail-controller/commits/3884d3e6604f75c15361b5b81d5af5e570ef5c55"}]}
{"actor":{"display_login":"nischalsheth"}}