[jira] [Created] (IOTDB-4678) [sync] Sync DataNode start-up process
yanze chen created IOTDB-4678: - Summary: [sync] Sync DataNode start-up process Key: IOTDB-4678 URL: https://issues.apache.org/jira/browse/IOTDB-4678 Project: Apache IoTDB Issue Type: New Feature Reporter: yanze chen Assignee: yanze chen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4677) [sync] Support sync DeleteData
yanze chen created IOTDB-4677: - Summary: [sync] Support sync DeleteData Key: IOTDB-4677 URL: https://issues.apache.org/jira/browse/IOTDB-4677 Project: Apache IoTDB Issue Type: New Feature Reporter: yanze chen Assignee: yusicheng * Support collect DeleteData in sender * Add new PipeData type * Support load DeleteData in receiver -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4676) [sync] Support sync DeleteTimeseries
yanze chen created IOTDB-4676: - Summary: [sync] Support sync DeleteTimeseries Key: IOTDB-4676 URL: https://issues.apache.org/jira/browse/IOTDB-4676 Project: Apache IoTDB Issue Type: New Feature Reporter: yanze chen Assignee: yusicheng * Support collect DeleteTimeseries in sender * Add new PipeData type * Support load DeleteTimeseries in receiver -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4675) Support load mlog.bin
Jialin Qiao created IOTDB-4675: -- Summary: Support load mlog.bin Key: IOTDB-4675 URL: https://issues.apache.org/jira/browse/IOTDB-4675 Project: Apache IoTDB Issue Type: New Feature Reporter: Jialin Qiao Assignee: yanze chen Get a mlog.bin file in an IoTDB, and load this mlog.bin into another IoTDB(may contains schema). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4674) settle.sh can not work in 0.14.0-preview
[ https://issues.apache.org/jira/browse/IOTDB-4674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haonan Hou reassigned IOTDB-4674: - Assignee: 周沛辰 > settle.sh can not work in 0.14.0-preview > > > Key: IOTDB-4674 > URL: https://issues.apache.org/jira/browse/IOTDB-4674 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: 0.14.0-SNAPSHOT >Reporter: Haonan Hou >Assignee: 周沛辰 >Priority: Major > > How to reproduce: > insert into root.sg.d1(time,s1) values(1,1) > flush > delete from root.sg.d1.s1 where time > 0 > Stop IoTDB server > run ./settle.sh /data/data > Start IoTDB server > select ** from root > Then you can see the data that should be deleted. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4674) settle.sh can not work in 0.14.0-preview
Haonan Hou created IOTDB-4674: - Summary: settle.sh can not work in 0.14.0-preview Key: IOTDB-4674 URL: https://issues.apache.org/jira/browse/IOTDB-4674 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.14.0-SNAPSHOT Reporter: Haonan Hou How to reproduce: insert into root.sg.d1(time,s1) values(1,1) flush delete from root.sg.d1.s1 where time > 0 Stop IoTDB server run ./settle.sh /data/data Start IoTDB server select ** from root Then you can see the data that should be deleted. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4673) [ confignode/datanode configuration parameters ] Removes the space character from both the start and the end of the parameter value
刘珍 created IOTDB-4673:
-
Summary: [ confignode/datanode configuration parameters ] Removes
the space character from both the start and the end of the parameter value
Key: IOTDB-4673
URL: https://issues.apache.org/jira/browse/IOTDB-4673
Project: Apache IoTDB
Issue Type: Improvement
Components: mpp-cluster
Reporter: 刘珍
Assignee: Jialin Qiao
举个例子
data_region_ratis_max_retry_attempts = 2
confignode配置文件中的这个参数值后面不小心多了1个空格"2 " ，启动confignode报错
confignode/datanode配置参数在代码里需要过滤掉空格。
2022-10-18 09:31:12,529 [main] INFO o.a.i.m.c.MetricConfigDescriptor:54 -
Start to read config file ./confignode/sbin/../conf/iotdb-metric.yml
Exception in thread "main" java.lang.ExceptionInInitializerError
at
org.apache.iotdb.confignode.conf.ConfigNodeDescriptor.getInstance(ConfigNodeDescriptor.java:491)
at
org.apache.iotdb.confignode.service.ConfigNode.(ConfigNode.java:55)
{color:#DE350B}*Caused by: java.lang.NumberFormatException: For input string:
"2 "*{color}
at
java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.base/java.lang.Integer.parseInt(Integer.java:652)
at java.base/java.lang.Integer.parseInt(Integer.java:770)
at
org.apache.iotdb.confignode.conf.ConfigNodeDescriptor.loadRatisConsensusConfig(ConfigNodeDescriptor.java:446)
at
org.apache.iotdb.confignode.conf.ConfigNodeDescriptor.loadProps(ConfigNodeDescriptor.java:272)
at
org.apache.iotdb.confignode.conf.ConfigNodeDescriptor.(ConfigNodeDescriptor.java:47)
at
org.apache.iotdb.confignode.conf.ConfigNodeDescriptor.(ConfigNodeDescriptor.java:39)
at
org.apache.iotdb.confignode.conf.ConfigNodeDescriptor$ConfigNodeDescriptorHolder.(ConfigNodeDescriptor.java:496)
... 2 more
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IOTDB-4664) Add UpdatePeer Interface in IConsensus
[ https://issues.apache.org/jira/browse/IOTDB-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17619178#comment-17619178 ] 伊丹翔 commented on IOTDB-4664: doc: https://apache-iotdb.feishu.cn/docx/doxcn8FueTE5MKKJAY3Pn79m3vf > Add UpdatePeer Interface in IConsensus > -- > > Key: IOTDB-4664 > URL: https://issues.apache.org/jira/browse/IOTDB-4664 > Project: Apache IoTDB > Issue Type: Task >Reporter: 伊丹翔 >Assignee: 伊丹翔 >Priority: Major > Labels: pull-request-available > > To support modifying ip:port function, we need to provide updatePeer > interface in IConsensus for updating Consensus layer. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4672) Experiments for the writing speed and memory occupation about 1C1D and CDN(ConfigNodeDataNode)
Gaofei Cao created IOTDB-4672: - Summary: Experiments for the writing speed and memory occupation about 1C1D and CDN(ConfigNodeDataNode) Key: IOTDB-4672 URL: https://issues.apache.org/jira/browse/IOTDB-4672 Project: Apache IoTDB Issue Type: Improvement Reporter: Gaofei Cao Assignee: 陈哲涵 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-4644) Support modify DataNode's IP:Port
[ https://issues.apache.org/jira/browse/IOTDB-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17619175#comment-17619175 ] 伊丹翔 commented on IOTDB-4644: doc: https://apache-iotdb.feishu.cn/docx/doxcn9d2kMsgvgCH5NotNRKoVoQ#doxcnIeI8YM6UWqKmQ3BbeL5yPh > Support modify DataNode's IP:Port > - > > Key: IOTDB-4644 > URL: https://issues.apache.org/jira/browse/IOTDB-4644 > Project: Apache IoTDB > Issue Type: Task >Reporter: 伊丹翔 >Assignee: 伊丹翔 >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [iotdb-client-go] HTHou merged pull request #53: Update README, add Troubleshooting section
HTHou merged PR #53: URL: https://github.com/apache/iotdb-client-go/pull/53 -- 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-client-go] citrusreticulata commented on a diff in pull request #53: Update README, add Troubleshooting section
citrusreticulata commented on code in PR #53: URL: https://github.com/apache/iotdb-client-go/pull/53#discussion_r996841350 ## README.md: ## @@ -92,3 +92,19 @@ go run session_example.go * make >= 3.0 * curl >= 7.1.1 * thrift 0.15.0 + +## Troubleshooting + +### Thrift version compatibility issues + +In the branch `rel/0.13.0` and earlier versions, the version of apache/thrift is `v0.14.1`. Review Comment: Fixed. Thanks a lot! ## README_ZH.md: ## @@ -89,3 +89,18 @@ go run session_example.go * make >= 3.0 * curl >= 7.1.1 * thrift 0.15.0 + +## 疑难解答 + +### thrift 版本兼容性问题 + +分支`rel/0.13.0`以及更早前的版本中，apache/thrift的版本为`v0.14.1`。 Review Comment: Fixed. Thanks a lot! -- 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-client-go] HTHou commented on a diff in pull request #53: Update README, add Troubleshooting section
HTHou commented on code in PR #53: URL: https://github.com/apache/iotdb-client-go/pull/53#discussion_r996831188 ## README_ZH.md: ## @@ -89,3 +89,18 @@ go run session_example.go * make >= 3.0 * curl >= 7.1.1 * thrift 0.15.0 + +## 疑难解答 + +### thrift 版本兼容性问题 + +分支`rel/0.13.0`以及更早前的版本中，apache/thrift的版本为`v0.14.1`。 Review Comment: ```suggestion 分支`rel/0.13`以及更早前的版本中，apache/thrift的版本为`v0.14.1`。 ``` -- 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-client-go] HTHou commented on a diff in pull request #53: Update README, add Troubleshooting section
HTHou commented on code in PR #53: URL: https://github.com/apache/iotdb-client-go/pull/53#discussion_r996830705 ## README.md: ## @@ -92,3 +92,19 @@ go run session_example.go * make >= 3.0 * curl >= 7.1.1 * thrift 0.15.0 + +## Troubleshooting + +### Thrift version compatibility issues + +In the branch `rel/0.13.0` and earlier versions, the version of apache/thrift is `v0.14.1`. Review Comment: ```suggestion In the branch `rel/0.13` and earlier versions, the version of apache/thrift is `v0.14.1`. ``` -- 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-client-go] citrusreticulata opened a new pull request, #53: Update README, add Troubleshooting section
citrusreticulata opened a new pull request, #53: URL: https://github.com/apache/iotdb-client-go/pull/53 Update README, add Troubleshooting section. Describes the possible causes of the thrift compatibility problem and some using tips. -- 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] [Created] (IOTDB-4671) [ MultiLeaderConsensus ] snapshot is not deleted after load snapshot
刘珍 created IOTDB-4671: - Summary: [ MultiLeaderConsensus ] snapshot is not deleted after load snapshot Key: IOTDB-4671 URL: https://issues.apache.org/jira/browse/IOTDB-4671 Project: Apache IoTDB Issue Type: Improvement Components: mpp-cluster Reporter: 刘珍 Assignee: Jinrui Zhang Attachments: image-2022-10-17-16-55-13-402.png master_1013_00dc222 schema : ratis data : MultiLeaderConsensus 3副本，3C5D , 缩容1个节点（ip72） new peer load snapshot 后，迁移过来的dataregion中的snapshot 没有删除。 ip73 共识层的文件信息： !image-2022-10-17-16-55-13-402.png! 测试环境： -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-4623) [ remove ConfigNode ] Surviving confignodes after removing other confignodes need to be updated confignode_list
[
https://issues.apache.org/jira/browse/IOTDB-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17618715#comment-17618715
]
刘珍 commented on IOTDB-4623:
---
master_1017_0ebc42f ，验证通过。
> [ remove ConfigNode ] Surviving confignodes after removing other confignodes
> need to be updated confignode_list
> ---
>
> Key: IOTDB-4623
> URL: https://issues.apache.org/jira/browse/IOTDB-4623
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: 陈哲涵
>Priority: Major
> Labels: pull-request-available
> Attachments: config.properties
>
>
> master_1010_9917053
> 3 ConfigNode , Successfully removed 1 confignode (follower ,ip:port ，ip66) ,
> remove another follower confignode （NodeID ，ip68），{color:#DE350B}*Error
> reported, but removed successfully *{color}：
> 2022-10-12 10:40:21,083 [main] WARN
> o.a.i.c.c.s.c.SyncConfigNodeClientPool:95 - REMOVE_CONFIG_NODE
> {color:#DE350B}*failed on ConfigNode TEndPoint(ip:192.168.10.66,
> port:22277)*{color}, because Borrow client from pool for node
> TEndPoint(ip:192.168.10.66, port:22277) failed., retrying 5...
> 2022-10-12 10:40:24,284 [main] ERROR
> o.a.i.c.c.s.c.SyncConfigNodeClientPool:104 - REMOVE_CONFIG_NODE failed on
> ConfigNode TEndPoint(ip:192.168.10.66, port:22277)
> java.io.IOException: Borrow client from pool for node
> TEndPoint(ip:192.168.10.66, port:22277) failed.
> at
> org.apache.iotdb.commons.client.ClientManager.borrowClient(ClientManager.java:61)
> at
> org.apache.iotdb.confignode.client.sync.confignode.SyncConfigNodeClientPool.sendSyncRequestToConfigNodeWithRetry(SyncConfigNodeClientPool.java:72)
> at
> org.apache.iotdb.confignode.conf.ConfigNodeRemoveCheck.removeConfigNode(ConfigNodeRemoveCheck.java:98)
> at
> org.apache.iotdb.confignode.service.ConfigNodeCommandLine.doRemoveNode(ConfigNodeCommandLine.java:112)
> at
> org.apache.iotdb.confignode.service.ConfigNodeCommandLine.run(ConfigNodeCommandLine.java:83)
> at
> org.apache.iotdb.commons.ServerCommandLine.doMain(ServerCommandLine.java:58)
> at
> org.apache.iotdb.confignode.service.ConfigNode.main(ConfigNode.java:71)
> Caused by: net.sf.cglib.core.CodeGenerationException:
> org.apache.thrift.transport.TTransportException-->java.net.ConnectException:
> Connection refused (Connection refused)
> at net.sf.cglib.core.ReflectUtils.newInstance(ReflectUtils.java:235)
> at net.sf.cglib.core.ReflectUtils.newInstance(ReflectUtils.java:220)
> at
> net.sf.cglib.proxy.Enhancer.createUsingReflection(Enhancer.java:639)
> at net.sf.cglib.proxy.Enhancer.firstInstance(Enhancer.java:538)
> at
> net.sf.cglib.core.AbstractClassGenerator.create(AbstractClassGenerator.java:231)
> at net.sf.cglib.proxy.Enhancer.createHelper(Enhancer.java:377)
> at net.sf.cglib.proxy.Enhancer.create(Enhancer.java:304)
> at
> org.apache.iotdb.commons.client.sync.SyncThriftClientWithErrorHandler.newErrorHandler(SyncThriftClientWithErrorHandler.java:48)
> at
> org.apache.iotdb.commons.client.sync.SyncConfigNodeIServiceClient$Factory.makeObject(SyncConfigNodeIServiceClient.java:115)
> at
> org.apache.iotdb.commons.client.sync.SyncConfigNodeIServiceClient$Factory.makeObject(SyncConfigNodeIServiceClient.java:94)
> at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.create(GenericKeyedObjectPool.java:780)
> at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:439)
> at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:350)
> at
> org.apache.iotdb.commons.client.ClientManager.borrowClient(ClientManager.java:50)
> ... 6 common frames omitted
> Caused by: org.apache.thrift.transport.TTransportException:
> java.net.ConnectException: Connection refused (Connection refused)
> at org.apache.thrift.transport.TSocket.open(TSocket.java:243)
> at
> org.apache.iotdb.rpc.TElasticFramedTransport.open(TElasticFramedTransport.java:91)
> at
> org.apache.iotdb.commons.client.sync.SyncConfigNodeIServiceClient.(SyncConfigNodeIServiceClient.java:62)
> at
> org.apache.iotdb.commons.client.sync.SyncConfigNodeIServiceClient$$EnhancerByCGLIB$$763d90ac.()
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
[jira] [Assigned] (IOTDB-4668) create storage group failed with 303 but it exists at the result of show storage group
[ https://issues.apache.org/jira/browse/IOTDB-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haonan Hou reassigned IOTDB-4668: - Assignee: Yukun Zhou (was: Haonan Hou) > create storage group failed with 303 but it exists at the result of show > storage group > -- > > Key: IOTDB-4668 > URL: https://issues.apache.org/jira/browse/IOTDB-4668 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Schema Manager >Affects Versions: 0.14.0-SNAPSHOT >Reporter: changxue >Assignee: Yukun Zhou >Priority: Major > Attachments: image-2022-10-17-15-32-41-422.png > > > create storage group failed with 303 but it exists at the result of show > storage group > 命令行窗口创建下面值的storage group, 创建后报错303（具体日志信息见附件），但是show storage group > 可以看到刚刚创建失败的这个storage group. > > storage group: > root.level2.level3.level4.level5.level6.level7.level8.level9.level10.level11.level12.level13.level14.level15.level16.level17.level18.level19.level20.level21.level22.level23.level24.level25.level26.level27.level28.level29.level30.level31.level32.level33.level34.level35.level36.level37.level38.level39.level40.level41.level42.level43.level44.level45.level46.level47.level48.level49.level50.level51.level52.level53.level54.level55.level56.level57.level58.level59.level60.level61.level62.level63.level64.level65.level66.level67.level68.level69.level70.level71.level72.level73.level74.level75.level76.level77.level78.level79.level80.level81.level82.level83.level84.level85.level86.level87.level88.level89.level90.level91.level92.level93.level94.level95.level96.level97.level98.level99.level100.level101.level102.level103.level104.level105.level106.level107.level108.level109.level110.level111.level112.level113.level114.level115.level116.level117.level118.level119.level120.level121.level122.level123.level124.level125.level126.level127.level128.level129.level130.level131.level132.level133.level134.level135.level136.level137.level138.level139.level140.level141.level142.level143.level144.level145.level146.level147.level148.level149.level150.level151.level152.level153.level154.level155.level156.level157.level158.level159.level160.level161.level162.level163.level164.level165.level166.level167.level168.level169.level170.level171.level172.level173.level174.level175.level176.level177.level178.level179.level180.level181 > > environment: > 1. git pull origin master > 2. mvn clean package -pl server -am -DskipTests > 3. iotdb/server/target/iotdb-server-0.14.0-SNAPSHOT/sbin/start-server.sh > 2022-10-17 172.20.70.44 > > failed info: > !image-2022-10-17-15-32-41-422.png! > > reproduction: > # build the newest source code of master branch, start-server.sh > # start-cli.sh > # show storage group: no such storage group with upstairs value > # create storage group with the value upstairs, failed > # show storage group, it shows the storage group with upstairs value > > 说明： > 使用java原生接口测试，发现该问题。 > 然后使用命令行测试，复现。 > 在0.13.3版本上复测，没有该问题。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [iotdb-client-go] citrusreticulata commented on issue #52: assignment mismatch: 2 variables but thrift.NewTSocketConf returns 1 value
citrusreticulata commented on issue #52: URL: https://github.com/apache/iotdb-client-go/issues/52#issuecomment-1280450348 For more details of differences between two version, please take a look at this PR: https://github.com/apache/iotdb-client-go/pull/41#issue-1313195823 -- 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-client-go] citrusreticulata commented on issue #52: assignment mismatch: 2 variables but thrift.NewTSocketConf returns 1 value
citrusreticulata commented on issue #52:
URL: https://github.com/apache/iotdb-client-go/issues/52#issuecomment-1280445011
Please check the version of thrift and the version of iotdb-clinet-go.
In thrift 0.14.1, function `NewTSocketConf` returns 2 values. It's specific
implementation of this function is as follows:
```
func NewTSocketConf(hostPort string, conf *TConfiguration) (*TSocket, error)
{
addr, err := net.ResolveTCPAddr("tcp", hostPort)
if err != nil {
return nil, err
}
return NewTSocketFromAddrConf(addr, conf), nil
}
```
In thrift 0.15.0, function `NewTSocketConf` returns 1 value. It's specific
implementation of this function is as follows:
```
func NewTSocketConf(hostPort string, conf *TConfiguration) *TSocket {
return NewTSocketFromAddrConf(tcpAddr(hostPort), conf)
}
```
--
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] [Created] (IOTDB-4670) [Trigger] Implement updateTriggerLocation interface
liaolanyu created IOTDB-4670: Summary: [Trigger] Implement updateTriggerLocation interface Key: IOTDB-4670 URL: https://issues.apache.org/jira/browse/IOTDB-4670 Project: Apache IoTDB Issue Type: New Feature Reporter: liaolanyu Assignee: liaolanyu Interface for transferring stateful trigger. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4669) [Trigger] Scheduled task for checking trigger-table of DataNode
liaolanyu created IOTDB-4669: Summary: [Trigger] Scheduled task for checking trigger-table of DataNode Key: IOTDB-4669 URL: https://issues.apache.org/jira/browse/IOTDB-4669 Project: Apache IoTDB Issue Type: New Feature Reporter: liaolanyu Assignee: liaolanyu Trigger-table on DataNode could be out of data due to many reasons. We need to update it in fixed time. You can refer to the doc:https://apache-iotdb.feishu.cn/docx/doxcneSc8w4eRHntxGkH5jpMgfe -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4668) create storage group failed with 303 but it exists at the result of show storage group
[ https://issues.apache.org/jira/browse/IOTDB-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] changxue reassigned IOTDB-4668: --- Assignee: Haonan Hou > create storage group failed with 303 but it exists at the result of show > storage group > -- > > Key: IOTDB-4668 > URL: https://issues.apache.org/jira/browse/IOTDB-4668 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Schema Manager >Affects Versions: master branch >Reporter: changxue >Assignee: Haonan Hou >Priority: Major > Attachments: image-2022-10-17-15-32-41-422.png > > > create storage group failed with 303 but it exists at the result of show > storage group > 命令行窗口创建下面值的storage group, 创建后报错303（具体日志信息见附件），但是show storage group > 可以看到刚刚创建失败的这个storage group. > > storage group: > root.level2.level3.level4.level5.level6.level7.level8.level9.level10.level11.level12.level13.level14.level15.level16.level17.level18.level19.level20.level21.level22.level23.level24.level25.level26.level27.level28.level29.level30.level31.level32.level33.level34.level35.level36.level37.level38.level39.level40.level41.level42.level43.level44.level45.level46.level47.level48.level49.level50.level51.level52.level53.level54.level55.level56.level57.level58.level59.level60.level61.level62.level63.level64.level65.level66.level67.level68.level69.level70.level71.level72.level73.level74.level75.level76.level77.level78.level79.level80.level81.level82.level83.level84.level85.level86.level87.level88.level89.level90.level91.level92.level93.level94.level95.level96.level97.level98.level99.level100.level101.level102.level103.level104.level105.level106.level107.level108.level109.level110.level111.level112.level113.level114.level115.level116.level117.level118.level119.level120.level121.level122.level123.level124.level125.level126.level127.level128.level129.level130.level131.level132.level133.level134.level135.level136.level137.level138.level139.level140.level141.level142.level143.level144.level145.level146.level147.level148.level149.level150.level151.level152.level153.level154.level155.level156.level157.level158.level159.level160.level161.level162.level163.level164.level165.level166.level167.level168.level169.level170.level171.level172.level173.level174.level175.level176.level177.level178.level179.level180.level181 > > environment: > 1. git pull origin master > 2. mvn clean package -pl server -am -DskipTests > 3. iotdb/server/target/iotdb-server-0.14.0-SNAPSHOT/sbin/start-server.sh > 2022-10-17 172.20.70.44 > > failed info: > !image-2022-10-17-15-32-41-422.png! > > reproduction: > # build the newest source code of master branch, start-server.sh > # start-cli.sh > # show storage group: no such storage group with upstairs value > # create storage group with the value upstairs, failed > # show storage group, it shows the storage group with upstairs value > > 说明： > 使用java原生接口测试，发现该问题。 > 然后使用命令行测试，复现。 > 在0.13.3版本上复测，没有该问题。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4667) The readme doc of cpp-client lacks detailed usage steps
[ https://issues.apache.org/jira/browse/IOTDB-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao reassigned IOTDB-4667: -- Assignee: LyndonYang > The readme doc of cpp-client lacks detailed usage steps > --- > > Key: IOTDB-4667 > URL: https://issues.apache.org/jira/browse/IOTDB-4667 > Project: Apache IoTDB > Issue Type: Improvement > Components: Client/C++ >Reporter: LyndonYang >Assignee: LyndonYang >Priority: Trivial > Original Estimate: 24h > Remaining Estimate: 24h > > The current readme doc of cpp-client has no usage method, update the detailed > usage method to the readme doc -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4668) create storage group failed with 303 but it exists at the result of show storage group
changxue created IOTDB-4668: --- Summary: create storage group failed with 303 but it exists at the result of show storage group Key: IOTDB-4668 URL: https://issues.apache.org/jira/browse/IOTDB-4668 Project: Apache IoTDB Issue Type: Bug Components: Core/Schema Manager Affects Versions: master branch Reporter: changxue Attachments: image-2022-10-17-15-32-41-422.png create storage group failed with 303 but it exists at the result of show storage group 命令行窗口创建下面值的storage group, 创建后报错303（具体日志信息见附件），但是show storage group 可以看到刚刚创建失败的这个storage group. storage group: root.level2.level3.level4.level5.level6.level7.level8.level9.level10.level11.level12.level13.level14.level15.level16.level17.level18.level19.level20.level21.level22.level23.level24.level25.level26.level27.level28.level29.level30.level31.level32.level33.level34.level35.level36.level37.level38.level39.level40.level41.level42.level43.level44.level45.level46.level47.level48.level49.level50.level51.level52.level53.level54.level55.level56.level57.level58.level59.level60.level61.level62.level63.level64.level65.level66.level67.level68.level69.level70.level71.level72.level73.level74.level75.level76.level77.level78.level79.level80.level81.level82.level83.level84.level85.level86.level87.level88.level89.level90.level91.level92.level93.level94.level95.level96.level97.level98.level99.level100.level101.level102.level103.level104.level105.level106.level107.level108.level109.level110.level111.level112.level113.level114.level115.level116.level117.level118.level119.level120.level121.level122.level123.level124.level125.level126.level127.level128.level129.level130.level131.level132.level133.level134.level135.level136.level137.level138.level139.level140.level141.level142.level143.level144.level145.level146.level147.level148.level149.level150.level151.level152.level153.level154.level155.level156.level157.level158.level159.level160.level161.level162.level163.level164.level165.level166.level167.level168.level169.level170.level171.level172.level173.level174.level175.level176.level177.level178.level179.level180.level181 environment: 1. git pull origin master 2. mvn clean package -pl server -am -DskipTests 3. iotdb/server/target/iotdb-server-0.14.0-SNAPSHOT/sbin/start-server.sh 2022-10-17 172.20.70.44 failed info: !image-2022-10-17-15-32-41-422.png! reproduction: # build the newest source code of master branch, start-server.sh # start-cli.sh # show storage group: no such storage group with upstairs value # create storage group with the value upstairs, failed # show storage group, it shows the storage group with upstairs value 说明： 使用java原生接口测试，发现该问题。 然后使用命令行测试，复现。 在0.13.3版本上复测，没有该问题。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4666) Get the devices in batches while compacting
周沛辰 created IOTDB-4666: -- Summary: Get the devices in batches while compacting Key: IOTDB-4666 URL: https://issues.apache.org/jira/browse/IOTDB-4666 Project: Apache IoTDB Issue Type: Improvement Reporter: 周沛辰 Assignee: 周沛辰 At present, the system obtains all devices in the source file at one time when compacting, which may cause OOM problems in the scenario of a large number of devices. To solve this problem, we should read the devices on one index tree node at a time instead of reading all devices from files at one time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4665) ".mods" (all data deleted) files lack a periodic deletion policy
[ https://issues.apache.org/jira/browse/IOTDB-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao reassigned IOTDB-4665: -- Assignee: Liuxuxin (was: Jialin Qiao) > ".mods" (all data deleted) files lack a periodic deletion policy > > > Key: IOTDB-4665 > URL: https://issues.apache.org/jira/browse/IOTDB-4665 > Project: Apache IoTDB > Issue Type: Improvement > Components: mpp-cluster >Reporter: 刘珍 >Assignee: Liuxuxin >Priority: Major > Attachments: image-2022-10-17-14-37-00-495.png, > image-2022-10-17-14-38-08-095.png > > > 已执行delete timeseries root.** > 全部数据和元数据已删除。 > 但是tsfile没有定期清理（删除）策略。 > !image-2022-10-17-14-37-00-495.png! > !image-2022-10-17-14-38-08-095.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4665) ".mods" (all data deleted) files lack a periodic deletion policy
刘珍 created IOTDB-4665: - Summary: ".mods" (all data deleted) files lack a periodic deletion policy Key: IOTDB-4665 URL: https://issues.apache.org/jira/browse/IOTDB-4665 Project: Apache IoTDB Issue Type: Improvement Components: mpp-cluster Reporter: 刘珍 Assignee: Jialin Qiao Attachments: image-2022-10-17-14-37-00-495.png, image-2022-10-17-14-38-08-095.png 已执行delete timeseries root.** 全部数据和元数据已删除。 但是tsfile没有定期清理（删除）策略。 !image-2022-10-17-14-37-00-495.png! !image-2022-10-17-14-38-08-095.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4664) Add UpdatePeer Interface in IConsensus
伊丹翔 created IOTDB-4664: -- Summary: Add UpdatePeer Interface in IConsensus Key: IOTDB-4664 URL: https://issues.apache.org/jira/browse/IOTDB-4664 Project: Apache IoTDB Issue Type: Task Reporter: 伊丹翔 Assignee: 伊丹翔 To support modifying ip:port function, we need to provide updatePeer interface in IConsensus for updating Consensus layer. -- This message was sent by Atlassian Jira (v8.20.10#820010)
