Update on order of plugin loading and online reindexing
The fix for this issue is submitted and will be included in the 2.16.3
minor release.
Change-Id: I7f69e5ff04f7f20c7cfc388c62fe746c542fb6d0
diff --git a/pages/site/releases/2.16.md b/pages/site/releases/2.16.md
index 42e9f6f..4d95478 100644
--- a/pages/site/releases/2.16.md
+++ b/pages/site/releases/2.16.md
@@ -43,26 +43,8 @@
is in the replication plugin, which needs to use the group cache when
`authGroup` is used in a destination configuration.
-A fix is in progress and will be provided in a later release.
-See [issue 10082](https://bugs.chromium.org/p/gerrit/issues/detail?id=10082)
-and the associated changes for details.
-
-#### Workaround for the replication plugin
-
-Due to the issue mentioned above, the replication plugin will fail to load
-when there is a destination configuration using `authGroup` and the plugin
-is loaded during server startup. Until a fix is available, please use one of
-the following workarounds:
-
-* Remove the `replication.jar` file from the site's `plugins` folder, start
-the server, and then put `replication.jar` back.
-
-* In a running site that has already failed to load the replication plugin,
-change the `replication.jar` file's timestamp, e.g. with the `touch`
-command. The plugin will then be automatically reloaded after some time. To
-force an immediate reload, issue a `plugin reload replication` command over
-ssh. Note that this requires the `plugins.allowRemoteAdmin` configuration to
-be enabled.
+A fix [issue 10082](https://bugs.chromium.org/p/gerrit/issues/detail?id=10082)
+is available since 2.16.3 release.
### Migration to NoteDb
