[GitHub] [iotdb-bin-resources] CloudWise-Lukemiao merged pull request #57: grafana_plugin/apache-iotdb-datasource.zip & grafana_plugin/dockerfile.zip for community tests

2023-05-19 Thread via GitHub


CloudWise-Lukemiao merged PR #57:
URL: https://github.com/apache/iotdb-bin-resources/pull/57


-- 
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, #57: grafana_plugin/apache-iotdb-datasource.zip & grafana_plugin/dockerfile.zip for community tests

2023-05-19 Thread via GitHub


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

   grafana_plugin/apache-iotdb-datasource.zip & grafana_plugin/dockerfile.zip 
for community tests


-- 
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-5903) Cannot select any inner space compaction task when there is only unsequence data

2023-05-19 Thread Liuxuxin (Jira)
Liuxuxin created IOTDB-5903:
---

 Summary: Cannot select any inner space compaction task when there 
is only unsequence data
 Key: IOTDB-5903
 URL: https://issues.apache.org/jira/browse/IOTDB-5903
 Project: Apache IoTDB
  Issue Type: Bug
Reporter: Liuxuxin
 Attachments: image-2023-05-19-16-16-44-423.png

!image-2023-05-19-16-16-44-423.png!

 

The reason is that the tsfile manager will only return the time partition id in 
sequence files.



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


[jira] [Assigned] (IOTDB-5902) IoTDB cluster can not restart successfully

2023-05-19 Thread Bo Zhang (Jira)


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

Bo Zhang reassigned IOTDB-5902:
---

Assignee: Bo Zhang

> IoTDB cluster can not restart successfully
> --
>
> Key: IOTDB-5902
> URL: https://issues.apache.org/jira/browse/IOTDB-5902
> Project: Apache IoTDB
>  Issue Type: Bug
>  Components: Core/Cluster
>Reporter: Bo Zhang
>Assignee: Bo Zhang
>Priority: Major
>
> IoTDB cluster can not restart successfully when cluster has had user data.
> !https://aone.alibaba-inc.com/v2/api/workitem/adapter/file/url?fileIdentifier=workitem%2Falibaba%2Fdefault%2F1682250119245image.png!
> Note:
> If  following the comments in above graph to delete mlog.bin and restart 
> again, the result is that : 
> DN can restart successfully, but can not query any user data.



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


[jira] [Commented] (IOTDB-5902) IoTDB cluster can not restart successfully

2023-05-19 Thread Bo Zhang (Jira)


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

Bo Zhang commented on IOTDB-5902:
-

*Root-cause 分析:*

DataNode 持久化 schema 信息到本地时,序列化 和 反序列化 代码 没有对齐。

序列化使用了 enum 的  ordinal(),反序列化使用自定义 的 deserialize(),二者功能没对齐。

导致 cluster 重启时读取本地的 schema 持久化文件 mlog.bin 时,产生了错误。

*问题触发条件:*

1)cluster 有配置 : 
schema_region_consensus_protocol_class=org.apache.iotdb.consensus.simple.SimpleConsensus

2)压缩方式使用了 LZ4

> IoTDB cluster can not restart successfully
> --
>
> Key: IOTDB-5902
> URL: https://issues.apache.org/jira/browse/IOTDB-5902
> Project: Apache IoTDB
>  Issue Type: Bug
>  Components: Core/Cluster
>Reporter: Bo Zhang
>Priority: Major
>
> IoTDB cluster can not restart successfully when cluster has had user data.
> !https://aone.alibaba-inc.com/v2/api/workitem/adapter/file/url?fileIdentifier=workitem%2Falibaba%2Fdefault%2F1682250119245image.png!
> Note:
> If  following the comments in above graph to delete mlog.bin and restart 
> again, the result is that : 
> DN can restart successfully, but can not query any user data.



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


[jira] [Created] (IOTDB-5902) IoTDB cluster can not restart successfully

2023-05-19 Thread Bo Zhang (Jira)
Bo Zhang created IOTDB-5902:
---

 Summary: IoTDB cluster can not restart successfully
 Key: IOTDB-5902
 URL: https://issues.apache.org/jira/browse/IOTDB-5902
 Project: Apache IoTDB
  Issue Type: Bug
  Components: Core/Cluster
Reporter: Bo Zhang


IoTDB cluster can not restart successfully when cluster has had data.

!https://aone.alibaba-inc.com/v2/api/workitem/adapter/file/url?fileIdentifier=workitem%2Falibaba%2Fdefault%2F1682250119245image.png!



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


[jira] [Created] (IOTDB-5901) Load: load tsfile without data will throw NPE

2023-05-19 Thread yusicheng (Jira)
yusicheng created IOTDB-5901:


 Summary: Load: load tsfile without data will throw NPE
 Key: IOTDB-5901
 URL: https://issues.apache.org/jira/browse/IOTDB-5901
 Project: Apache IoTDB
  Issue Type: Bug
Reporter: yusicheng
Assignee: yusicheng


load a  tsfile without data will throw NPE

java.lang.NullPointerException: null
at 
org.apache.iotdb.commons.partition.StorageExecutor.getDataNodeLocation(StorageExecutor.java:39)
at 
org.apache.iotdb.db.mpp.plan.planner.plan.FragmentInstance.setExecutorAndHost(FragmentInstance.java:107)
at 
org.apache.iotdb.db.mpp.plan.scheduler.load.LoadTsFileScheduler.loadLocally(LoadTsFileScheduler.java:319)
at 
org.apache.iotdb.db.mpp.plan.scheduler.load.LoadTsFileScheduler.start(LoadTsFileScheduler.java:140)
at 
org.apache.iotdb.db.mpp.plan.execution.QueryExecution.schedule(QueryExecution.java:305)
at 
org.apache.iotdb.db.mpp.plan.execution.QueryExecution.start(QueryExecution.java:219)
at 
org.apache.iotdb.db.mpp.plan.Coordinator.execute(Coordinator.java:161)
at 
org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.executeStatementInternal(ClientRPCServiceImpl.java:221)
at 
org.apache.iotdb.db.service.thrift.impl.ClientRPCServiceImpl.executeStatementV2(ClientRPCServiceImpl.java:502)
at 
org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$executeStatementV2.getResult(IClientRPCService.java:3689)
at 
org.apache.iotdb.service.rpc.thrift.IClientRPCService$Processor$executeStatementV2.getResult(IClientRPCService.java:3669)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:38)
at 
org.apache.iotdb.db.service.thrift.ProcessorWithMetrics.process(ProcessorWithMetrics.java:64)
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:750)



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


[jira] [Created] (IOTDB-5900) Put SessionIdleTime into IClientSession

2023-05-19 Thread Yuan Tian (Jira)
Yuan Tian created IOTDB-5900:


 Summary: Put SessionIdleTime into IClientSession
 Key: IOTDB-5900
 URL: https://issues.apache.org/jira/browse/IOTDB-5900
 Project: Apache IoTDB
  Issue Type: Improvement
Reporter: Yuan Tian
Assignee: Hongyin Zhang
 Attachments: image-2023-05-19-14-07-47-413.png

All session related info should be put into IClientSession.

!image-2023-05-19-14-07-47-413.png!



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