[jira] [Commented] (IOTDB-5279) [Metric] Got a wrong number after restart the cluster

2022-12-29 Thread Jinrui Zhang (Jira) 


[ 
https://issues.apache.org/jira/browse/IOTDB-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653047#comment-17653047
 ] 

Jinrui Zhang commented on IOTDB-5279:
-

Let's paste the PR if it is completed

> [Metric] Got a wrong number after restart the cluster
> -
>
> Key: IOTDB-5279
> URL: https://issues.apache.org/jira/browse/IOTDB-5279
> Project: Apache IoTDB
>  Issue Type: Bug
>  Components: Core/Cluster
>Affects Versions: 1.0.0
>Reporter: Qingxin Feng
>Assignee: Liuxuxin
>Priority: Minor
> Attachments: image-2022-12-26-11-30-04-470.png
>
>
> Reproduce:
> commit version: 1.0.1-SNAPSHOT (Build: a7908ab-dev)
> Steps:
> 1. setup cluster (3C3D 3副本）
> 2. using BM to insert data
> 3. after all test finished,try to restart the cluster
> 4. Check the result in iotdb-metric,like below picture
> http://111.202.73.147:13000/d/TbEVYRw7A/apache-iotdb-datanode-dashboard?orgId=1=1672013871154=1672024516629=datanode=172.20.70.22:9091
> !image-2022-12-26-11-30-04-470.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (IOTDB-5319) The write speed in atoms testing declined after merging commit 5126711d

2022-12-29 Thread Jinrui Zhang (Jira) 


 [ 
https://issues.apache.org/jira/browse/IOTDB-5319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jinrui Zhang reassigned IOTDB-5319:
---

Assignee: Jinrui Zhang

> The write speed in atoms testing declined after merging commit 5126711d
> ---
>
> Key: IOTDB-5319
> URL: https://issues.apache.org/jira/browse/IOTDB-5319
> Project: Apache IoTDB
>  Issue Type: Improvement
>Reporter: Jinrui Zhang
>Assignee: Jinrui Zhang
>Priority: Major
> Attachments: image-2022-12-29-18-37-25-693.png, 
> image-2022-12-29-18-38-45-394.png
>
>
> !image-2022-12-29-18-37-25-693.png|width=701,height=156!
>  
> After merging this commit, the write speed in atoms testing declined. 
>  
> We inferred that this change lead to compaction grabs more CPU/IO resources, 
> which decrease available resources of write/read.
>  
> After we change the parameter `iops_per_min` from 50 to 30, the scenario 
> still exists.
> See this snapshot,
> !image-2022-12-29-18-38-45-394.png|width=541,height=346!
>  
> Let's investigate the details.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (IOTDB-5324) [migrate region] 1rep1C4D ,after the region is migrated successfully， wal cannot be deleted from destDataNode

2022-12-29 Thread Haiming Zhu (Jira) 


[ 
https://issues.apache.org/jira/browse/IOTDB-5324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653008#comment-17653008
 ] 

Haiming Zhu commented on IOTDB-5324:


The safelyDeletedSearchIndex is always Long.MIN_VALUE, which means the region 
status isn't set correctly after being migrated.

!40971672369689_.pic.jpg!

> [migrate region] 1rep1C4D ,after the region is migrated successfully， wal 
> cannot be deleted from destDataNode 
> --
>
> Key: IOTDB-5324
> URL: https://issues.apache.org/jira/browse/IOTDB-5324
> Project: Apache IoTDB
>  Issue Type: Bug
>  Components: mpp-cluster
>Affects Versions: master branch
>Reporter: 刘珍
>Assignee: Gaofei Cao
>Priority: Major
> Attachments: 40971672369689_.pic.jpg, mig.conf, screenshot-1.png, 
> screenshot-2.png
>
>
> m_1229_0fedffd
> 问题描述
> 1副本1C4D集群，写入数据过程中，迁移region（Id=1 from ip4 to ip14）成功，但是目的节点的wal删不掉。
> 1.启动1副本1C4D集群
> config/schema/data 是ratis/ratis/IoT协议
> 2.BM 写入数据（配置见附件）
> 9分钟后，迁移region
> ./sbin/start-cli.sh -h 172.20.70.4 -e "migrate region 1 from 2 to 3"
> 迁移成功，耗时20秒（2022-12-29 18:25:17,621-2022-12-29 18:25:37,676）
> 但是ip14的datanode 
> 的regionId=1的wal删除不掉，导致大小为50GB，一直有限流的WARN日志，BM16个多小时不结束，理论上BM1个多小时就应该执行完成：
> 2022-12-30 10:14:07,669 
> [pool-25-IoTDB-ClientRPC-Processor-59$20221230_021337_10719_3.1.0] WARN  
> o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:243 - write locally failed. 
> TSStatus: TSStatus(code:606, message:Reject write because there are too many 
> requests need to process), message: Reject write because there are too many 
> requests need to process
> 测试环境：私有云3期
> DataNode配置
> MAX_HEAP_SIZE="20G"
> MAX_DIRECT_MEMORY_SIZE="6G"
> dn_max_connection_for_internal_service=300
> ConfigNode配置
> MAX_HEAP_SIZE="20G"
> MAX_DIRECT_MEMORY_SIZE="6G"
> 迁移region前的region信息
>  !screenshot-1.png! 
> 迁移region成功后的region信息
>  !screenshot-2.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (IOTDB-5324) [migrate region] 1rep1C4D ,after the region is migrated successfully， wal cannot be deleted from destDataNode

2022-12-29 Thread Jira 
刘珍 created IOTDB-5324:
-

 Summary: [migrate region] 1rep1C4D ,after the region is migrated 
successfully， wal cannot be deleted from destDataNode 
 Key: IOTDB-5324
 URL: https://issues.apache.org/jira/browse/IOTDB-5324
 Project: Apache IoTDB
  Issue Type: Bug
  Components: mpp-cluster
Affects Versions: master branch
Reporter: 刘珍
Assignee: Gaofei Cao


m_1229_0fedffd
问题描述
1副本1C4D集群，写入数据过程中，迁移region（Id=1 from ip4 to ip14）成功，但是目的节点的wal删不掉。

1.启动1副本1C4D集群
config/schema/data 是ratis/ratis/IoT协议
2.BM 写入数据（配置见附件）
9分钟后，迁移region
./sbin/start-cli.sh -h 172.20.70.4 -e "migrate region 1 from 2 to 3"
迁移成功，耗时20秒（2022-12-29 18:25:17,621-2022-12-29 18:25:37,676）
但是ip14的datanode 
的regionId=1的wal删除不掉，导致大小为50GB，一直有限流的WARN日志，BM16个多小时不结束，理论上BM1个多小时就应该执行完成：
2022-12-30 10:14:07,669 
[pool-25-IoTDB-ClientRPC-Processor-59$20221230_021337_10719_3.1.0] WARN  
o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:243 - write locally failed. 
TSStatus: TSStatus(code:606, message:Reject write because there are too many 
requests need to process), message: Reject write because there are too many 
requests need to process





--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (IOTDB-5323) [metric] Collects the number of open file handles of DataNode/ConfigNode

2022-12-29 Thread Jira 
刘珍 created IOTDB-5323:
-

 Summary: [metric] Collects the number of open file handles of  
DataNode/ConfigNode
 Key: IOTDB-5323
 URL: https://issues.apache.org/jira/browse/IOTDB-5323
 Project: Apache IoTDB
  Issue Type: Improvement
Reporter: 刘珍
Assignee: Hongyin Zhang


metric 需支持 采集ConfigNode/DataNode 进程打开的文件句柄数，以监控是否有文件句柄泄露。
filehandle_num=`ssh ${u_name}@${node} "lsof -p ${pid} | wc -l"`




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (IOTDB-5251) [iotdb-tsfile-viewer]In the Filemanagement interface, the page turning function is abnormal

2022-12-29 Thread long.li (Jira) 


[ 
https://issues.apache.org/jira/browse/IOTDB-5251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652992#comment-17652992
 ] 

long.li commented on IOTDB-5251:


pr：https://github.com/apache/iotdb/pull/7248

> [iotdb-tsfile-viewer]In the Filemanagement interface, the page turning 
> function is abnormal
> ---
>
> Key: IOTDB-5251
> URL: https://issues.apache.org/jira/browse/IOTDB-5251
> Project: Apache IoTDB
>  Issue Type: Bug
>  Components: Core/TsFile, Tools/Others
>Reporter: xiaozhihong
>Assignee: long.li
>Priority: Major
> Attachments: image-2022-12-20-17-20-21-942.png, 
> image-2022-12-20-17-20-57-710.png
>
>
> commit 45fd00cdcb25c9b44f5bc3473bbcca0df7537e0d 
> Run Application.java
> Then visit [http://locallhost:8080|http://locallhost:8080/];
> In FileManagement interface, switch pages and jump directly to the main 
> directory interface.
> !image-2022-12-20-17-20-21-942.png|width=538,height=302!
> !image-2022-12-20-17-20-57-710.png|width=531,height=271!
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (IOTDB-5254) [iotdb-tsfile-viewer]When there is no resource file to load tsfile, the prompt message needs to be optimized

2022-12-29 Thread long.li (Jira) 


[ 
https://issues.apache.org/jira/browse/IOTDB-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652993#comment-17652993
 ] 

long.li commented on IOTDB-5254:


pr：https://github.com/apache/iotdb/pull/7248

> [iotdb-tsfile-viewer]When there is no resource file to load tsfile, the 
> prompt message needs to be optimized
> 
>
> Key: IOTDB-5254
> URL: https://issues.apache.org/jira/browse/IOTDB-5254
> Project: Apache IoTDB
>  Issue Type: Improvement
>  Components: Tools/Others, TsFile
>Reporter: xiaozhihong
>Assignee: long.li
>Priority: Major
> Attachments: image-2022-12-20-18-24-01-006.png
>
>
> Run Application.java
> Then visit [http://locallhost:8080|http://locallhost:8080/];
> !image-2022-12-20-18-24-01-006.png|width=562,height=263!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (IOTDB-5322) Define the RPC interface

2022-12-29 Thread Minghui Liu (Jira) 
Minghui Liu created IOTDB-5322:
--

 Summary: Define the RPC interface
 Key: IOTDB-5322
 URL: https://issues.apache.org/jira/browse/IOTDB-5322
 Project: Apache IoTDB
  Issue Type: Task
Reporter: Minghui Liu
Assignee: Minghui Liu
 Fix For: master branch


doc:

[https://apache-iotdb.feishu.cn/docx/KQ0XdTjnwonROqxYtaecbsQYnoe]

https://apache-iotdb.feishu.cn/docx/SKbQdonpeo4JjLxLcJHcaN0Ln1e

https://apache-iotdb.feishu.cn/docx/PVmXdquUbohAIHxnodkcNuDUnlg



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (IOTDB-5321) [load snapshot]ERROR o.a.i.d.e.s.SnapshotLoader:72 - Exception occurs while load snapshot

2022-12-29 Thread Jira 


 [ 
https://issues.apache.org/jira/browse/IOTDB-5321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

刘珍 reassigned IOTDB-5321:
-

   Sprint: 2022-12-Catalyst
Affects Version/s: master branch
 Assignee: Xinyu Tan

> [load snapshot]ERROR o.a.i.d.e.s.SnapshotLoader:72 - Exception occurs while 
> load snapshot 
> --
>
> Key: IOTDB-5321
> URL: https://issues.apache.org/jira/browse/IOTDB-5321
> Project: Apache IoTDB
>  Issue Type: Bug
>  Components: mpp-cluster
>Affects Versions: master branch
>Reporter: 刘珍
>Assignee: Xinyu Tan
>Priority: Major
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> master_1229_0fedffd
> config/schema/data 分别是ratis/ratis/IoT协议
> 1副本1C4D，BM写入数据过程中，执行migrate region操作，目标节点报错（各节点OS时间不一致）：
> 2022-12-29 18:24:39,186 [pool-20-IoTDB-IoTConsensusRPC-Processor-6] ERROR 
> o.a.i.d.e.s.SnapshotLoader:72 - Exception occurs while load snapshot from 
> /data/iotdb/m_1229_0fedffd/sbin/../data/datanode/consensus/data_region/1_1/snapshot_1_1672309589275
> org.apache.iotdb.db.exception.DataRegionException: data region 
> root.test.g_0[1] is down,{color:#DE350B}* because the time of tsfile 
> /data/iotdb/m_1229_0fedffd/sbin/../data/datanode/data/sequence/root.test.g_0/1/2538/1672309581061-39-0-0.tsfile
>  is larger than system current time*{color}, file time is 1672309581061 while 
> system current time is 1672309479184, please check it.
> at 
> org.apache.iotdb.db.engine.storagegroup.DataRegion.checkTsFileTime(DataRegion.java:732)
> at 
> org.apache.iotdb.db.engine.storagegroup.DataRegion.getAllFiles(DataRegion.java:691)
> at 
> org.apache.iotdb.db.engine.storagegroup.DataRegion.recover(DataRegion.java:429)
> at 
> org.apache.iotdb.db.engine.storagegroup.DataRegion.(DataRegion.java:334)
> at 
> org.apache.iotdb.db.engine.snapshot.SnapshotLoader.loadSnapshot(SnapshotLoader.java:69)
> at 
> org.apache.iotdb.db.engine.snapshot.SnapshotLoader.loadSnapshotWithoutLog(SnapshotLoader.java:134)
> at 
> org.apache.iotdb.db.engine.snapshot.SnapshotLoader.loadSnapshotForStateMachine(SnapshotLoader.java:111)
> at 
> org.apache.iotdb.db.consensus.statemachine.DataRegionStateMachine.loadSnapshot(DataRegionStateMachine.java:137)
> at 
> org.apache.iotdb.consensus.iot.IoTConsensusServerImpl.loadSnapshot(IoTConsensusServerImpl.java:394)
> at 
> org.apache.iotdb.consensus.iot.service.IoTConsensusRPCServiceProcessor.triggerSnapshotLoad(IoTConsensusRPCServiceProcessor.java:288)
> at 
> org.apache.iotdb.consensus.iot.thrift.IoTConsensusIService$AsyncProcessor$triggerSnapshotLoad.start(IoTConsensusIService.java:1349)
> at 
> org.apache.iotdb.consensus.iot.thrift.IoTConsensusIService$AsyncProcessor$triggerSnapshotLoad.start(IoTConsensusIService.java:1292)
> at 
> org.apache.thrift.TBaseAsyncProcessor.process(TBaseAsyncProcessor.java:103)
> at 
> org.apache.thrift.server.AbstractNonblockingServer$AsyncFrameBuffer.invoke(AbstractNonblockingServer.java:603)
> at org.apache.thrift.server.Invocation.run(Invocation.java:18)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> 测试环境：私有云3期
> DataNode配置
> MAX_HEAP_SIZE="20G"
> MAX_DIRECT_MEMORY_SIZE="6G"
> dn_max_connection_for_internal_service=300
> ConfigNode配置
> MAX_HEAP_SIZE="20G"
> MAX_DIRECT_MEMORY_SIZE="6G"
> 运行BM写入数据，配置见附件。
> 10分钟后执行迁移region：
> 迁移之前的region信息
>  !screenshot-1.png! 
> 迁移命令
> ./sbin/start-cli.sh -h 172.20.70.4 -e "migrate region 1 from 2 to 3"
> 迁移成功，迁移后的region信息
>  !screenshot-2.png! 
> 172.20.70.14节点datanode 报错。



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (IOTDB-5321) [load snapshot]ERROR o.a.i.d.e.s.SnapshotLoader:72 - Exception occurs while load snapshot

2022-12-29 Thread Jira 
刘珍 created IOTDB-5321:
-

 Summary: [load snapshot]ERROR o.a.i.d.e.s.SnapshotLoader:72 - 
Exception occurs while load snapshot 
 Key: IOTDB-5321
 URL: https://issues.apache.org/jira/browse/IOTDB-5321
 Project: Apache IoTDB
  Issue Type: Bug
  Components: mpp-cluster
Reporter: 刘珍


master_1229_0fedffd
config/schema/data 分别是ratis/ratis/IoT协议
1副本1C4D，BM写入数据过程中，执行migrate region操作，目标节点报错（各节点OS时间不一致）：
2022-12-29 18:24:39,186 [pool-20-IoTDB-IoTConsensusRPC-Processor-6] ERROR 
o.a.i.d.e.s.SnapshotLoader:72 - Exception occurs while load snapshot from 
/data/iotdb/m_1229_0fedffd/sbin/../data/datanode/consensus/data_region/1_1/snapshot_1_1672309589275
org.apache.iotdb.db.exception.DataRegionException: data region root.test.g_0[1] 
is down,{color:#DE350B}* because the time of tsfile 
/data/iotdb/m_1229_0fedffd/sbin/../data/datanode/data/sequence/root.test.g_0/1/2538/1672309581061-39-0-0.tsfile
 is larger than system current time*{color}, file time is 1672309581061 while 
system current time is 1672309479184, please check it.
at 
org.apache.iotdb.db.engine.storagegroup.DataRegion.checkTsFileTime(DataRegion.java:732)
at 
org.apache.iotdb.db.engine.storagegroup.DataRegion.getAllFiles(DataRegion.java:691)
at 
org.apache.iotdb.db.engine.storagegroup.DataRegion.recover(DataRegion.java:429)
at 
org.apache.iotdb.db.engine.storagegroup.DataRegion.(DataRegion.java:334)
at 
org.apache.iotdb.db.engine.snapshot.SnapshotLoader.loadSnapshot(SnapshotLoader.java:69)
at 
org.apache.iotdb.db.engine.snapshot.SnapshotLoader.loadSnapshotWithoutLog(SnapshotLoader.java:134)
at 
org.apache.iotdb.db.engine.snapshot.SnapshotLoader.loadSnapshotForStateMachine(SnapshotLoader.java:111)
at 
org.apache.iotdb.db.consensus.statemachine.DataRegionStateMachine.loadSnapshot(DataRegionStateMachine.java:137)
at 
org.apache.iotdb.consensus.iot.IoTConsensusServerImpl.loadSnapshot(IoTConsensusServerImpl.java:394)
at 
org.apache.iotdb.consensus.iot.service.IoTConsensusRPCServiceProcessor.triggerSnapshotLoad(IoTConsensusRPCServiceProcessor.java:288)
at 
org.apache.iotdb.consensus.iot.thrift.IoTConsensusIService$AsyncProcessor$triggerSnapshotLoad.start(IoTConsensusIService.java:1349)
at 
org.apache.iotdb.consensus.iot.thrift.IoTConsensusIService$AsyncProcessor$triggerSnapshotLoad.start(IoTConsensusIService.java:1292)
at 
org.apache.thrift.TBaseAsyncProcessor.process(TBaseAsyncProcessor.java:103)
at 
org.apache.thrift.server.AbstractNonblockingServer$AsyncFrameBuffer.invoke(AbstractNonblockingServer.java:603)
at org.apache.thrift.server.Invocation.run(Invocation.java:18)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

测试环境，私有云3期




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (IOTDB-5320) Add executeAggregationQuery interface in session API

2022-12-29 Thread Minghui Liu (Jira) 
Minghui Liu created IOTDB-5320:
--

 Summary: Add executeAggregationQuery interface in session API
 Key: IOTDB-5320
 URL: https://issues.apache.org/jira/browse/IOTDB-5320
 Project: Apache IoTDB
  Issue Type: Task
Reporter: Minghui Liu
Assignee: Minghui Liu
 Fix For: master branch


Add an efficient interface for aggregation query that can save time-consuming 
SQL parsing.
 * Support specified query time range: The specified query time range is a 
left-closed right-open interval, including the start time but not the end time.
 * Support GROUP BY TIME.

{code:java}
SessionDataSet executeAggregationQuery(List paths, List 
aggregations);

SessionDataSet executeAggregationQuery(
List paths, List aggregations, long startTime, long 
endTime);

SessionDataSet executeAggregationQuery(
List paths,
List aggregations,
long startTime,
long endTime,
long interval);

SessionDataSet executeAggregationQuery(
List paths,
List aggregations,
long startTime,
long endTime,
long interval,
long slidingStep);{code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (IOTDB-5319) The write speed in atoms testing declined after merging commit 5126711d

2022-12-29 Thread Jinrui Zhang (Jira) 
Jinrui Zhang created IOTDB-5319:
---

 Summary: The write speed in atoms testing declined after merging 
commit 5126711d
 Key: IOTDB-5319
 URL: https://issues.apache.org/jira/browse/IOTDB-5319
 Project: Apache IoTDB
  Issue Type: Improvement
Reporter: Jinrui Zhang
 Attachments: image-2022-12-29-18-37-25-693.png

!image-2022-12-29-18-37-25-693.png|width=701,height=156!

 

After merging this commit, the write speed in atoms testing declined. 

 

We inferred that this change lead to compaction grabs more CPU/IO resources, 
which decrease available resources of write/read.

 

After we change the parameter `iops_per_min` from 50 to 30, the scenario still 
exists.

See this snapshot,

!image-2022-12-29-18-35-42-134.png|width=521,height=333!

 

Let's investigate the details.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [iotdb-client-go] HTHou merged pull request #70: [To rel/0.13] Fix some bugs about time zone

2022-12-29 Thread GitBox 


HTHou merged PR #70:
URL: https://github.com/apache/iotdb-client-go/pull/70


-- 
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-5318) java native API should support the way of docker deployment

2022-12-29 Thread changxue (Jira) 


[ 
https://issues.apache.org/jira/browse/IOTDB-5318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652790#comment-17652790
 ] 

changxue commented on IOTDB-5318:
-

Set the priority to "Critical" , because this problem make the docker 
deployment useless and this bug is from customer.

> java native API should support the way of docker deployment
> ---
>
> Key: IOTDB-5318
> URL: https://issues.apache.org/jira/browse/IOTDB-5318
> Project: Apache IoTDB
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: changxue
>Assignee: Haonan Hou
>Priority: Critical
> Attachments: image-2022-12-29-17-47-13-842.png
>
>
> java native API should support the way of docker deployment
> environment:
> docker 1c1d
> reproduction:
> 1. new iotdb-service with:
> {code}
> docker network create --driver=bridge --subnet=172.18.0.0/16 
> --gateway=172.18.0.1 iotdb
> docker run -d --name iotdb-service \
>   --hostname iotdb-service \
>   --network iotdb \
>   --ip 172.18.0.6 \
>   -p 16667:6667 \
>   -e cn_internal_address=iotdb-service \
>   -e cn_target_config_node_list=iotdb-service:22277 \
>   -e dn_rpc_address=iotdb-service \
>   -e dn_internal_address=iotdb-service \
>   -e dn_target_config_node_list=iotdb-service:22277 \
>   apache/iotdb:1.0.0-standalone
> {code}
> 2. run the java source code below:
> {code}
> Session session = new Session.Builder()
> .host("172.20.70.44")
> .port(16667)
> .username("root")
> .password("root")
> .build();
> session.open(false);
> session.setFetchSize(1);
> // 1. confirm the connection is OK
> try (SessionDataSet dataSet =
>  session.executeQueryStatement("show cluster", 20)) {
> System.out.println(dataSet.getColumnNames());
> dataSet.setFetchSize(1024); // default is 1
> while (dataSet.hasNext()) {
> System.out.println(dataSet.next());
> }
> }
> // 2. insert 
> List measuraments = new ArrayList<>();
> List tsDataTypes = new ArrayList<>();
> List content = new ArrayList<>();
> String targetDevice = "root.ln.alerting";
> measuraments.add("table_name");
> measuraments.add("alert_content");
> tsDataTypes.add(TSDataType.TEXT);
> tsDataTypes.add(TSDataType.TEXT);
> content.add("root.ln.wf01.wt01");
> content.add("CRITICAL test value greater then 100");
> session.insertAlignedRecord(targetDevice, new Date().getTime(), 
> measuraments, tsDataTypes, content);
> {code}
> actual result:
>  !image-2022-12-29-17-47-13-842.png! 
> 问题：
> 1. step 1 : show cluster 证明，docker 部署的连接是没有问题的。
> 2. step 2: insert 会缓存并重定向，结果重定向的地址是docker内网地址，导致连接不上



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (IOTDB-5318) java native API should support the way of docker deployment

2022-12-29 Thread changxue (Jira) 
changxue created IOTDB-5318:
---

 Summary: java native API should support the way of docker 
deployment
 Key: IOTDB-5318
 URL: https://issues.apache.org/jira/browse/IOTDB-5318
 Project: Apache IoTDB
  Issue Type: Bug
Affects Versions: 1.0.0
Reporter: changxue
Assignee: Haonan Hou
 Attachments: image-2022-12-29-17-47-13-842.png

java native API should support the way of docker deployment

environment:
docker 1c1d

reproduction:
1. new iotdb-service with:
{code}
docker network create --driver=bridge --subnet=172.18.0.0/16 
--gateway=172.18.0.1 iotdb
docker run -d --name iotdb-service \
  --hostname iotdb-service \
  --network iotdb \
  --ip 172.18.0.6 \
  -p 16667:6667 \
  -e cn_internal_address=iotdb-service \
  -e cn_target_config_node_list=iotdb-service:22277 \
  -e dn_rpc_address=iotdb-service \
  -e dn_internal_address=iotdb-service \
  -e dn_target_config_node_list=iotdb-service:22277 \
  apache/iotdb:1.0.0-standalone
{code}
2. run the java source code below:
{code}
Session session = new Session.Builder()
.host("172.20.70.44")
.port(16667)
.username("root")
.password("root")
.build();
session.open(false);
session.setFetchSize(1);

// 1. confirm the connection is OK
try (SessionDataSet dataSet =
 session.executeQueryStatement("show cluster", 20)) {
System.out.println(dataSet.getColumnNames());
dataSet.setFetchSize(1024); // default is 1
while (dataSet.hasNext()) {
System.out.println(dataSet.next());
}
}

// 2. insert 
List measuraments = new ArrayList<>();
List tsDataTypes = new ArrayList<>();
List content = new ArrayList<>();
String targetDevice = "root.ln.alerting";
measuraments.add("table_name");
measuraments.add("alert_content");
tsDataTypes.add(TSDataType.TEXT);
tsDataTypes.add(TSDataType.TEXT);

content.add("root.ln.wf01.wt01");
content.add("CRITICAL test value greater then 100");
session.insertAlignedRecord(targetDevice, new Date().getTime(), 
measuraments, tsDataTypes, content);
{code}

actual result:
 !image-2022-12-29-17-47-13-842.png! 

问题：
1. step 1 : show cluster 证明，docker 部署的连接是没有问题的。
2. step 2: insert 会缓存并重定向，结果重定向的地址是docker内网地址，导致连接不上





--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[GitHub] [iotdb-client-go] citrusreticulata opened a new pull request, #70: [To rel/0.13] Fix gettimezone to 0.13

2022-12-29 Thread GitBox 


citrusreticulata opened a new pull request, #70:
URL: https://github.com/apache/iotdb-client-go/pull/70

   Fix some bugs about time zone.
   This PR is for `rel/0.13`, relative PR for `main`:
   1. https://github.com/apache/iotdb-client-go/pull/68 
   2. https://github.com/apache/iotdb-client-go/pull/69
   
   ### summary:
    cleanup invalid codes from session
   cleanup invalid codes from session
   
    set DefaultTimeZone if GetTimeZone returns an error
   `func (s *Session) GetTimeZone() (string, error)`:
   `return "", err` --> `return DefaultTimeZone, err`
   
   If the error is not handled, the TimeZone in the config may be directly set 
to an empty string value without any check.
   In previous file 'session_example.go', the time zone was printed only when 
there was an error. It should be a design error
   
   
   


-- 
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-5317) [migrate region] 3rep1C4D ,1rep of the migrated region is Running, 1rep is Unkown, and 1rep is ReadOnly， the migration fails

2022-12-29 Thread Jira 
刘珍 created IOTDB-5317:
-

 Summary: [migrate region] 3rep1C4D ,1rep of the migrated region is 
Running, 1rep is Unkown, and 1rep is ReadOnly， the migration fails
 Key: IOTDB-5317
 URL: https://issues.apache.org/jira/browse/IOTDB-5317
 Project: Apache IoTDB
  Issue Type: Bug
  Components: mpp-cluster
Affects Versions: master branch
Reporter: 刘珍
Assignee: Gaofei Cao
 Attachments: image-2022-12-29-17-16-00-294.png, 
image-2022-12-29-17-17-26-853.png

m_1229_15c9231
3副本1C4D，迁移region的Id=1 ，这个region的信息是1个副本是Running，1个是Unkown，1个是ReadOnly，迁移失败。
1.迁移开始前，查看region信息
 !image-2022-12-29-17-16-00-294.png! 
2.迁移命令
./sbin/start-cli.sh -h 172.20.70.4 -e "migrate region 1 from 1 to 3"
命令返回成功
3.实际迁移失败，ConfigNode日志报错
 !image-2022-12-29-17-17-26-853.png! 

测试环境：私有云3期
COMMON配置
schema_replication_factor=3
data_replication_factor=3
DataNode配置
MAX_HEAP_SIZE="20G"
MAX_DIRECT_MEMORY_SIZE="6G"
dn_max_connection_for_internal_service=300
ConfigNode配置
MAX_HEAP_SIZE="20G"
MAX_DIRECT_MEMORY_SIZE="6G"

运行BM写入数据，全部写入成功。
再执行stop datanode和set system to readonly on local的操作。




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Assigned] (IOTDB-5316) Session.setFetchSize is not used in the following fetch requests

2022-12-29 Thread Lei Rui (Jira) 


 [ 
https://issues.apache.org/jira/browse/IOTDB-5316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lei Rui reassigned IOTDB-5316:
--

Assignee: Lei Rui

> Session.setFetchSize is not used in the following fetch requests
> 
>
> Key: IOTDB-5316
> URL: https://issues.apache.org/jira/browse/IOTDB-5316
> Project: Apache IoTDB
>  Issue Type: Bug
>Reporter: Lei Rui
>Assignee: Lei Rui
>Priority: Major
>
> Session.setFetchSize only applies for the first query execution request and 
> the following fetch request uses the default fetch size 5000.
> The reason is that the construction method of SessionDataSet in 
> `SessionConnection.executeQueryStatement` uses 
> `SessionConfig.DEFAULT_FETCH_SIZE` instead of the actual `session.fetchSize`.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (IOTDB-5316) Session.setFetchSize is not used in the following fetch requests

2022-12-29 Thread Lei Rui (Jira) 
Lei Rui created IOTDB-5316:
--

 Summary: Session.setFetchSize is not used in the following fetch 
requests
 Key: IOTDB-5316
 URL: https://issues.apache.org/jira/browse/IOTDB-5316
 Project: Apache IoTDB
  Issue Type: Bug
Reporter: Lei Rui


Session.setFetchSize only applies for the first query execution request and the 
following fetch request uses the default fetch size 5000.

The reason is that the construction method of SessionDataSet in 
`SessionConnection.executeQueryStatement` uses 
`SessionConfig.DEFAULT_FETCH_SIZE` instead of the actual `session.fetchSize`.

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (IOTDB-5217) [CQ]General user query CQ is abnormal

2022-12-29 Thread xiaozhihong (Jira) 


[ 
https://issues.apache.org/jira/browse/IOTDB-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652771#comment-17652771
 ] 

xiaozhihong commented on IOTDB-5217:


master branch
commit 08f924c707abae0b10491363b3d8e040864f5b2e

I verified.

> [CQ]General user query CQ is abnormal
> -
>
> Key: IOTDB-5217
> URL: https://issues.apache.org/jira/browse/IOTDB-5217
> Project: Apache IoTDB
>  Issue Type: Bug
>  Components: mpp-cluster
>Affects Versions: 1.0.0, 1.0.1
>Reporter: xiaozhihong
>Assignee: Yuan Tian
>Priority: Major
> Attachments: image-2022-12-14-20-31-20-088.png
>
>
> commit 4dcd255ae86485f4d3e019ab622e5af42d324340
> Default conf file, start 1C1D.
> Enter CLi, Execute sql;
> user : root
> {code:java}
> IoTDB> CREATE CONTINUOUS QUERY cq1 RESAMPLE EVERY 20s BOUNDARY 
> 2022-01-14T23:00:00.000+08:00  RANGE 20s BEGIN SELECT avg(temperature) INTO 
> root.ln_cq.${2}(temperature_avg) FROM root.ln.*.* GROUP BY time(10s), level=2 
> END;
> Msg: The statement is executed successfully.
> IoTDB> CREATE USER user01 'pass1234';
> > GRANT USER user01 PRIVILEGES READ_TIMESERIES on root.**;
> Msg: The statement is executed successfully.
> Msg: The statement is executed successfully.
> IoTDB> SHOW CONTINUOUS QUERIES;
> ++-+--+
> |CQId|                                                                        
>                                                                               
>                                                           Query| State|
> ++-+--+
> | cq1|CREATE CONTINUOUS QUERY cq1 RESAMPLE EVERY 20s BOUNDARY 
> 2022-01-14T23:00:00.000+08:00  RANGE 20s BEGIN SELECT avg(temperature) INTO 
> root.ln_cq.${2}(temperature_avg) FROM root.ln.*.* GROUP BY time(10s), level=2 
> END|ACTIVE|
> ++-+--+
> Total line number = 1
> It costs 0.003s
> IoTDB> show cqs;
> ++-+--+
> |CQId|                                                                        
>                                                                               
>                                                           Query| State|
> ++-+--+
> | cq1|CREATE CONTINUOUS QUERY cq1 RESAMPLE EVERY 20s BOUNDARY 
> 2022-01-14T23:00:00.000+08:00  RANGE 20s BEGIN SELECT avg(temperature) INTO 
> root.ln_cq.${2}(temperature_avg) FROM root.ln.*.* GROUP BY time(10s), level=2 
> END|ACTIVE|
> ++-+--+
> Total line number = 1
> It costs 0.003s
>  {code}
> user : user01
> {code:java}
> [xzh@i-ipza09nr apache-iotdb-1.0.1-SNAPSHOT-all-bin]$ ./sbin/start-cli.sh -u 
> user01 -pw pass1234
> -
> Starting IoTDB Cli
> -
>  _       _  __   __    
> |_   _|     |  _   _  ||_   _ `.|_   _ \   
>   | |   .--.|_/ | | \_|  | | `. \ | |_) |  
>   | | / .'`\ \  | |      | |  | | |  __'.  
>  _| |_| \__. | _| |_    _| |_.' /_| |__) | 
> |_|'.__.' |_|  |__.'|___/  version 1.0.1-SNAPSHOT (Build: 
> 4dcd255) Successfully login at 127.0.0.1:6667 IoTDB> CREATE CONTINUOUS QUERY 
> cq4 RESAMPLE EVERY 20s BOUNDARY 2022-01-14T23:00:00.000+08:00 RANGE 20s BEGIN 
> SELECT avg(temperature) INTO root.ln_cq.${2}(temperature_avg) FROM root.ln.*.*
>  GROUP BY time(10s), level=2 END;
> Msg: 803: No permissions for this operation, please add privilege 
> CREATE_CONTINUOUS_QUERY
> IoTDB> SHOW CONTINUOUS QUERIES;
> Msg: 301: [EXECUTE_STATEMENT_ERROR(301)] Exception occurred: checkAuthority 
> failed. Index -1 out of bounds for length 34
> IoTDB> show cqs;
> Msg: 301: [EXECUTE_STATEMENT_ERROR(301)] Exception

[jira] [Assigned] (IOTDB-5315) There should be an access to active and deactive a template in java native API

2022-12-29 Thread Haonan Hou (Jira) 


 [ 
https://issues.apache.org/jira/browse/IOTDB-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Haonan Hou reassigned IOTDB-5315:
-

Assignee: Yukun Zhou  (was: Haonan Hou)

> There should be an access to active and deactive a template in java native 
> API 
> ---
>
> Key: IOTDB-5315
> URL: https://issues.apache.org/jira/browse/IOTDB-5315
> Project: Apache IoTDB
>  Issue Type: New Feature
>Reporter: changxue
>Assignee: Yukun Zhou
>Priority: Major
>
> There should be an access to active and deactive a template in java native 
> API 
> 问题：
> template 的生命周期：“创建”、“挂载”、“激活”、“解除”、“卸载”、和“删除”
> java 原生接口(session)中没有“激活”(active)、“解除”(deactive)两种状态的接口函数
> 应该有。



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (IOTDB-5315) There should be an access to active and deactive a template in java native API

2022-12-29 Thread changxue (Jira) 
changxue created IOTDB-5315:
---

 Summary: There should be an access to active and deactive a 
template in java native API 
 Key: IOTDB-5315
 URL: https://issues.apache.org/jira/browse/IOTDB-5315
 Project: Apache IoTDB
  Issue Type: New Feature
Reporter: changxue
Assignee: Haonan Hou


There should be an access to active and deactive a template in java native API 
问题：
template 的生命周期：“创建”、“挂载”、“激活”、“解除”、“卸载”、和“删除”
java 原生接口(session)中没有“激活”(active)、“解除”(deactive)两种状态的接口函数
应该有。




--
This message was sent by Atlassian Jira
(v8.20.10#820010)