[jira] [Created] (IOTDB-4555) [Grafana]The Metrics template displayed in grafana does not match the actual

2022-09-28 Thread xiaozhihong (Jira)
xiaozhihong created IOTDB-4555:
--

 Summary: [Grafana]The Metrics template displayed in grafana does 
not match the actual
 Key: IOTDB-4555
 URL: https://issues.apache.org/jira/browse/IOTDB-4555
 Project: Apache IoTDB
  Issue Type: Bug
  Components: Connectors/Grafana
Affects Versions: 0.13.3
Reporter: xiaozhihong
Assignee: 张洪胤
 Attachments: image-2022-09-29-11-30-39-230.png, 
image-2022-09-29-11-31-33-486.png, image-2022-09-29-12-36-24-267.png

Turn on the monitoring mode, perform read and write operations on IOTDB, and 
finally display in grafana inconsistent with the actual.
For example:
The number of file

!image-2022-09-29-12-36-24-267.png|width=548,height=76!

!image-2022-09-29-11-31-33-486.png|width=551,height=128!

 



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


[GitHub] [iotdb-bin-resources] HTHou merged pull request #41: [IOTDB-2623] iotdb grafana plugin

2022-09-28 Thread GitBox


HTHou merged PR #41:
URL: https://github.com/apache/iotdb-bin-resources/pull/41


-- 
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] CloudWise-Lukemiao opened a new pull request, #41: [IOTDB-2623] iotdb grafana plugin

2022-09-28 Thread GitBox


CloudWise-Lukemiao opened a new pull request, #41:
URL: https://github.com/apache/iotdb-bin-resources/pull/41

   [IOTDB-2623] iotdb grafana plugin


-- 
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-4550) Add nodeId in class Peer

2022-09-28 Thread Jira


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

伊丹翔 commented on IOTDB-4550:


Peer 结构和接口文档:https://apacheiotdb.feishu.cn/docx/doxcn8FueTE5MKKJAY3Pn79m3vf

> Add nodeId in class Peer
> 
>
> Key: IOTDB-4550
> URL: https://issues.apache.org/jira/browse/IOTDB-4550
> Project: Apache IoTDB
>  Issue Type: Improvement
>Reporter: 伊丹翔
>Assignee: 伊丹翔
>Priority: Major
>
> 共识组编号+节点编号 作为 Peer 的唯一标识,方便修改 Peer 持有的TEndPoint



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


[jira] [Commented] (IOTDB-4402) Avoid multiple IoTDB processes accessing same data dir

2022-09-28 Thread yanze chen (Jira)


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

yanze chen commented on IOTDB-4402:
---

https://stackoverflow.com/questions/35842/how-can-a-java-program-get-its-own-process-id

> Avoid multiple IoTDB processes accessing same data dir 
> ---
>
> Key: IOTDB-4402
> URL: https://issues.apache.org/jira/browse/IOTDB-4402
> Project: Apache IoTDB
>  Issue Type: Improvement
>Reporter: Haonan Hou
>Assignee: yanze chen
>Priority: Major
>
> If multiple IoTDB processes operate the same data dirs, the data file may be 
> damaged. Need a method to protect the data dir.



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


[jira] [Assigned] (IOTDB-4402) Avoid multiple IoTDB processes accessing same data dir

2022-09-28 Thread Haonan Hou (Jira)


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

Haonan Hou reassigned IOTDB-4402:
-

Assignee: yanze chen

> Avoid multiple IoTDB processes accessing same data dir 
> ---
>
> Key: IOTDB-4402
> URL: https://issues.apache.org/jira/browse/IOTDB-4402
> Project: Apache IoTDB
>  Issue Type: Improvement
>Reporter: Haonan Hou
>Assignee: yanze chen
>Priority: Major
>
> If multiple IoTDB processes operate the same data dirs, the data file may be 
> damaged. Need a method to protect the data dir.



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


[jira] [Created] (IOTDB-4554) Start compaction only when IoTDB is fully recovered

2022-09-28 Thread Jialin Qiao (Jira)
Jialin Qiao created IOTDB-4554:
--

 Summary: Start compaction only when IoTDB is fully recovered
 Key: IOTDB-4554
 URL: https://issues.apache.org/jira/browse/IOTDB-4554
 Project: Apache IoTDB
  Issue Type: Improvement
Reporter: Jialin Qiao
Assignee: Liuxuxin


Accelerate restarting



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


[jira] [Created] (IOTDB-4553) [remove datanode ] SchemaRegion migration failed

2022-09-28 Thread Jira
刘珍 created IOTDB-4553:
-

 Summary: [remove datanode ] SchemaRegion migration failed
 Key: IOTDB-4553
 URL: https://issues.apache.org/jira/browse/IOTDB-4553
 Project: Apache IoTDB
  Issue Type: Bug
  Components: mpp-cluster
Affects Versions: 0.14.0-SNAPSHOT
Reporter: 刘珍
Assignee: Song Ziyang
 Attachments: image-2022-09-28-18-03-13-622.png

master_0928_e5cc456
SchemaRegion : ratis
DataRegion : multiLeader
均为3副本,先启动3C3D,bm写入数据,增加1个datanode ip40,缩容ip39,
ip39 缩容成功后,SchemaRegion 迁移失败
 !image-2022-09-28-18-03-13-622.png! 

ip40的datanode error 
2022-09-28 17:37:55,449 [pool-21-IoTDB-DataNodeInternalRPC-Processor-3] ERROR 
o.a.i.d.s.t.i.DataNodeInternalRPCServiceImpl:1002 - CreateNewRegionPeer error, 
peers: [Peer{groupId=SchemaRegion[0], endpoint=TEndPoint(ip:172.20.70.37, 
port:50010)}, Peer{groupId=SchemaRegion[0], endpoint=TEndPoint(ip:172.20.70.38, 
port:50010)}, Peer{groupId=SchemaRegion[0], endpoint=TEndPoint(ip:172.20.70.39, 
port:50010)}, Peer{groupId=SchemaRegion[0], endpoint=TEndPoint(ip:172.20.70.40, 
port:50010)}], regionId: SchemaRegion[0], errorMessage
org.apache.iotdb.consensus.exception.RatisRequestFailedException: Ratis request 
failed
at 
org.apache.iotdb.consensus.ratis.RatisConsensus.createPeer(RatisConsensus.java:332)
at 
org.apache.iotdb.db.service.thrift.impl.DataNodeInternalRPCServiceImpl.createNewRegionPeer(DataNodeInternalRPCServiceImpl.java:999)
at 
org.apache.iotdb.db.service.thrift.impl.DataNodeInternalRPCServiceImpl.createNewRegionPeer(DataNodeInternalRPCServiceImpl.java:838)
at 
org.apache.iotdb.mpp.rpc.thrift.IDataNodeRPCService$Processor$createNewRegionPeer.getResult(IDataNodeRPCService.java:3237)
at 
org.apache.iotdb.mpp.rpc.thrift.IDataNodeRPCService$Processor$createNewRegionPeer.getResult(IDataNodeRPCService.java:3217)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:38)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:38)
at 
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:248)
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)
Caused by: java.io.IOException: 
org.apache.ratis.thirdparty.io.grpc.StatusRuntimeException: UNAVAILABLE: io 
exception
at org.apache.ratis.grpc.GrpcUtil.unwrapException(GrpcUtil.java:92)
at 
org.apache.ratis.grpc.client.GrpcClientProtocolClient.blockingCall(GrpcClientProtocolClient.java:234)
at 
org.apache.ratis.grpc.client.GrpcClientProtocolClient.groupAdd(GrpcClientProtocolClient.java:181)
at 
org.apache.ratis.grpc.client.GrpcClientRpc.sendRequest(GrpcClientRpc.java:98)
at 
org.apache.ratis.client.impl.BlockingImpl.sendRequest(BlockingImpl.java:132)
at 
org.apache.ratis.client.impl.BlockingImpl.sendRequestWithRetry(BlockingImpl.java:98)
at 
org.apache.ratis.client.impl.GroupManagementImpl.add(GroupManagementImpl.java:51)
at 
org.apache.iotdb.consensus.ratis.RatisConsensus.createPeer(RatisConsensus.java:327)
... 10 common frames omitted
Caused by: org.apache.ratis.thirdparty.io.grpc.StatusRuntimeException: 
UNAVAILABLE: io exception
at 
org.apache.ratis.thirdparty.io.grpc.stub.ClientCalls.toStatusRuntimeException(ClientCalls.java:262)
at 
org.apache.ratis.thirdparty.io.grpc.stub.ClientCalls.getUnchecked(ClientCalls.java:243)
at 
org.apache.ratis.thirdparty.io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:156)
at 
org.apache.ratis.proto.grpc.AdminProtocolServiceGrpc$AdminProtocolServiceBlockingStub.groupManagement(AdminProtocolServiceGrpc.java:507)
at 
org.apache.ratis.grpc.client.GrpcClientProtocolClient.lambda$groupAdd$5(GrpcClientProtocolClient.java:183)
at 
org.apache.ratis.grpc.client.GrpcClientProtocolClient.blockingCall(GrpcClientProtocolClient.java:232)
... 16 common frames omitted
Caused by: 
org.apache.ratis.thirdparty.io.netty.channel.AbstractChannel$AnnotatedConnectException:
 finishConnect(..) failed: Connection refused: /172.20.70.40:50010
Caused by: java.net.ConnectException: finishConnect(..) failed: Connection 
refused
at 
org.apache.ratis.thirdparty.io.netty.channel.unix.Errors.newConnectException0(Errors.java:155)
at 
org.apache.ratis.thirdparty.io.netty.channel.unix.Errors.handleConnectErrno(Errors.java:128)
at 
org.apache.ratis.thirdparty.io.netty.channel.unix.Socket.finishConnect(Socket.java:320)
at 
org.apache.ratis.thirdparty.io.netty.channel.epoll.AbstractEpollChannel$AbstractEpollUnsafe.doFinishConnect(AbstractEpollChannel.java:710)
at 

[jira] [Created] (IOTDB-4552) NPE in SourceHandle

2022-09-28 Thread Yuan Tian (Jira)
Yuan Tian created IOTDB-4552:


 Summary: NPE in SourceHandle
 Key: IOTDB-4552
 URL: https://issues.apache.org/jira/browse/IOTDB-4552
 Project: Apache IoTDB
  Issue Type: Bug
Reporter: Yuan Tian
Assignee: Yuan Tian


While upstream FI failed, stateTracker may detect its state and then abort the 
SourceHandle in downstream, however meanwhile there may still exist GetTsBlock 
request in thread pool, it will fail because SinkHandle in upstream is already 
released. Then the GetTsBlock request will rertry 3 times and when it reach max 
retry times, it will try to release memory that reserved by itself, but this 
part of memory has already been released while this SourceHandle being aborted 
before.



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


[jira] [Created] (IOTDB-4551) NPE while fetching schema

2022-09-28 Thread Yuan Tian (Jira)
Yuan Tian created IOTDB-4551:


 Summary: NPE while fetching schema
 Key: IOTDB-4551
 URL: https://issues.apache.org/jira/browse/IOTDB-4551
 Project: Apache IoTDB
  Issue Type: Bug
Reporter: Yuan Tian
Assignee: Yukun Zhou






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


[jira] [Created] (IOTDB-4550) Add nodeId in class Peer

2022-09-28 Thread Jira
伊丹翔 created IOTDB-4550:
--

 Summary: Add nodeId in class Peer
 Key: IOTDB-4550
 URL: https://issues.apache.org/jira/browse/IOTDB-4550
 Project: Apache IoTDB
  Issue Type: Improvement
Reporter: 伊丹翔
Assignee: 伊丹翔


共识组编号+节点编号 作为 Peer 的唯一标识,方便修改 Peer 持有的TEndPoint



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


[jira] [Created] (IOTDB-4549) ConfigNode snapshot test

2022-09-28 Thread Yongzao Dan (Jira)
Yongzao Dan created IOTDB-4549:
--

 Summary: ConfigNode snapshot test
 Key: IOTDB-4549
 URL: https://issues.apache.org/jira/browse/IOTDB-4549
 Project: Apache IoTDB
  Issue Type: Improvement
Reporter: Yongzao Dan
Assignee: Yongzao Dan
 Fix For: 0.14.0






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


[jira] [Created] (IOTDB-4548) Add a status code in TGetDataBlockResponse to indicate no sourceHandle and so on exception

2022-09-28 Thread Yuan Tian (Jira)
Yuan Tian created IOTDB-4548:


 Summary: Add a status code in TGetDataBlockResponse to indicate no 
sourceHandle and so on exception 
 Key: IOTDB-4548
 URL: https://issues.apache.org/jira/browse/IOTDB-4548
 Project: Apache IoTDB
  Issue Type: Improvement
Reporter: Yuan Tian


Currently, iotdb will print too much error stack in log_error while we throw 
TException.



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


[jira] [Created] (IOTDB-4547) [cluster]Import CSV file to report 400

2022-09-28 Thread xiaozhihong (Jira)
xiaozhihong created IOTDB-4547:
--

 Summary: [cluster]Import CSV file to report 400
 Key: IOTDB-4547
 URL: https://issues.apache.org/jira/browse/IOTDB-4547
 Project: Apache IoTDB
  Issue Type: Bug
  Components: csv, mpp-cluster
Affects Versions: 0.14.0-SNAPSHOT
Reporter: xiaozhihong
Assignee: Quan Siyi
 Attachments: log_all.log, no_datatype.csv

commit e5cc456a6732ddee0e8129f29a85c7f3d30ccddd

Start 3C3D, Import a CSV file that does not contain data types, and then report 
a 400 error.
{code:java}
[xzh@i-kg9g1xqu tools]$ ./import-csv.sh -h 172.20.31.3 -p 6667 -u root -pw root 
-f /home/xzh/data/xzh/csv-data/no_datatype.csv
--
Starting IoTDB Client Import Script
--
Meet error when insert csv because 400: [EXECUTE_STATEMENT_ERROR(400)] 
Exception occurred: insertRecords failed. Index 0 out of bounds for length 0
Import completely! {code}

csv file please see attachment



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