{"push_id":1263854770,"size":1,"distinct_size":1,"ref":"refs/heads/stable/boron","head":"4c740c3abb70b9729851af6ce646feba3e975704","before":"2303f468a95828ce88812afafb919830b39bb7b5","commits":[{"sha":"4c740c3abb70b9729851af6ce646feba3e975704","author":{"name":"Tom Pantelis","email":"23e523b81fb6727eb6a8a64691b8cfc0a6b361e4@brocade.com"},"message":"Updated git submodules\n\nProject: controller stable/boron 80f019059ce0ecebbd25d86c69150dfb6f7f62f3\n\nFix issues when persistence enabled\n\nWhen persistence is dynamically enabled, we start persisting subsequent log\nentries which causes issues on restart due to a gap in journal indexes. We need to\npersist a snapshot with the current state to avoid this.\n\nAlso if persistence is disabled, we still persist ReplicatedLogEntry instances that\nhave a PersistentPayload, of which ServerConfigurationPayload is currently the only one.\nThis also can cause gaps in the persisted journal indexes which cause issues if\npersistence is later enabled. To avoid this, we really shouldn't persist\nReplicatedLogEntry instances at all if data persistence is disabled since we don't\nadd them to the in-memory journal on recovery anyway - we just recover and apply the\nServerConfigurationPayload. Instead we should persist just the\nServerConfigurationPayload.\n\nChange-Id: Ief78d68423b33aac1649220a36d32ff50f493eb7\nSigned-off-by: Tom Pantelis <tpanteli@brocade.com>\n(cherry picked from commit c42a5e91e0dcfc499b33a321ef45c0d310d366cc)","distinct":true,"url":"https://api.github.com/repos/opendaylight/releng-autorelease/commits/4c740c3abb70b9729851af6ce646feba3e975704"}]}
{"actor":{"display_login":"odl-github"}}