?????? We are very excited to announce the upcoming release of IoTDB-WorkBench 1.1.0
We have removed Chinese in source files, please review. Thanks, --- Haiyang Qin CISDI ?? ---- ??: "dev"
Re: new IT framwork
Thanks, Jialin. Your review does me a lot of favor. Glad to see anyone's feedback. Jialin Qiao 于2021年11月23日周二 下午8:20写道： > Hi, > Yes, the catching-up work is heavy... > Looking forward to merging this PR :) > — > Jialin Qiao > School of Software, Tsinghua University > > 乔嘉林 > 清华大学 软件学院 > > > Junqing Wang 于2021年11月23日周二 下午7:56写道： > > > Hi, > > > > As catching up with the master branch is continuous and massive, all > > refactor work can be split into two temporary phases. > > > > Phase 1, > > > >- This PR should be reviewed. > >- All tests should be annotated with the LocalStandaloneTest category. > >- All these LocalStandaloneTest should be passed. > >- No-brain tutorials should be done. (It will be sent tomorrow at the > >latest.) > > > > The milestone of phase 1 is this PR is merged. > > > > Phase 2, > > > >- All tests should be appropriately annotated with the ClusterTest > >category. > >- All these ClusterTest should be passed. > >- New IT should be followed by No-brain tutorials. > > > > The milestone of phase 2 is all ITs are passed. > > > > I think phase 1 is done this week is appropriate. And phase 2 is not so > > urgent. > > > > The above is already mentioned in the #integration-test channel of slack > in > > Chinese. I will sync the progress in slack. > > > > Jialin Qiao 于2021年11月23日周二 下午7:12写道： > > > > > Hi, > > > > > > This PR refactors the IT framework: > > > https://github.com/apache/iotdb/pull/4371 > > > > > > It will help us test the cluster, please pay attention and review. > > > > > > Thanks, > > > — > > > Jialin Qiao > > > School of Software, Tsinghua University > > > > > > 乔嘉林 > > > 清华大学 软件学院 > > > > > >
Re: new IT framwork
Hi, Yes, the catching-up work is heavy... Looking forward to merging this PR :) — Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院 Junqing Wang 于2021年11月23日周二 下午7:56写道： > Hi, > > As catching up with the master branch is continuous and massive, all > refactor work can be split into two temporary phases. > > Phase 1, > >- This PR should be reviewed. >- All tests should be annotated with the LocalStandaloneTest category. >- All these LocalStandaloneTest should be passed. >- No-brain tutorials should be done. (It will be sent tomorrow at the >latest.) > > The milestone of phase 1 is this PR is merged. > > Phase 2, > >- All tests should be appropriately annotated with the ClusterTest >category. >- All these ClusterTest should be passed. >- New IT should be followed by No-brain tutorials. > > The milestone of phase 2 is all ITs are passed. > > I think phase 1 is done this week is appropriate. And phase 2 is not so > urgent. > > The above is already mentioned in the #integration-test channel of slack in > Chinese. I will sync the progress in slack. > > Jialin Qiao 于2021年11月23日周二 下午7:12写道： > > > Hi, > > > > This PR refactors the IT framework: > > https://github.com/apache/iotdb/pull/4371 > > > > It will help us test the cluster, please pay attention and review. > > > > Thanks, > > — > > Jialin Qiao > > School of Software, Tsinghua University > > > > 乔嘉林 > > 清华大学 软件学院 > > >
Re: share a rust based IoTDB-client
Thank you so much, Julian. On Tue, Nov 23, 2021, 19:52 Julian Feinauer wrote: > Francis, > > let me give you a very warm welcome here! > The work you did so far is simply awesome and I thank you very much! > > Would be cool to have you here in the community and maybe contribute some > of your work to the project itself. > > Greetings! > Julian > > Von: Francis Du > Datum: Dienstag, 23. November 2021 um 12:48 > An: dev@iotdb.apache.org > Betreff: Re: share a rust based IoTDB-client > Hi guys, I'm Francis. The author of iotdb-rs. And welcome to join in and > contribute this.There is also an IotDB cli [1] client built by iotdb-rs, > and everyone is welcome to experience and feedback. > > I also plan to donate them to the community. There are still some work to > be improved. I hope to get you guys guidance. > > [1]. https://github.com/francis-du/iotdb-rs > > On Tue, Nov 23, 2021, 18:52 Jialin Qiao wrote: > > > Good work! > > > > Best, > > Jialin Qiao > > > > Xiangdong Huang 于2021年11月23日周二 下午4:36写道： > > > > > Yes, I have contacted him, and he has already subscribed to the mailing > > > list. > > > > > > --- > > > Xiangdong Huang > > > School of Software, Tsinghua University > > > > > > 黄向东 > > > 清华大学 软件学院 > > > > > > Julian Feinauer 于2021年11月23日周二 > 下午4:20写道： > > > > > > > > Thats pretty cool work. > > > > Did you contact the author @Xiangdong? > > > > I think it would be cool to invite him here to this community if hes > > not > > > already in? > > > > > > > > Best > > > > Julian > > > > > > > > Von: Xiangdong Huang > > > > Datum: Mittwoch, 17. November 2021 um 03:42 > > > > An: dev > > > > Betreff: share a rust based IoTDB-client > > > > Hi, > > > > > > > > to whom may be interested in: > > > > > > > > I find a rust based iotdb-client when I explore Twitter :D > > > > > > > > [1] https://twitter.com/francis_run/status/1457699833981046790?s=20 > > > > [2] https://github.com/francis-du/iotdb-rs > > > > > > > > Best, > > > > --- > > > > Xiangdong Huang > > > > School of Software, Tsinghua University > > > > > > > > 黄向东 > > > > 清华大学 软件学院 > > > > > >
Re: share a rust based IoTDB-client
Sorry for the wrong link, here is iotdb-cli( https://github.com/francis-du/iotdb-cli) On Tue, Nov 23, 2021, 19:47 Francis Du wrote: > Hi guys, I'm Francis. The author of iotdb-rs. And welcome to join in and > contribute this.There is also an IotDB cli [1] client built by iotdb-rs, > and everyone is welcome to experience and feedback. > > I also plan to donate them to the community. There are still some work to > be improved. I hope to get you guys guidance. > > [1]. https://github.com/francis-du/iotdb-rs > > On Tue, Nov 23, 2021, 18:52 Jialin Qiao wrote: > >> Good work! >> >> Best, >> Jialin Qiao >> >> Xiangdong Huang 于2021年11月23日周二 下午4:36写道： >> >> > Yes, I have contacted him, and he has already subscribed to the mailing >> > list. >> > >> > --- >> > Xiangdong Huang >> > School of Software, Tsinghua University >> > >> > 黄向东 >> > 清华大学 软件学院 >> > >> > Julian Feinauer 于2021年11月23日周二 下午4:20写道： >> > > >> > > Thats pretty cool work. >> > > Did you contact the author @Xiangdong? >> > > I think it would be cool to invite him here to this community if hes >> not >> > already in? >> > > >> > > Best >> > > Julian >> > > >> > > Von: Xiangdong Huang >> > > Datum: Mittwoch, 17. November 2021 um 03:42 >> > > An: dev >> > > Betreff: share a rust based IoTDB-client >> > > Hi, >> > > >> > > to whom may be interested in: >> > > >> > > I find a rust based iotdb-client when I explore Twitter :D >> > > >> > > [1] https://twitter.com/francis_run/status/1457699833981046790?s=20 >> > > [2] https://github.com/francis-du/iotdb-rs >> > > >> > > Best, >> > > --- >> > > Xiangdong Huang >> > > School of Software, Tsinghua University >> > > >> > > 黄向东 >> > > 清华大学 软件学院 >> > >> >
Re: new IT framwork
Hi, As catching up with the master branch is continuous and massive, all refactor work can be split into two temporary phases. Phase 1, - This PR should be reviewed. - All tests should be annotated with the LocalStandaloneTest category. - All these LocalStandaloneTest should be passed. - No-brain tutorials should be done. (It will be sent tomorrow at the latest.) The milestone of phase 1 is this PR is merged. Phase 2, - All tests should be appropriately annotated with the ClusterTest category. - All these ClusterTest should be passed. - New IT should be followed by No-brain tutorials. The milestone of phase 2 is all ITs are passed. I think phase 1 is done this week is appropriate. And phase 2 is not so urgent. The above is already mentioned in the #integration-test channel of slack in Chinese. I will sync the progress in slack. Jialin Qiao 于2021年11月23日周二 下午7:12写道： > Hi, > > This PR refactors the IT framework: > https://github.com/apache/iotdb/pull/4371 > > It will help us test the cluster, please pay attention and review. > > Thanks, > — > Jialin Qiao > School of Software, Tsinghua University > > 乔嘉林 > 清华大学 软件学院 >
AW: share a rust based IoTDB-client
Francis, let me give you a very warm welcome here! The work you did so far is simply awesome and I thank you very much! Would be cool to have you here in the community and maybe contribute some of your work to the project itself. Greetings! Julian Von: Francis Du Datum: Dienstag, 23. November 2021 um 12:48 An: dev@iotdb.apache.org Betreff: Re: share a rust based IoTDB-client Hi guys, I'm Francis. The author of iotdb-rs. And welcome to join in and contribute this.There is also an IotDB cli [1] client built by iotdb-rs, and everyone is welcome to experience and feedback. I also plan to donate them to the community. There are still some work to be improved. I hope to get you guys guidance. [1]. https://github.com/francis-du/iotdb-rs On Tue, Nov 23, 2021, 18:52 Jialin Qiao wrote: > Good work! > > Best, > Jialin Qiao > > Xiangdong Huang 于2021年11月23日周二 下午4:36写道： > > > Yes, I have contacted him, and he has already subscribed to the mailing > > list. > > > > --- > > Xiangdong Huang > > School of Software, Tsinghua University > > > > 黄向东 > > 清华大学 软件学院 > > > > Julian Feinauer 于2021年11月23日周二 下午4:20写道： > > > > > > Thats pretty cool work. > > > Did you contact the author @Xiangdong? > > > I think it would be cool to invite him here to this community if hes > not > > already in? > > > > > > Best > > > Julian > > > > > > Von: Xiangdong Huang > > > Datum: Mittwoch, 17. November 2021 um 03:42 > > > An: dev > > > Betreff: share a rust based IoTDB-client > > > Hi, > > > > > > to whom may be interested in: > > > > > > I find a rust based iotdb-client when I explore Twitter :D > > > > > > [1] https://twitter.com/francis_run/status/1457699833981046790?s=20 > > > [2] https://github.com/francis-du/iotdb-rs > > > > > > Best, > > > --- > > > Xiangdong Huang > > > School of Software, Tsinghua University > > > > > > 黄向东 > > > 清华大学 软件学院 > > >
Re: share a rust based IoTDB-client
Hi guys, I'm Francis. The author of iotdb-rs. And welcome to join in and contribute this.There is also an IotDB cli [1] client built by iotdb-rs, and everyone is welcome to experience and feedback. I also plan to donate them to the community. There are still some work to be improved. I hope to get you guys guidance. [1]. https://github.com/francis-du/iotdb-rs On Tue, Nov 23, 2021, 18:52 Jialin Qiao wrote: > Good work! > > Best, > Jialin Qiao > > Xiangdong Huang 于2021年11月23日周二 下午4:36写道： > > > Yes, I have contacted him, and he has already subscribed to the mailing > > list. > > > > --- > > Xiangdong Huang > > School of Software, Tsinghua University > > > > 黄向东 > > 清华大学 软件学院 > > > > Julian Feinauer 于2021年11月23日周二 下午4:20写道： > > > > > > Thats pretty cool work. > > > Did you contact the author @Xiangdong? > > > I think it would be cool to invite him here to this community if hes > not > > already in? > > > > > > Best > > > Julian > > > > > > Von: Xiangdong Huang > > > Datum: Mittwoch, 17. November 2021 um 03:42 > > > An: dev > > > Betreff: share a rust based IoTDB-client > > > Hi, > > > > > > to whom may be interested in: > > > > > > I find a rust based iotdb-client when I explore Twitter :D > > > > > > [1] https://twitter.com/francis_run/status/1457699833981046790?s=20 > > > [2] https://github.com/francis-du/iotdb-rs > > > > > > Best, > > > --- > > > Xiangdong Huang > > > School of Software, Tsinghua University > > > > > > 黄向东 > > > 清华大学 软件学院 > > >
new IT framwork
Hi, This PR refactors the IT framework: https://github.com/apache/iotdb/pull/4371 It will help us test the cluster, please pay attention and review. Thanks, — Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院
Re: share a rust based IoTDB-client
Good work! Best, Jialin Qiao Xiangdong Huang 于2021年11月23日周二 下午4:36写道： > Yes, I have contacted him, and he has already subscribed to the mailing > list. > > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > Julian Feinauer 于2021年11月23日周二 下午4:20写道： > > > > Thats pretty cool work. > > Did you contact the author @Xiangdong? > > I think it would be cool to invite him here to this community if hes not > already in? > > > > Best > > Julian > > > > Von: Xiangdong Huang > > Datum: Mittwoch, 17. November 2021 um 03:42 > > An: dev > > Betreff: share a rust based IoTDB-client > > Hi, > > > > to whom may be interested in: > > > > I find a rust based iotdb-client when I explore Twitter :D > > > > [1] https://twitter.com/francis_run/status/1457699833981046790?s=20 > > [2] https://github.com/francis-du/iotdb-rs > > > > Best, > > --- > > Xiangdong Huang > > School of Software, Tsinghua University > > > > 黄向东 > > 清华大学 软件学院 >
Re: refactor cluster discussion
Hi, yes you raise up another existing topic: whether and how to decouple and smoothly change to another RPC framework? Besides, I wonder how do you find these Chinese materials... Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer 于2021年11月23日周二 下午4:53写道： > > Hey Xiangdong, > > that makes totally sense and its good that we „can“ always do CP but switch > more towards AP if wanted. > Regarding RPC I just found this interesting benchmark (you may be better able > to read everything…): > > https://github.com/eisig/rpc-benchmark > https://www.jianshu.com/p/cdd94d0853c3 > > Best > Julian > > Von: Xiangdong Huang > Datum: Dienstag, 23. November 2021 um 09:46 > An: dev > Betreff: Re: refactor cluster discussion > Hi Julian, > > Well, in my view, it is AP by default, and can switch to CP (but for > some operations, it only supports CP). > 1. As we used cache for reducing RPC, it is AP. But if we mandatorily > requires check whether the cache is the latest, then it is CP but has > a larger latency. > 2. For some un-frequent operations (e.g., delete timeseries, delete > storage group), we use CP, and requires all nodes to execute the > operations successfully. > > For RPC times, yes the less, the better. If some RPC requests can not > be avoid, then the other way is reduce the message size of the request > and response. > > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > Julian Feinauer 于2021年11月23日周二 下午4:14写道： > > > > > Hi Community, > > > > I really like the discussions here and although I do not find enough time > > (and language skills in Chinese) to participate in the meetups I think we > > are on a very good way. > > > > While reading through the docs provided I just quickly had two thoughts > > that I wanted to share here > > > > > > * Regarding the CAP Theorem, where do we (want to) place ourselves? The > > current cluster module is, from my understanding CP but many MPP Databases > > rather go for AP (I think). I am not sure whats the best approach for > > timeseries and perhaps theres even the chance to switch between both modes > > in certain scenarios (people usually call it something like almost > > certainly consistent or something.. but math is clear, you are either CP or > > AP nothing in between) > > * If we do have a lot of communication over sockets we should perhaps > > re-evaluate our RPC mechanism. I know that it’s a razors edge between > > “preliminary optimization” and doing “the right”. But I think it would be > > good to reconsider or check a bit on how much time we loose on RPC because > > that’s a latency we always have to pay and probably multiple times during a > > single call depending on the situation > > > > If that’s already well discussed and written in the documents than please > > excuse me missing it. > > > > Best! > > Julian > > > > Von: Xiangdong Huang > > Datum: Montag, 22. November 2021 um 03:04 > > An: dev > > Betreff: refactor cluster discussion > > Hi all, > > > > In the brainstorming last week [1], we tried to introduce a more clear > > code decoupling design, which embraced MPP architecture, and shrinked > > the raft protocol only into a small scope in the codebase (then it is > > easy to replace the implementation of raft, and even replace raft to > > other replica mechanism). > > > > Some detailed discussion is on [2], and welcome to supply the doc. > > > > [1] > > https://cwiki.apache.org/confluence/display/IOTDB/%5BChinese%5Diotdb+cluster+discussion+2021.11 > > > > [2] > > https://cwiki.apache.org/confluence/display/IOTDB/refactor-2021-MPP-decoupling > > > > Best, > > --- > > Xiangdong Huang > > School of Software, Tsinghua University > > > > 黄向东 > > 清华大学 软件学院
AW: refactor cluster discussion
Hey Xiangdong, that makes totally sense and its good that we „can“ always do CP but switch more towards AP if wanted. Regarding RPC I just found this interesting benchmark (you may be better able to read everything…): https://github.com/eisig/rpc-benchmark https://www.jianshu.com/p/cdd94d0853c3 Best Julian Von: Xiangdong Huang Datum: Dienstag, 23. November 2021 um 09:46 An: dev Betreff: Re: refactor cluster discussion Hi Julian, Well, in my view, it is AP by default, and can switch to CP (but for some operations, it only supports CP). 1. As we used cache for reducing RPC, it is AP. But if we mandatorily requires check whether the cache is the latest, then it is CP but has a larger latency. 2. For some un-frequent operations (e.g., delete timeseries, delete storage group), we use CP, and requires all nodes to execute the operations successfully. For RPC times, yes the less, the better. If some RPC requests can not be avoid, then the other way is reduce the message size of the request and response. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer 于2021年11月23日周二 下午4:14写道： > > Hi Community, > > I really like the discussions here and although I do not find enough time > (and language skills in Chinese) to participate in the meetups I think we are > on a very good way. > > While reading through the docs provided I just quickly had two thoughts that > I wanted to share here > > > * Regarding the CAP Theorem, where do we (want to) place ourselves? The > current cluster module is, from my understanding CP but many MPP Databases > rather go for AP (I think). I am not sure whats the best approach for > timeseries and perhaps theres even the chance to switch between both modes in > certain scenarios (people usually call it something like almost certainly > consistent or something.. but math is clear, you are either CP or AP nothing > in between) > * If we do have a lot of communication over sockets we should perhaps > re-evaluate our RPC mechanism. I know that it’s a razors edge between > “preliminary optimization” and doing “the right”. But I think it would be > good to reconsider or check a bit on how much time we loose on RPC because > that’s a latency we always have to pay and probably multiple times during a > single call depending on the situation > > If that’s already well discussed and written in the documents than please > excuse me missing it. > > Best! > Julian > > Von: Xiangdong Huang > Datum: Montag, 22. November 2021 um 03:04 > An: dev > Betreff: refactor cluster discussion > Hi all, > > In the brainstorming last week [1], we tried to introduce a more clear > code decoupling design, which embraced MPP architecture, and shrinked > the raft protocol only into a small scope in the codebase (then it is > easy to replace the implementation of raft, and even replace raft to > other replica mechanism). > > Some detailed discussion is on [2], and welcome to supply the doc. > > [1] > https://cwiki.apache.org/confluence/display/IOTDB/%5BChinese%5Diotdb+cluster+discussion+2021.11 > > [2] > https://cwiki.apache.org/confluence/display/IOTDB/refactor-2021-MPP-decoupling > > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院
Re: refactor cluster discussion
Hi Julian, Well, in my view, it is AP by default, and can switch to CP (but for some operations, it only supports CP). 1. As we used cache for reducing RPC, it is AP. But if we mandatorily requires check whether the cache is the latest, then it is CP but has a larger latency. 2. For some un-frequent operations (e.g., delete timeseries, delete storage group), we use CP, and requires all nodes to execute the operations successfully. For RPC times, yes the less, the better. If some RPC requests can not be avoid, then the other way is reduce the message size of the request and response. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer 于2021年11月23日周二 下午4:14写道： > > Hi Community, > > I really like the discussions here and although I do not find enough time > (and language skills in Chinese) to participate in the meetups I think we are > on a very good way. > > While reading through the docs provided I just quickly had two thoughts that > I wanted to share here > > > * Regarding the CAP Theorem, where do we (want to) place ourselves? The > current cluster module is, from my understanding CP but many MPP Databases > rather go for AP (I think). I am not sure whats the best approach for > timeseries and perhaps theres even the chance to switch between both modes in > certain scenarios (people usually call it something like almost certainly > consistent or something.. but math is clear, you are either CP or AP nothing > in between) > * If we do have a lot of communication over sockets we should perhaps > re-evaluate our RPC mechanism. I know that it’s a razors edge between > “preliminary optimization” and doing “the right”. But I think it would be > good to reconsider or check a bit on how much time we loose on RPC because > that’s a latency we always have to pay and probably multiple times during a > single call depending on the situation > > If that’s already well discussed and written in the documents than please > excuse me missing it. > > Best! > Julian > > Von: Xiangdong Huang > Datum: Montag, 22. November 2021 um 03:04 > An: dev > Betreff: refactor cluster discussion > Hi all, > > In the brainstorming last week [1], we tried to introduce a more clear > code decoupling design, which embraced MPP architecture, and shrinked > the raft protocol only into a small scope in the codebase (then it is > easy to replace the implementation of raft, and even replace raft to > other replica mechanism). > > Some detailed discussion is on [2], and welcome to supply the doc. > > [1] > https://cwiki.apache.org/confluence/display/IOTDB/%5BChinese%5Diotdb+cluster+discussion+2021.11 > > [2] > https://cwiki.apache.org/confluence/display/IOTDB/refactor-2021-MPP-decoupling > > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院
Re: share a rust based IoTDB-client
Yes, I have contacted him, and he has already subscribed to the mailing list. --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer 于2021年11月23日周二 下午4:20写道： > > Thats pretty cool work. > Did you contact the author @Xiangdong? > I think it would be cool to invite him here to this community if hes not > already in? > > Best > Julian > > Von: Xiangdong Huang > Datum: Mittwoch, 17. November 2021 um 03:42 > An: dev > Betreff: share a rust based IoTDB-client > Hi, > > to whom may be interested in: > > I find a rust based iotdb-client when I explore Twitter :D > > [1] https://twitter.com/francis_run/status/1457699833981046790?s=20 > [2] https://github.com/francis-du/iotdb-rs > > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院
AW: share a rust based IoTDB-client
Thats pretty cool work. Did you contact the author @Xiangdong? I think it would be cool to invite him here to this community if hes not already in? Best Julian Von: Xiangdong Huang Datum: Mittwoch, 17. November 2021 um 03:42 An: dev Betreff: share a rust based IoTDB-client Hi, to whom may be interested in: I find a rust based iotdb-client when I explore Twitter :D [1] https://twitter.com/francis_run/status/1457699833981046790?s=20 [2] https://github.com/francis-du/iotdb-rs Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
AW: refactor cluster discussion
Hi Community, I really like the discussions here and although I do not find enough time (and language skills in Chinese) to participate in the meetups I think we are on a very good way. While reading through the docs provided I just quickly had two thoughts that I wanted to share here * Regarding the CAP Theorem, where do we (want to) place ourselves? The current cluster module is, from my understanding CP but many MPP Databases rather go for AP (I think). I am not sure whats the best approach for timeseries and perhaps theres even the chance to switch between both modes in certain scenarios (people usually call it something like almost certainly consistent or something.. but math is clear, you are either CP or AP nothing in between) * If we do have a lot of communication over sockets we should perhaps re-evaluate our RPC mechanism. I know that it’s a razors edge between “preliminary optimization” and doing “the right”. But I think it would be good to reconsider or check a bit on how much time we loose on RPC because that’s a latency we always have to pay and probably multiple times during a single call depending on the situation If that’s already well discussed and written in the documents than please excuse me missing it. Best! Julian Von: Xiangdong Huang Datum: Montag, 22. November 2021 um 03:04 An: dev Betreff: refactor cluster discussion Hi all, In the brainstorming last week [1], we tried to introduce a more clear code decoupling design, which embraced MPP architecture, and shrinked the raft protocol only into a small scope in the codebase (then it is easy to replace the implementation of raft, and even replace raft to other replica mechanism). Some detailed discussion is on [2], and welcome to supply the doc. [1] https://cwiki.apache.org/confluence/display/IOTDB/%5BChinese%5Diotdb+cluster+discussion+2021.11 [2] https://cwiki.apache.org/confluence/display/IOTDB/refactor-2021-MPP-decoupling Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
