[jira] [Created] (IOTDB-5110) Add tests of fast compaction performer
周沛辰 created IOTDB-5110: -- Summary: Add tests of fast compaction performer Key: IOTDB-5110 URL: https://issues.apache.org/jira/browse/IOTDB-5110 Project: Apache IoTDB Issue Type: Task Reporter: 周沛辰 Assignee: 周沛辰 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4595) It is recommended to add real-time monitoring data for tsfile merge
[ https://issues.apache.org/jira/browse/IOTDB-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liuxuxin reassigned IOTDB-4595: --- Assignee: Liuxuxin (was: 张洪胤) > It is recommended to add real-time monitoring data for tsfile merge > --- > > Key: IOTDB-4595 > URL: https://issues.apache.org/jira/browse/IOTDB-4595 > Project: Apache IoTDB > Issue Type: Improvement > Components: Connectors/Grafana >Affects Versions: 0.13.3 >Reporter: xiaozhihong >Assignee: Liuxuxin >Priority: Minor > Attachments: Apache IoTDB Dashboard v0.13.1.json, > image-2022-10-10-15-50-49-400.png > > > Currently, only sequence tsfile, unsequence tsfile, and wal folder are > monitored in the grafana monitoring interface, but file used by compaction > are not monitored. > !image-2022-10-10-15-50-49-400.png|width=531,height=121! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5109) [Snapshot] Fix npe because role folder is empty when load snapshot
张洪胤 created IOTDB-5109: -- Summary: [Snapshot] Fix npe because role folder is empty when load snapshot Key: IOTDB-5109 URL: https://issues.apache.org/jira/browse/IOTDB-5109 Project: Apache IoTDB Issue Type: Bug Reporter: 张洪胤 Assignee: 张洪胤 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [iotdb-client-go] HTHou merged pull request #65: add ConnectRetryMax for config
HTHou merged PR #65: URL: https://github.com/apache/iotdb-client-go/pull/65 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (IOTDB-5101) Last flush time may replaced by previous files when recovering
[ https://issues.apache.org/jira/browse/IOTDB-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17642274#comment-17642274 ] Jialin Qiao commented on IOTDB-5101: https://issues.apache.org/jira/browse/IOTDB-5101https://issues.apache.org/jira/browse/IOTDB-5101 > Last flush time may replaced by previous files when recovering > -- > > Key: IOTDB-5101 > URL: https://issues.apache.org/jira/browse/IOTDB-5101 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Recover >Reporter: Haiming Zhu >Assignee: Haiming Zhu >Priority: Major > Labels: pull-request-available > Fix For: 1.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5103) LastFlushTime may be set incorrectly when DataRegion recovering
[ https://issues.apache.org/jira/browse/IOTDB-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17642273#comment-17642273 ] Jialin Qiao commented on IOTDB-5103: https://github.com/apache/iotdb/pull/8285 > LastFlushTime may be set incorrectly when DataRegion recovering > --- > > Key: IOTDB-5103 > URL: https://issues.apache.org/jira/browse/IOTDB-5103 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Jinrui Zhang >Assignee: Jinrui Zhang >Priority: Major > > During the DataRegion recovering, the unsealed file may be read before the > complete of sealed TsFile, which will lead to the incorrect lastFlushTime for > current DataRegion. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5101) Last flush time may replaced by previous files when recovering
[ https://issues.apache.org/jira/browse/IOTDB-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17642276#comment-17642276 ] Jialin Qiao commented on IOTDB-5101: https://issues.apache.org/jira/browse/IOTDB-5103 > Last flush time may replaced by previous files when recovering > -- > > Key: IOTDB-5101 > URL: https://issues.apache.org/jira/browse/IOTDB-5101 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Recover >Reporter: Haiming Zhu >Assignee: Haiming Zhu >Priority: Major > Labels: pull-request-available > Fix For: 1.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [iotdb-client-go] manlge opened a new pull request, #65: add ConnectRetryMax for config
manlge opened a new pull request, #65: URL: https://github.com/apache/iotdb-client-go/pull/65 Add ConnectRetryMax to config and apply it for session.reconnect() -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [iotdb-bin-resources] qiaojialin merged pull request #49: Add a data resource file
qiaojialin merged PR #49: URL: https://github.com/apache/iotdb-bin-resources/pull/49 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Reopened] (IOTDB-5069) The thread number of ConfigNode increases when the the number of DataNode increases
[ https://issues.apache.org/jira/browse/IOTDB-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongzao Dan reopened IOTDB-5069: > The thread number of ConfigNode increases when the the number of DataNode > increases > --- > > Key: IOTDB-5069 > URL: https://issues.apache.org/jira/browse/IOTDB-5069 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Gaofei Cao >Assignee: Yongzao Dan >Priority: Minor > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5096) DataRegionGroup is front of SchemaRegionGroup
[ https://issues.apache.org/jira/browse/IOTDB-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17642213#comment-17642213 ] Yongzao Dan commented on IOTDB-5096: This scenario is because that when we enable auto create Schema feature, the DataNode should get the DataPartition first, thereby it can route this request to the DataNode where the DataPartition resides in and processes the Schema Check. Therefore, this result is normal and we won't improve it. > DataRegionGroup is front of SchemaRegionGroup > - > > Key: IOTDB-5096 > URL: https://issues.apache.org/jira/browse/IOTDB-5096 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Gaofei Cao >Assignee: Yongzao Dan >Priority: Major > Attachments: image-2022-12-01-11-01-25-686.png > > > !image-2022-12-01-11-01-25-686.png|width=536,height=272! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5108) Migrate Region SQL/Shell
Gaofei Cao created IOTDB-5108: - Summary: Migrate Region SQL/Shell Key: IOTDB-5108 URL: https://issues.apache.org/jira/browse/IOTDB-5108 Project: Apache IoTDB Issue Type: Improvement Reporter: Gaofei Cao Assignee: 陈哲涵 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5107) [confignode] cn_internal_address should not bind IP address
[ https://issues.apache.org/jira/browse/IOTDB-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao reassigned IOTDB-5107: -- Assignee: Gaofei Cao (was: Xinyu Tan) > [confignode] cn_internal_address should not bind IP address > --- > > Key: IOTDB-5107 > URL: https://issues.apache.org/jira/browse/IOTDB-5107 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: changxue >Assignee: Gaofei Cao >Priority: Blocker > Attachments: image-2022-12-01-22-10-49-805.png > > > [confignode] cn_internal_address should not bind IP address > description: > The docker container of config node start failed, because it do socket > connection to itself -- a16/172.20.31.16:22277 > a16 is the hostname of computer and the IP address upstairs is the real IP of > computer. > 我希望confignode只是使用我指定的域名进行绑定，而不是IP地址。因为IP地址又可能是container > 的IP，也有可能是物理机的IP，如果只绑定一个，我将不能使用bridge网络。只能使用host或者overlay网络。 > 与22278端口一样处理就很好。 > 另外，为什么启动confignode时，它会连接它自己，因为这是第一个启动的confignode吗？ > !image-2022-12-01-22-10-49-805.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5107) [confignode] cn_internal_address should not bind IP address
[ https://issues.apache.org/jira/browse/IOTDB-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao reassigned IOTDB-5107: -- Assignee: Xinyu Tan (was: Jinrui Zhang) > [confignode] cn_internal_address should not bind IP address > --- > > Key: IOTDB-5107 > URL: https://issues.apache.org/jira/browse/IOTDB-5107 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: 1.0.0 >Reporter: changxue >Assignee: Xinyu Tan >Priority: Blocker > Attachments: image-2022-12-01-22-10-49-805.png > > > [confignode] cn_internal_address should not bind IP address > description: > The docker container of config node start failed, because it do socket > connection to itself -- a16/172.20.31.16:22277 > a16 is the hostname of computer and the IP address upstairs is the real IP of > computer. > 我希望confignode只是使用我指定的域名进行绑定，而不是IP地址。因为IP地址又可能是container > 的IP，也有可能是物理机的IP，如果只绑定一个，我将不能使用bridge网络。只能使用host或者overlay网络。 > 与22278端口一样处理就很好。 > 另外，为什么启动confignode时，它会连接它自己，因为这是第一个启动的confignode吗？ > !image-2022-12-01-22-10-49-805.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5107) [confignode] cn_internal_address should not bind IP address
changxue created IOTDB-5107: --- Summary: [confignode] cn_internal_address should not bind IP address Key: IOTDB-5107 URL: https://issues.apache.org/jira/browse/IOTDB-5107 Project: Apache IoTDB Issue Type: Bug Affects Versions: 1.0.0 Reporter: changxue Assignee: Jinrui Zhang Attachments: image-2022-12-01-22-10-49-805.png [confignode] cn_internal_address should not bind IP address description: The docker container of config node start failed, because it do socket connection to itself -- a16/172.20.31.16:22277 a16 is the hostname of computer and the IP address upstairs is the real IP of computer. 我希望confignode只是使用我指定的域名进行绑定，而不是IP地址。因为IP地址又可能是container 的IP，也有可能是物理机的IP，如果只绑定一个，我将不能使用bridge网络。只能使用host或者overlay网络。 与22278端口一样处理就很好。 另外，为什么启动confignode时，它会连接它自己，因为这是第一个启动的confignode吗？ !image-2022-12-01-22-10-49-805.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-4546) Add Procedure development guide
[ https://issues.apache.org/jira/browse/IOTDB-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641935#comment-17641935 ] 伊丹翔 commented on IOTDB-4546: doc: https://apache-iotdb.feishu.cn/docx/Jk80dB4ODoMOCyx6jWOc0bI6nZb > Add Procedure development guide > --- > > Key: IOTDB-4546 > URL: https://issues.apache.org/jira/browse/IOTDB-4546 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Jialin Qiao >Assignee: 伊丹翔 >Priority: Minor > > Add a guide for developing a new procedure process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5020) Throw NPE in CI testCreateSnapshotWithUnclosedTsFile
[ https://issues.apache.org/jira/browse/IOTDB-5020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao reassigned IOTDB-5020: -- Assignee: Liuxuxin > Throw NPE in CI testCreateSnapshotWithUnclosedTsFile > > > Key: IOTDB-5020 > URL: https://issues.apache.org/jira/browse/IOTDB-5020 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Jialin Qiao >Assignee: Liuxuxin >Priority: Minor > Attachments: image-2022-11-22-17-43-52-344.png > > > https://github.com/apache/iotdb/actions/runs/3519541019/jobs/5899596610 > > Error: Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 32.374 s <<< FAILURE! - in > org.apache.iotdb.db.engine.snapshot.IoTDBSnapshotTest > [12241|https://github.com/apache/iotdb/actions/runs/3519541019/jobs/5899596610#step:6:12242]Error: > > testCreateSnapshotWithUnclosedTsFile(org.apache.iotdb.db.engine.snapshot.IoTDBSnapshotTest) > Time elapsed: 15.801 s <<< ERROR! > [12242|https://github.com/apache/iotdb/actions/runs/3519541019/jobs/5899596610#step:6:12243]java.lang.NullPointerException > > [12243|https://github.com/apache/iotdb/actions/runs/3519541019/jobs/5899596610#step:6:12244] > at > org.apache.iotdb.db.engine.snapshot.IoTDBSnapshotTest.tearDown(IoTDBSnapshotTest.java:60) > > > !image-2022-11-22-17-43-52-344.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5106) Parse PathPattern to Deterministic Finite Automate
[ https://issues.apache.org/jira/browse/IOTDB-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yanze chen reassigned IOTDB-5106: - Assignee: yanze chen > Parse PathPattern to Deterministic Finite Automate > -- > > Key: IOTDB-5106 > URL: https://issues.apache.org/jira/browse/IOTDB-5106 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: yanze chen >Assignee: yanze chen >Priority: Major > > https://apache-iotdb.feishu.cn/docx/DjrAdDM3woXcn1x5Phlcyveznqe -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5106) Parse PathPattern to Deterministic Finite Automate
yanze chen created IOTDB-5106: - Summary: Parse PathPattern to Deterministic Finite Automate Key: IOTDB-5106 URL: https://issues.apache.org/jira/browse/IOTDB-5106 Project: Apache IoTDB Issue Type: New Feature Reporter: yanze chen https://apache-iotdb.feishu.cn/docx/DjrAdDM3woXcn1x5Phlcyveznqe -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5105) Can not register new confignode to cluster
[ https://issues.apache.org/jira/browse/IOTDB-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641825#comment-17641825 ] Jialin Qiao commented on IOTDB-5105: !image-2022-12-01-18-51-38-262.png|width=1100,height=645! > Can not register new confignode to cluster > -- > > Key: IOTDB-5105 > URL: https://issues.apache.org/jira/browse/IOTDB-5105 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Cluster >Reporter: Houliang Qi >Priority: Critical > Labels: pull-request-available > Attachments: image-2022-12-01-17-58-05-668.png, > image-2022-12-01-18-51-38-262.png > > > Hi, I found one bug when registering a new confignode to the cluster. > when registering the new confignode to the cluster, the target confignode > will check the > _least_data_region_group_num_ , however, the parameter can auto-be adjusted > in the cluster, which causes the node that wants to register the cluster can > not to register successfully. > > !image-2022-12-01-17-58-05-668.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5105) Can not register new confignode to cluster
[ https://issues.apache.org/jira/browse/IOTDB-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641824#comment-17641824 ] Jialin Qiao commented on IOTDB-5105: Reproduce: Start 1C1D Create some databases. When you see the following log in ConfigNode, then adding a new ConfigNode will fail. 2022-12-01 18:45:30,052 [pool-12-IoTDB-ConfigNodeRPC-Processor-4] INFO o.a.i.c.m.ClusterSchemaManager:335 - [AdjustRegionGroupNum] The least number of DataRegionGroups per Database is adjusted to: 4 > Can not register new confignode to cluster > -- > > Key: IOTDB-5105 > URL: https://issues.apache.org/jira/browse/IOTDB-5105 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Cluster >Reporter: Houliang Qi >Priority: Critical > Attachments: image-2022-12-01-17-58-05-668.png > > > Hi, I found one bug when registering a new confignode to the cluster. > when registering the new confignode to the cluster, the target confignode > will check the > _least_data_region_group_num_ , however, the parameter can auto-be adjusted > in the cluster, which causes the node that wants to register the cluster can > not to register successfully. > > !image-2022-12-01-17-58-05-668.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5101) Last flush time may replaced by previous files when recovering
[ https://issues.apache.org/jira/browse/IOTDB-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haiming Zhu reassigned IOTDB-5101: -- Component/s: Core/Recover Fix Version/s: 1.0.0 Sprint: 2022-11-Cluster Assignee: Haiming Zhu > Last flush time may replaced by previous files when recovering > -- > > Key: IOTDB-5101 > URL: https://issues.apache.org/jira/browse/IOTDB-5101 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Recover >Reporter: Haiming Zhu >Assignee: Haiming Zhu >Priority: Major > Fix For: 1.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5105) Can not register new confignode to cluster
Houliang Qi created IOTDB-5105: -- Summary: Can not register new confignode to cluster Key: IOTDB-5105 URL: https://issues.apache.org/jira/browse/IOTDB-5105 Project: Apache IoTDB Issue Type: Bug Components: Core/Cluster Reporter: Houliang Qi Attachments: image-2022-12-01-17-58-05-668.png Hi, I found one bug when registering a new confignode to the cluster. when registering the new confignode to the cluster, the target confignode will check the _least_data_region_group_num_ , however, the parameter can auto-be adjusted in the cluster, which causes the node that wants to register the cluster can not to register successfully. !image-2022-12-01-17-58-05-668.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5103) LastFlushTime may be set incorrectly when DataRegion recovering
Jinrui Zhang created IOTDB-5103: --- Summary: LastFlushTime may be set incorrectly when DataRegion recovering Key: IOTDB-5103 URL: https://issues.apache.org/jira/browse/IOTDB-5103 Project: Apache IoTDB Issue Type: Bug Reporter: Jinrui Zhang Assignee: Jinrui Zhang During the DataRegion recovering, the unsealed file may be read before the complete of sealed TsFile, which will lead to the incorrect lastFlushTime for current DataRegion. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5104) [Benchmark] Support taos 3.x version
张洪胤 created IOTDB-5104: -- Summary: [Benchmark] Support taos 3.x version Key: IOTDB-5104 URL: https://issues.apache.org/jira/browse/IOTDB-5104 Project: Apache IoTDB Issue Type: Improvement Reporter: 张洪胤 Assignee: 张洪胤 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5102) Get a null result when explain the sql using align by device
yang caiyin created IOTDB-5102: -- Summary: Get a null result when explain the sql using align by device Key: IOTDB-5102 URL: https://issues.apache.org/jira/browse/IOTDB-5102 Project: Apache IoTDB Issue Type: Bug Components: Core/Server Reporter: yang caiyin Assignee: yang caiyin Attachments: image-2022-12-01-17-54-00-997.png !image-2022-12-01-17-54-00-997.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5101) Last flush time is replaced when recovering
Haiming Zhu created IOTDB-5101: -- Summary: Last flush time is replaced when recovering Key: IOTDB-5101 URL: https://issues.apache.org/jira/browse/IOTDB-5101 Project: Apache IoTDB Issue Type: Bug Reporter: Haiming Zhu -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5100) [Benchmark] Support TimescaleDB Cluster
张洪胤 created IOTDB-5100: -- Summary: [Benchmark] Support TimescaleDB Cluster Key: IOTDB-5100 URL: https://issues.apache.org/jira/browse/IOTDB-5100 Project: Apache IoTDB Issue Type: Improvement Reporter: 张洪胤 Assignee: 张洪胤 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5099) [Benchmark] Optimize the generation of out-of-order data
[ https://issues.apache.org/jira/browse/IOTDB-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641779#comment-17641779 ] 张洪胤 commented on IOTDB-5099: https://github.com/thulab/iot-benchmark/pull/311 > [Benchmark] Optimize the generation of out-of-order data > > > Key: IOTDB-5099 > URL: https://issues.apache.org/jira/browse/IOTDB-5099 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: 张洪胤 >Assignee: 张洪胤 >Priority: Major > Original Estimate: 2h > Remaining Estimate: 2h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5099) [Benchmark] Optimize the generation of out-of-order data
张洪胤 created IOTDB-5099: -- Summary: [Benchmark] Optimize the generation of out-of-order data Key: IOTDB-5099 URL: https://issues.apache.org/jira/browse/IOTDB-5099 Project: Apache IoTDB Issue Type: Improvement Reporter: 张洪胤 Assignee: 张洪胤 -- This message was sent by Atlassian Jira (v8.20.10#820010)
