You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@iotdb.apache.org by yo...@apache.org on 2025/10/17 11:37:40 UTC

(iotdb) branch Fix-datanode-start-process updated (010fab552f8 -> 682ae9d753e)

This is an automated email from the ASF dual-hosted git repository.

yongzao pushed a change to branch Fix-datanode-start-process
in repository https://gitbox.apache.org/repos/asf/iotdb.git


 discard 010fab552f8 Update DataNode.java
     add fe96a5573dd Perfect implicit time process in first, last, first_by, last_by of TableModel
     add 2ae06e811bd Optimize memtable scan
     new 682ae9d753e Update DataNode.java

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (010fab552f8)
            \
             N -- N -- N   refs/heads/Fix-datanode-start-process (682ae9d753e)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 .../db/it/IoTDBMultiTAGsWithAttributesTableIT.java |  39 +++-
 .../fragment/FragmentInstanceContext.java          |  20 ++
 .../execution/operator/source/SeriesScanUtil.java  |  65 +++++-
 .../plan/relational/sql/parser/AstBuilder.java     |  42 ++--
 .../read/reader/common/NoDataPointReader.java}     |  38 ++--
 .../db/utils/datastructure/AlignedTVList.java      | 100 +++++----
 .../iotdb/db/utils/datastructure/LazyBitMap.java   |  93 +++++++++
 .../db/utils/datastructure/MemPointIterator.java   |   3 +
 .../MergeSortMultiAlignedTVListIterator.java       |  22 ++
 .../MergeSortMultiTVListIterator.java              |  22 ++
 .../OrderedMultiAlignedTVListIterator.java         |  24 +++
 .../datastructure/OrderedMultiTVListIterator.java  |  24 +++
 .../iotdb/db/utils/datastructure/TVList.java       | 229 ++++++++++++++++++++-
 .../memtable/AlignedTVListIteratorTest.java        | 110 ++++++++++
 .../memtable/NonAlignedTVListIteratorTest.java     |  87 ++++++++
 15 files changed, 832 insertions(+), 86 deletions(-)
 copy iotdb-core/datanode/src/main/java/org/apache/iotdb/db/{queryengine/plan/relational/sql/ast/ShowAIDevices.java => storageengine/dataregion/read/reader/common/NoDataPointReader.java} (56%)
 create mode 100644 iotdb-core/datanode/src/main/java/org/apache/iotdb/db/utils/datastructure/LazyBitMap.java


(iotdb) 01/01: Update DataNode.java

Posted by yo...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

yongzao pushed a commit to branch Fix-datanode-start-process
in repository https://gitbox.apache.org/repos/asf/iotdb.git

commit 682ae9d753e9ccf93415c60021e9bc13f5df64c1
Author: Yongzao <53...@qq.com>
AuthorDate: Fri Oct 17 19:37:08 2025 +0800

    Update DataNode.java
---
 .../datanode/src/main/java/org/apache/iotdb/db/service/DataNode.java  | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/iotdb-core/datanode/src/main/java/org/apache/iotdb/db/service/DataNode.java b/iotdb-core/datanode/src/main/java/org/apache/iotdb/db/service/DataNode.java
index cebf7dab9f3..f66eff373ab 100644
--- a/iotdb-core/datanode/src/main/java/org/apache/iotdb/db/service/DataNode.java
+++ b/iotdb-core/datanode/src/main/java/org/apache/iotdb/db/service/DataNode.java
@@ -236,10 +236,12 @@ public class DataNode extends ServerCommandLine implements DataNodeMBean {
       pullAndCheckSystemConfigurations();
 
       if (isFirstStart) {
+        // ========Generate system file immediately after registered from ConfigNode========
         sendRegisterRequestToConfigNode(true);
         IoTDBStartCheck.getInstance().generateOrOverwriteSystemPropertiesFile();
-        IoTDBStartCheck.getInstance().serializeEncryptMagicString();
         ConfigNodeInfo.getInstance().storeConfigNodeList();
+        // =================================================================================
+        IoTDBStartCheck.getInstance().serializeEncryptMagicString();
         // Register this DataNode to the cluster when first start
         sendRegisterRequestToConfigNode(false);
         saveSecretKey();