I stared a general thread concerning topics for the next release. One major topic raised was the state of replication and trying to determine if there is consensus for a way forward. I stared this thread so that replication discussions can occur in a single thread for continuity. From the general email thread:
It is hard to know what the state of replication is and maybe we need to mark it as either experimental or deprecated to convey that to users. The replication tests have been unstable and failing with transient errors and have been removed from the regular build process – this reduced the automated build time by over 2 hours. A recent example is accumulo-testing issue #164 (https://github.com/apache/accumulo-testing/issues/164) Without the test running regularly, it is hard to state with any confidence that replication works reliably in a production environment. This should not be interpreted as advocating that we remove replication at this point, but we need a way forward. Maybe someone volunteers to examine the tests and fixes them so that they run reliably and in a reasonable time, or maybe we begin to explore other approaches – for example, maybe some kind of NiFi connector or something else entirely. I really don’t know, but it seems we need to clearly communicate so mething to any users that may be using or considering using replication in the next release the current state and to signal possible future intentions.
