Update git submodules
* Update plugins/replication from branch 'master' to 4590b53e5ef3726ed12b8a3054ae5d4d8363f90d - Merge "Merge branch 'stable-3.1'" - Merge branch 'stable-3.1' * stable-3.1: ReplicationQueue: Check nulls in firePendingEvents Log stack trace when an error occur while deleting event Append LF to the json string of persisted replication event Change default for the replicateOnStartup to false Don't lose ref-updated events on plugin restart Change-Id: Ife23d8746ca1af5060c4d77f8974b707fec4625a - Merge branch 'stable-3.0' into stable-3.1 * stable-3.0: ReplicationQueue: Check nulls in firePendingEvents Log stack trace when an error occur while deleting event Append LF to the json string of persisted replication event Change default for the replicateOnStartup to false Don't lose ref-updated events on plugin restart Change-Id: I505f3769fe89720533e93c197ffe791eda82e848 - Merge branch 'stable-2.16' into stable-3.0 * stable-2.16: ReplicationQueue: Check nulls in firePendingEvents Log stack trace when an error occur while deleting event Append LF to the json string of persisted replication event Change default for the replicateOnStartup to false Don't lose ref-updated events on plugin restart Change-Id: Ic1f42587fce15cfce546c7a3946c0e2d8e75922d - Merge branch 'stable-2.15' into stable-2.16 * stable-2.15: ReplicationQueue: Check nulls in firePendingEvents Log stack trace when an error occur while deleting event Append LF to the json string of persisted replication event Change default for the replicateOnStartup to false Don't lose ref-updated events on plugin restart Change-Id: Icc855dd26ee9f8fb195435d8902404b364242940 - ReplicationQueue: Check nulls in firePendingEvents After a sudden reboot (for unknown reason) Gerrit at startup couldn't load because of NullPointerException. There is a possibility that stored event was null at that point. Extra logging added to handle null events. Change-Id: I72f34d8def6e0246196cd865f33f6e795b21664b - Log stack trace when an error occur while deleting event This will help figuring out root cause of failure to delete event file. Change-Id: I2f9774c3daf19a04f6b04414ba8145c99bb6e0fe (cherry picked from commit b62f006b1350180de0af02c82fb18fb290a2548f) - Append LF to the json string of persisted replication event Change-Id: I83ed3f37071125018bf23f6dcd137ef819ef3559 (cherry picked from commit 5e91925cfd391898e8e33fd149b9e1a115dafee4) - Change default for the replicateOnStartup to false Now that replication events are persistent and non-finished replications rescheduled after plugin restart the replicateOnStartup feature becomes less important. We can change the default value for this option to false. Change-Id: I237d8d8514e01b8786b7db9f39bead4eb475a0a4 (cherry picked from commit 807790f7d4058235a19b2a766e84628168b64ae6) - Don't lose ref-updated events on plugin restart When a ref-updated event is received, persist the event in the directory defined by the replication.eventsDirectory. When the updated ref is replicated deleted the persisted event. If replication queue is non-empty and plugin gets stopped, ref updates will not be replicated and, therefore, the persisted events will not get deleted. When the plugin starts it will schedule replication for all persisted events and delete them. This change provides two benefits: * no ref-updated events are lost on plugin restart * eliminate need for the replicateOnStartup=true setting which schedules replication of all refs for all projects and typically creates a humongous replication queue on every plugin restart. Change-Id: Ieacd084fabe703333241ffda11c8b6c78cced37a (cherry picked from commit bdaea910694dd5a3474dbc051b298aaee9d77950)
This commit is contained in:
parent
84c535cd45
commit
2b3f086f2c
@ -1 +1 @@
|
||||
Subproject commit f475ca45428ce3a1432bf09a24c84c52c9f5bc91
|
||||
Subproject commit 4590b53e5ef3726ed12b8a3054ae5d4d8363f90d
|
Loading…
Reference in New Issue
Block a user