[BUILD-FAILURE]: Job 'IoTDB/IoTDB-Pipe/master [master] [603]'

[Apache Jenkins Server]

BUILD-FAILURE: Job 'IoTDB/IoTDB-Pipe/master [master] [603]':

Check console output at "https://ci-builds.apache.org/job/IoTDB/job/IoTDB-Pipe/job/master/603/";>IoTDB/IoTDB-Pipe/master
 [master] [603]"

RE: new committer: Minghui Liu

[jianyun cheng]

Congratulations, Minghui!

--
Thanks
Jianyun Cheng

From: HW-Chao Wang
Sent: Wednesday, May 25, 2022 8:08 AM
To: dev
Subject: Re: new committer: Minghui Liu

Congratulations to minghui


---Original---
From: "Jialin Qiao"

RE: new committer: Xuxin Liu

[jianyun cheng]

Congratulations, Xuxin!

--
Thanks
Jianyun Cheng

From: HW-Chao Wang
Sent: Tuesday, May 24, 2022 10:04 PM
To: dev
Subject: Re: new committer: Xuxin Liu

Congratulations to xuxin…




---Original---
From: "Jialin Qiao"

Refactor integration test for the new MPP cluster

[Junqing Wang]

Hi, all,

This new version of the integration test has some excellent features:

- Adapt for the new MPP cluster.
- Parallel to do cluster integration test.
- Add the whitelist of import statements to forbid the invalid use of env
statements.
- Add the log record for every node in the cluster integration test, and
these log files can be
  downloaded on the GitHub action page.

The PR link is:
https://github.com/apache/iotdb/pull/5901

The user guide link is:
https://github.com/irvine0109/iotdb/blob/IOTDB-3178/integration-test/README.md

Thanks for any comments.
And there is some discussion in slack channel #integraion-test in Chinese.

Best,
Junqing WANG

Re: replacing log4j

[Jialin Qiao]

Hi,

+1 for the replacing. The PR is merged.

Maybe the security issue is so critical that the author wants to get rid of
it by renaming it...

Thanks,
—
Jialin Qiao
Apache IoTDB PMC


HW-Chao Wang <576749...@qq.com.invalid> 于2022年5月24日周二 21:54写道：

> yes, i will raise jira and alter it.
>
>
>
> ---Original---
> From: "Xiangdong Huang" Date: Tue, May 24, 2022 21:47 PM
> To: "dev" Subject: Re: replacing log4j
>
>
> I see, [1] introduces the reason that reload4j is born.
> As it is just a modification in pom file and the project is forked from
> log4j 1.2.17, I think it is fine.
>
> BTW, I feel very very confusing why log4j community ends the life of log4j
> 1
> (and in the same time the initial author of log4j 1 forks an independent
> project...)
>
> [1] https://reload4j.qos.ch/
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> HW-Chao Wang <576749...@qq.com.invalid> 于2022年5月24日周二 17:24写道：
>
> > Because of the large amount of changes, the configuration file and
> import
> > of each class have to change.
> >
> >
> >
> >
> > ---Original---
> > From: "Xiangdong Huang" > Date: Tue, May 24, 2022 17:17 PM
> > To: "dev" > Subject: Re: replacing log4j
> >
> >
> > Hi, I wonder why not log4j2? any comparison in other communities?
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
> >
> >
> > HW-Chao Wang <576749...@qq.com.invalid> 于2022年5月24日周二 16:23写道：
> >
> > > hi all ，
> > > We need to consider replacing log4j1, because log4j1 is EOM
> and has
> > some
> > > CVE vulnerabilities. Reload 4J is used to replace it. Other
> open
> > source
> > > communities have been replaced. Refer to hbase-26691.
> > > Thanks&nbsp;

Consensus layer in new cluster architecture

[Xinyu Tan]

Hi everyone,

In our new cluster architecture, the consensus layer is a general
interface, which is mainly responsible for providing abstractions of read,
write and shard management for the upper side, and applying the logs to the
state machine in sequence for the below side. Similar to the idea in the
OSDI 2020 best paper Delos[1],  our very simple idea is to enable the
consensus layer to support multiple consensus algorithms, and to shield the
details of the consensus for the upper and lower layers through interface.

Currently our consensus layer supports two common implementations
StandAloneConsensus and RatisConsensus. The former is a very simple
single-copy abstraction, and the latter uses Apache Ratis to achieve
Replicate state machine among multiple nodes. However, Ratis guarantees
strong consistency over multiple replicas, which undoubtedly affects
performance, and we don't necessarily need such consistency in some
time-series user scenarios. Therefore, we have recently implemented a
consensus algorithm for multi-master replication that provides weak
consistency but higher performance. Welcome to review this pr [2].

BTW, Although this multi-master consensus algorithm has good theoretical
performance, it provides very weak consistency. We may enhance the
consistency level it can provide by adding certain constraints later, just
like the CAD algorithm in Fast 2020 Best Paper [3], We welcome friends in
the community who are interested in this area to contribute your ideas.

In addition, since the consensus layer is a general interface, we also
welcome friends in the community who are interested in implementing
consensus algorithms to implement more consensus algorithms for the
consensus layer, such as EPaxos, etc. This is undoubtedly a very meaningful
independent work.

[1] https://www.usenix.org/conference/osdi20/presentation/balakrishnan
[2] https://github.com/apache/iotdb/pull/5939
[3] https://www.usenix.org/system/files/fast20-ganesan.pdf

Best
-
Xinyu Tan

[BUILD-FAILURE]: Job 'IoTDB/IoTDB-Pipe/master [master] [604]'

[Apache Jenkins Server]

BUILD-FAILURE: Job 'IoTDB/IoTDB-Pipe/master [master] [604]':

Check console output at "https://ci-builds.apache.org/job/IoTDB/job/IoTDB-Pipe/job/master/604/";>IoTDB/IoTDB-Pipe/master
 [master] [604]"

Re: Consensus layer in new cluster architecture

[HW-Chao Wang]

Thanks to Xinyu. I just read this design and code, which can improve the 
performance of writing. I made a few suggestions that we need to consider. The 
order of data is a problem. In multleader mode, the operations to ensure data 
order need to be explained in the user guide. 1. The data of the same sequence 
of the client is written to a node. 2. The client remains unchanged, the server 
optimizes session segmentation, and the same sequence is transferred to a node 
to control writing.

best
---
HW-Chao Wang

---Original---
From: "Xinyu Tan"https://www.usenix.org/conference/osdi20/presentation/balakrishnan
[2] https://github.com/apache/iotdb/pull/5939
[3] https://www.usenix.org/system/files/fast20-ganesan.pdf

Best
-
Xinyu Tan

self-introduction by Xin Hua

[Xin Hua]

Hi,

I'm Xin Hua, from Yonyou.

jira id: huaxin

Confluence id: huaxin


Best.

Account authority

[高希鸣]

Hello, I'm Gao Ximing, from Beijing, China. My JIRA email is 
gaoxim...@vip.163.com ; My confluence email is gaoxim...@vip.163.com ； Please 
open relevant permissions for me.

Re: Refactor integration test for the new MPP cluster

[Jialin Qiao]

Hi,

Really a great feature! The new cluster version very needs the IT :D

Thanks,
—
Jialin Qiao
Apache IoTDB PMC


Junqing Wang  于2022年5月25日周三 21:25写道：

> Hi, all,
>
> This new version of the integration test has some excellent features:
>
> - Adapt for the new MPP cluster.
> - Parallel to do cluster integration test.
> - Add the whitelist of import statements to forbid the invalid use of env
> statements.
> - Add the log record for every node in the cluster integration test, and
> these log files can be
>   downloaded on the GitHub action page.
>
> The PR link is:
> https://github.com/apache/iotdb/pull/5901
>
> The user guide link is:
>
> https://github.com/irvine0109/iotdb/blob/IOTDB-3178/integration-test/README.md
>
> Thanks for any comments.
> And there is some discussion in slack channel #integraion-test in Chinese.
>
> Best,
> Junqing WANG
>

Re: Account authority

[Jialin Qiao]

Hi,

Welcome! The confluence permission is allocated to you.
However, I can't find the your jira account according to the email, please
give me the jira account id.

Thanks,
—
Jialin Qiao
Apache IoTDB PMC


高希鸣  于2022年5月26日周四 11:50写道：

> Hello, I'm Gao Ximing, from Beijing, China. My JIRA email is
> gaoxim...@vip.163.com ; My confluence email is gaoxim...@vip.163.com ；
> Please open relevant permissions for me.
>

Re: self-introduction by Xin Hua

[Jialin Qiao]

Hi,

Welcome! all accounts added.

Thanks,
—
Jialin Qiao
Apache IoTDB PMC


Xin Hua  于2022年5月26日周四 11:47写道：

> Hi,
>
> I'm Xin Hua, from Yonyou.
>
> jira id: huaxin
>
> Confluence id: huaxin
>
>
> Best.
>

Re: Account authority

[高希鸣]

jira：高希鸣
confluence：gaoximing

> 2022年5月26日 11:57，Jialin Qiao  写道：
> 
> Hi,
> 
> Welcome! The confluence permission is allocated to you.
> However, I can't find the your jira account according to the email, please
> give me the jira account id.
> 
> Thanks,
> —
> Jialin Qiao
> Apache IoTDB PMC
> 
> 
> 高希鸣  于2022年5月26日周四 11:50写道：
> 
>> Hello, I'm Gao Ximing, from Beijing, China. My JIRA email is
>> gaoxim...@vip.163.com ; My confluence email is gaoxim...@vip.163.com ；
>> Please open relevant permissions for me.
>> 

Re: Account authority

[Jialin Qiao]

Hi, Jira added
—
Jialin Qiao
Apache IoTDB PMC


高希鸣  于2022年5月26日周四 12:17写道：

> jira：高希鸣
> confluence：gaoximing
>
> > 2022年5月26日 11:57，Jialin Qiao  写道：
> >
> > Hi,
> >
> > Welcome! The confluence permission is allocated to you.
> > However, I can't find the your jira account according to the email,
> please
> > give me the jira account id.
> >
> > Thanks,
> > —
> > Jialin Qiao
> > Apache IoTDB PMC
> >
> >
> > 高希鸣  于2022年5月26日周四 11:50写道：
> >
> >> Hello, I'm Gao Ximing, from Beijing, China. My JIRA email is
> >> gaoxim...@vip.163.com ; My confluence email is gaoxim...@vip.163.com ；
> >> Please open relevant permissions for me.
> >>
>
>