Good news! How about '0.14.0-preview' ? As in general development we always use
*-alpha as an internal test version with all main features present. As the
description of the version, it mainly contains the new cluster.
在 2022/6/22 16:44，“Jialin Qiao”<qiaojia...@apache.org> 写入:
Hi all,
It has been 4~5 months since we started the new cluster version. Thanks for
the contribution of all contributors!
It's time to start the topic of releasing :)
The summary status of the master branch is as follows:
(1) The new cluster version has many advantages compared to the old
one(0.12~0.13).
* MPP Query Engine, we use volcano module with operators for better
extendibility in data processing.
* Configurable consensus protocol (Standalone, Raft, Multi-Leader) for
Partition, Schema and Data.
* Controlable partition table, so that we could control which node to
manage data.
* No whole cluster consensus group.
* More flexible and lightweight scale-out, we could add a node in a few
seconds without moving data.
* Extensible load balance strategy.
* Built-in metric framework to monitor the status of the cluster.
(2) We have implement the basic function (read/write/schema/udf) of the new
Cluster/standalone version.
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapache-iotdb.feishu.cn%2Fmindnotes%2FbmncnEr7XPzmPvrZgYbcSEvMTIf%23mindmap&data=05%7C01%7C%7C14142baedc434ef11f1d08da542b722d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637914842832750235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=HpaVs90uuGUsA4MhtHGyIltGwexNWcITWmcINs00rN8%3D&reserved=0
There are still some functions that need to be implemented in new
Cluster/standalone.
* Trigger
* Schema Template
* Continuous Query
* Select into
* Sync framework
(3) The performance optimization of the new Cluster is still going.
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapache-iotdb.feishu.cn%2Fdocx%2Fdoxcn6xEgTopkvsLsG3TXjwlx0c&data=05%7C01%7C%7C14142baedc434ef11f1d08da542b722d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637914842832750235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=YDO5juXfrC0LZDmYJovmgAHw6LxZJANbLFcyobt4FOM%3D&reserved=0
* Write performance of one replication with standalone/multiLeader in new
cluster. [ok].
* Write performance of one replication with Ratis. [underway]
* Write performance of three replication with Ratis/MultiLeader. [underway]
* Query performance of one replication with standalone/ratis/multileader.
[underway]
* Query performance of three replication with Ratis/MultiLeader. [underway]
I suppose we could get a not-bad number by this weekend for all above
scenaios.
(4) More test needs to be done to improve the stability of the new
cluster/standalone, and the ITs are being added.
As this version does not contains the whole functions of 0.13, and the
system performance and stability need to be improved for some time before
produnction, I suggest retaining the 0.14.0 version number.
So, how about using 【0.14.0-alpha】, and we only release the binary
distribution of new cluster, without new/old standalone version.
Then, for the formal 0.14.0, we could release the new Cluster/Standalone
version and discard the old Standalone version.
Thanks,
—————————————————
Jialin Qiao
Apache IoTDB PMC
