+1 for SimpleConsensus OneCopy may cause confuse, Users may treat one replica as OneCopy.
Or treat OneCopy as two replicas ( one primary + one copy) Thanks, Jialin Qiao On 2022/11/02 04:14:52 Haonan Hou wrote: > +1 for SimpleConsensus. > > Cassandra has a similar `SimpleStrategy`. > See > https://cassandra.apache.org/doc/4.1/cassandra/architecture/dynamo.html#simple-strategy > > Best, > Haonan Hou > > > On Oct 31, 2022, at 9:32 PM, Jialin Qiao <[email protected]> wrote: > > > > +1 for OneReplicaConsensus > > ————————————————— > > Jialin Qiao > > Apache IoTDB PMC > > > > Yuan Tian <[email protected]> 于2022年10月31日周一 20:08写道： > >> > >> Hi all, > >> > >> After discussing, we think OneCopyConsensus may be better. So I rename > >> it to OneCopyConsensus in this pr > >> https://github.com/apache/iotdb/pull/7832/files > >> > >> Best, > >> ---------------- > >> Yuan Tian > >> > >> On Mon, Oct 31, 2022 at 12:39 PM Yuan Tian <[email protected]> wrote: > >>> > >>> Hi, all > >>> > >>> Now, we name the consensus which is optmized for only single > >>> replica(actualy this consensus can only support one replica) as > >>> StandAloneConsensus. However, `StandAlone` is ambiguous, it was used > >>> for IoTDB StandAlone version(v.s. distributed version). > >>> > >>> So, we decided to change its name, here are some candidates: > >>> > >>> 1. OneCopyConsensus > >>> 2. NoCopyConsensus > >>> 3. SimpleConsensus > >>> 4. ZereCostConsensus > >>> > >>> Do you guys have any suggestions? Or Which one of the above names you > >>> voted for? > >>> > >>> > >>> Best, > >>> -------------- > >>> Yuan Tian > >
