Hi Apache Kudu dev community, We have made a lot of progress in recent months and years building out Kudu's replication features and making stabilizing improvements. Capturing, in one place, where we're headed would give us all the benefits of more design validation and more opportunities for involvement and collaboration.
I'd like to offer a draft roadmap for Kudu's distributed replication subsystem (based on Raft consensus). The doc tries to comprehensively capture important improvements we should design and implement in the future, both near term and long term. Please note that attaching features to future releases and / or dates is *not* a goal of this document. Future merge dates will depend on the individuals contributing the designs / code and the individuals reviewing / committing it. Discussion about whether some improvement is useful at all or whether a particular benefit could be better achieved using an alternative approach is welcome and strongly encouraged. However, relative prioritization of legitimate features and improvements may be somewhat subjective so I don't expect to reach consensus on that (no pun intended) -- therefore the items are not necessarily placed in a priority order. Please feel to leave comments and feedback on the document, which can be found here: https://docs.google.com/document/d/1EFSCfv1JtbAQGwIEpO59KxB2Eg96r imIHtfOb0Z8XyQ If you want to make significant additions, please feel free to send me email and I will incorporate them or give you edit/suggest rights. Thanks in advance for your comments and suggestions. Regards, Mike
