[jira] [Assigned] (IOTDB-5649) Refactor ExpressionAnalyzer using visitor pattern
[ https://issues.apache.org/jira/browse/IOTDB-5649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LiYuheng reassigned IOTDB-5649: --- Assignee: LiYuheng (was: Minghui Liu) > Refactor ExpressionAnalyzer using visitor pattern > - > > Key: IOTDB-5649 > URL: https://issues.apache.org/jira/browse/IOTDB-5649 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Minghui Liu >Assignee: LiYuheng >Priority: Major > Labels: pull-request-available > Fix For: master branch > > > ExpressionAnalyzer is the class in charge of handling expressions. > Each method in this class has different ability, such as > searchSourceExpressions() finds out which sources the expression contains, > removeWildcardInExpression() remove * from expression, and so on. > There were some redundant logic in ExpressionAnalyzer's methods. To make it > easier to add new kinds of expressions, it's necessary to simplify. > After analyze the similarity between these methods, I believe the visitor > pattern is a good way to make it simple. The same logic can be contained in > superclass-visitor, and the difference can be implemented by > subclass-visitor's override. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6129) ConfigNode restarts without relying on Seed-ConfigNode
[ https://issues.apache.org/jira/browse/IOTDB-6129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LiYuheng reassigned IOTDB-6129: --- Assignee: LiYuheng > ConfigNode restarts without relying on Seed-ConfigNode > -- > > Key: IOTDB-6129 > URL: https://issues.apache.org/jira/browse/IOTDB-6129 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Cluster >Reporter: LiYuheng >Assignee: LiYuheng >Priority: Major > > [https://apache-iotdb.feishu.cn/docs/doccnSfXXrSbLu3ETmDWLY5tmwu#H8SOcB] > [https://github.com/apache/iotdb/pull/10988] > > As of version 1.2.1, the roles of the current ConfigNode are divided into > Seed-ConfigNode and non-Seed-ConfigNode. The former is the first started > ConfigNode, and the latter is the ConfigNode started later. > After forming a multi-replica ConfigNode cluster, a Leader-ConfigNode and > several Follower-ConfigNodes are selected. The expected behavior is that when > a small number of ConfigNode nodes go down, the ConfigNode cluster can still > elect a Leader and provide services to meet high availability requirements. > However, in the current implementation, the non-Seed-ConfigNode depends on > the Seed-ConfigNode during restart. That is, if the Seed-ConfigNode goes > down, other non-Seed-ConfigNodes cannot restart, which poses a risk to the > high availability guarantee of the IoTDB ConfigNode cluster. > Therefore, it is expected in version 1.2.2 to remove the dependency of > non-Seed-ConfigNode on Seed-ConfigNode during restart, further enhancing the > high availability of IoTDB ConfigNode. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6129) ConfigNode restarts without relying on Seed-ConfigNode
LiYuheng created IOTDB-6129: --- Summary: ConfigNode restarts without relying on Seed-ConfigNode Key: IOTDB-6129 URL: https://issues.apache.org/jira/browse/IOTDB-6129 Project: Apache IoTDB Issue Type: Improvement Components: Core/Cluster Reporter: LiYuheng [https://apache-iotdb.feishu.cn/docs/doccnSfXXrSbLu3ETmDWLY5tmwu#H8SOcB] [https://github.com/apache/iotdb/pull/10988] As of version 1.2.1, the roles of the current ConfigNode are divided into Seed-ConfigNode and non-Seed-ConfigNode. The former is the first started ConfigNode, and the latter is the ConfigNode started later. After forming a multi-replica ConfigNode cluster, a Leader-ConfigNode and several Follower-ConfigNodes are selected. The expected behavior is that when a small number of ConfigNode nodes go down, the ConfigNode cluster can still elect a Leader and provide services to meet high availability requirements. However, in the current implementation, the non-Seed-ConfigNode depends on the Seed-ConfigNode during restart. That is, if the Seed-ConfigNode goes down, other non-Seed-ConfigNodes cannot restart, which poses a risk to the high availability guarantee of the IoTDB ConfigNode cluster. Therefore, it is expected in version 1.2.2 to remove the dependency of non-Seed-ConfigNode on Seed-ConfigNode during restart, further enhancing the high availability of IoTDB ConfigNode. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-6125) Fix DataPartition allocation bug when insert big batch data
[ https://issues.apache.org/jira/browse/IOTDB-6125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761159#comment-17761159 ] LiYuheng commented on IOTDB-6125: - iotdb使用默认配置，bm将DEVICE_NUM_PER_WRITE设为1000，BATCH_SIZE_PER_WRITE设为1，应该就能复现当时的问题。 完整配置见附件。 > Fix DataPartition allocation bug when insert big batch data > --- > > Key: IOTDB-6125 > URL: https://issues.apache.org/jira/browse/IOTDB-6125 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Yongzao Dan >Assignee: Yongzao Dan >Priority: Major > Labels: pull-request-available > Attachments: iotd与bm配置.zip > > > The DataPartitions will be allocated un-balanced if the user insert a big > batch data to the cluster firstly. Because the RegionGroup > quickly-extension-policy doesn't extend enough RegionGroups for the special > case. > > In this PR, the RegionGroup extension policy will always ensure the database > have enough RegionGroups for allocate new Partitions balancely. > > And this PR also add some concise log to record the DataAllotTable -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6150) Remove datanode/system/compression_ratio
LiYuheng created IOTDB-6150: --- Summary: Remove datanode/system/compression_ratio Key: IOTDB-6150 URL: https://issues.apache.org/jira/browse/IOTDB-6150 Project: Apache IoTDB Issue Type: Improvement Components: Core/Server Reporter: LiYuheng Assignee: LiYuheng Now we check compression_ratio from metric, so this file (datanode/system/compression_ratio) is not necessary now. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6151) Move datanode/schema/system.properties to datanode/system.properties
LiYuheng created IOTDB-6151: --- Summary: Move datanode/schema/system.properties to datanode/system.properties Key: IOTDB-6151 URL: https://issues.apache.org/jira/browse/IOTDB-6151 Project: Apache IoTDB Issue Type: Improvement Reporter: LiYuheng Assignee: LiYuheng system.properties contains all kinds configuration, not only schema configuration. So it's better to move this file to `datanode` directory. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6150) Remove datanode/system/compression_ratio
[ https://issues.apache.org/jira/browse/IOTDB-6150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LiYuheng reassigned IOTDB-6150: --- Assignee: (was: LiYuheng) > Remove datanode/system/compression_ratio > > > Key: IOTDB-6150 > URL: https://issues.apache.org/jira/browse/IOTDB-6150 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Server >Reporter: LiYuheng >Priority: Minor > > Now we check compression_ratio from metric, so this file > (datanode/system/compression_ratio) is not necessary now. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-6150) Remove datanode/system/compression_ratio
[ https://issues.apache.org/jira/browse/IOTDB-6150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] LiYuheng reassigned IOTDB-6150: --- Assignee: LiYuheng > Remove datanode/system/compression_ratio > > > Key: IOTDB-6150 > URL: https://issues.apache.org/jira/browse/IOTDB-6150 > Project: Apache IoTDB > Issue Type: Improvement > Components: Core/Server >Reporter: LiYuheng >Assignee: LiYuheng >Priority: Minor > > Now we check compression_ratio from metric, so this file > (datanode/system/compression_ratio) is not necessary now. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6345) Auto create database fail after drop database
LiYuheng created IOTDB-6345: --- Summary: Auto create database fail after drop database Key: IOTDB-6345 URL: https://issues.apache.org/jira/browse/IOTDB-6345 Project: Apache IoTDB Issue Type: Bug Reporter: LiYuheng -- This message was sent by Atlassian Jira (v8.20.10#820010)
