[jira] [Commented] (IOTDB-1208) [master-0.12.0-snapshot][iotdb-cluster]Cannot open transport for client Node
[ https://issues.apache.org/jira/browse/IOTDB-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17299355#comment-17299355 ] Houliang Qi commented on IOTDB-1208: Thank you for your feedback, I will revise the docs description! > [master-0.12.0-snapshot][iotdb-cluster]Cannot open transport for client Node > > > Key: IOTDB-1208 > URL: https://issues.apache.org/jira/browse/IOTDB-1208 > Project: Apache IoTDB > Issue Type: Bug > Components: Cluster >Reporter: FengQingxin >Priority: Major > Attachments: image-2021-03-11-11-02-27-954.png, > image-2021-03-11-11-02-36-333.png, log_all.log > > > branch : master > commit 19ad435bc93c1ae8b71be1e9454bc4dad31018c6 > Author: wangchao316 > <66939405+wangchao316@[users.noreply.github.com|http://users.noreply.github.com/]> > Date: Thu Mar 11 09:01:06 2021 +0800 > [IOTDB-1204] set parameter in iotdb-cluster.properties (#2797) > Repeat steps： > # 第一步 (注意以下路径在 Windows MinGW 中并不适用) > > mvn clean package -pl cluster -am -Dmaven.test.skip=true > > cp -rf ./cluster/target/cluster-0.12.0-SNAPSHOT > ./cluster/target/cluster-0.12.0-SNAPSHOT1 > > cp -rf ./cluster/target/cluster-0.12.0-SNAPSHOT > ./cluster/target/cluster-0.12.0-SNAPSHOT2 > > sed -i -e 's/6667/6668/g' > ./cluster/target/cluster-0.12.0-SNAPSHOT1/conf/iotdb-engine.properties > > sed -i -e 's/6667/6669/g' > ./cluster/target/cluster-0.12.0-SNAPSHOT2/conf/iotdb-engine.properties > # 第二步: Unix/OS X/Windows (git bash or WSL) > > sed -i -e 's/31999/32000/g' > ./cluster/target/cluster-0.12.0-SNAPSHOT1/conf/iotdb-env.sh > > sed -i -e 's/31999/32001/g' > ./cluster/target/cluster-0.12.0-SNAPSHOT2/conf/iotdb-env.sh > > chmod -R 777 ./cluster/target/ > > nohup ./cluster/target/cluster-0.12.0-SNAPSHOT/sbin/start-node.sh > >/dev/null 2>&1 & > > nohup ./cluster/target/cluster-0.12.0-SNAPSHOT1/sbin/start-node.sh > -internal_meta_port 9005 -internal_data_port 40012 -cluster_rpc_port 55561 > >/dev/null 2>&1 & > > nohup ./cluster/target/cluster-0.12.0-SNAPSHOT2/sbin/start-node.sh > -internal_meta_port 9007 -internal_data_port 40014 -cluster_rpc_port 55562 > >/dev/null 2>&1 & > After that I can't connect iotdb with iotdb-cli,and there are error logs in > log_all.log. > Please refer to the attachment. > !image-2021-03-11-11-02-27-954.png!!image-2021-03-11-11-02-36-333.png! > # -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1211) create function [Reserved Words] ，The error message is not clear
刘珍 created IOTDB-1211:
-
Summary: create function [Reserved Words] ，The error message is
not clear
Key: IOTDB-1211
URL: https://issues.apache.org/jira/browse/IOTDB-1211
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Engine
Reporter: 刘珍
Attachments: image-2021-03-11-14-46-00-500.png
master branch
commit 5fcff40f2299caeb0c8a9ae42f68bc18ecf8fee7
Merge: 7f9 f63b849
Author: Xiangwei Wei <34242296+alima...@users.noreply.github.com>
Date: Thu Mar 4 15:57:38 2021 +0800
Merge pull request #2759 from apache/fixQueryInfoNull
[ISSUE-2758] NullPointerException in QueryTimeManager.checkQueryAlive()
IoTDB> CREATE FUNCTION {color:#FF}add{color} AS
"org.apache.iotdb.udf.Adder";
{color:#FF}Msg: 401: Error occurred while parsing SQL to physical plan:
line 1:16 mismatched input 'add' expecting ID{color}
{color:#FF}!image-2021-03-11-14-46-00-500.png!{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-1208) [master-0.12.0-snapshot][iotdb-cluster]Cannot open transport for client Node
[ https://issues.apache.org/jira/browse/IOTDB-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17299341#comment-17299341 ] FengQingxin commented on IOTDB-1208: Yes! It works. But "mvn clean package -pl cluster -am -Dmaven.test.skip=true" is inappropriate. We should using "mvn clean package -DskipTests" under "/iotdb/cluster", then the folder named "test-classes" will be created and we can try it as the description in the website[2]. > [master-0.12.0-snapshot][iotdb-cluster]Cannot open transport for client Node > > > Key: IOTDB-1208 > URL: https://issues.apache.org/jira/browse/IOTDB-1208 > Project: Apache IoTDB > Issue Type: Bug > Components: Cluster >Reporter: FengQingxin >Priority: Major > Attachments: image-2021-03-11-11-02-27-954.png, > image-2021-03-11-11-02-36-333.png, log_all.log > > > branch : master > commit 19ad435bc93c1ae8b71be1e9454bc4dad31018c6 > Author: wangchao316 > <66939405+wangchao316@[users.noreply.github.com|http://users.noreply.github.com/]> > Date: Thu Mar 11 09:01:06 2021 +0800 > [IOTDB-1204] set parameter in iotdb-cluster.properties (#2797) > Repeat steps： > # 第一步 (注意以下路径在 Windows MinGW 中并不适用) > > mvn clean package -pl cluster -am -Dmaven.test.skip=true > > cp -rf ./cluster/target/cluster-0.12.0-SNAPSHOT > ./cluster/target/cluster-0.12.0-SNAPSHOT1 > > cp -rf ./cluster/target/cluster-0.12.0-SNAPSHOT > ./cluster/target/cluster-0.12.0-SNAPSHOT2 > > sed -i -e 's/6667/6668/g' > ./cluster/target/cluster-0.12.0-SNAPSHOT1/conf/iotdb-engine.properties > > sed -i -e 's/6667/6669/g' > ./cluster/target/cluster-0.12.0-SNAPSHOT2/conf/iotdb-engine.properties > # 第二步: Unix/OS X/Windows (git bash or WSL) > > sed -i -e 's/31999/32000/g' > ./cluster/target/cluster-0.12.0-SNAPSHOT1/conf/iotdb-env.sh > > sed -i -e 's/31999/32001/g' > ./cluster/target/cluster-0.12.0-SNAPSHOT2/conf/iotdb-env.sh > > chmod -R 777 ./cluster/target/ > > nohup ./cluster/target/cluster-0.12.0-SNAPSHOT/sbin/start-node.sh > >/dev/null 2>&1 & > > nohup ./cluster/target/cluster-0.12.0-SNAPSHOT1/sbin/start-node.sh > -internal_meta_port 9005 -internal_data_port 40012 -cluster_rpc_port 55561 > >/dev/null 2>&1 & > > nohup ./cluster/target/cluster-0.12.0-SNAPSHOT2/sbin/start-node.sh > -internal_meta_port 9007 -internal_data_port 40014 -cluster_rpc_port 55562 > >/dev/null 2>&1 & > After that I can't connect iotdb with iotdb-cli,and there are error logs in > log_all.log. > Please refer to the attachment. > !image-2021-03-11-11-02-27-954.png!!image-2021-03-11-11-02-36-333.png! > # -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1210) Skip code coverage and sonar reports in a forked pull request
Eric Pai created IOTDB-1210: --- Summary: Skip code coverage and sonar reports in a forked pull request Key: IOTDB-1210 URL: https://issues.apache.org/jira/browse/IOTDB-1210 Project: Apache IoTDB Issue Type: Task Components: CI Reporter: Eric Pai Fix For: master branch For any pull requests triggered from a forked repository, the jobs _Code Coverage (Coveralls)_ and _SonarCloud Report_ are always failed because the secrets in apache/iotdb can't be used in a forked repo. Thus we can skip the two jobs if they're triggered in a pull request. Fixed in https://github.com/apache/iotdb/pull/2806 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1209) When loading a tsfile with a large timestamp, the data is incorrect
Houliang Qi created IOTDB-1209: -- Summary: When loading a tsfile with a large timestamp, the data is incorrect Key: IOTDB-1209 URL: https://issues.apache.org/jira/browse/IOTDB-1209 Project: Apache IoTDB Issue Type: Bug Reporter: Houliang Qi Step 1： # insert into root.group_1.d_1(timestamp, s_1, s_0, s_2) values(2018-07-18T00:00:00.000+08:00, 18, false, 18.18) # flush # insert into root.group_1.d_1(timestamp, s_1, s_0, s_2) values(2018-07-19T00:00:00.000+08:00, 19, false, 19.18) # flush !https://code.bonc.com.cn/confluence/download/attachments/64011154/image2021-3-11%2012%3A0%3A42.png?version=1&modificationDate=1615435242446&api=v2! Step2： load one tsfile which the tsfile name have a large timestamp, but its data's timestamp are small. # load "../1678502448000-1-0.tsfile" # !https://code.bonc.com.cn/confluence/download/attachments/64011154/image2021-3-11%2012%3A1%3A12.png?version=1&modificationDate=1615435272389&api=v2! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1208) [master-0.12.0-snapshot][iotdb-cluster]Cannot open transport for client Node
[ https://issues.apache.org/jira/browse/IOTDB-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17299282#comment-17299282 ] Houliang Qi commented on IOTDB-1208: Thanks [~QX.Feng]， I think you referenced the old docs, it have been changed after PR[1], the new setup docs can be found here[2]. You can retry according to [2]. [1]https://github.com/apache/iotdb/pull/2740 [2] http://iotdb.apache.org/UserGuide/Master/Server/Cluster%20Setup.html > [master-0.12.0-snapshot][iotdb-cluster]Cannot open transport for client Node > > > Key: IOTDB-1208 > URL: https://issues.apache.org/jira/browse/IOTDB-1208 > Project: Apache IoTDB > Issue Type: Bug > Components: Cluster >Reporter: FengQingxin >Priority: Major > Attachments: image-2021-03-11-11-02-27-954.png, > image-2021-03-11-11-02-36-333.png, log_all.log > > > branch : master > commit 19ad435bc93c1ae8b71be1e9454bc4dad31018c6 > Author: wangchao316 > <66939405+wangchao316@[users.noreply.github.com|http://users.noreply.github.com/]> > Date: Thu Mar 11 09:01:06 2021 +0800 > [IOTDB-1204] set parameter in iotdb-cluster.properties (#2797) > Repeat steps： > # 第一步 (注意以下路径在 Windows MinGW 中并不适用) > > mvn clean package -pl cluster -am -Dmaven.test.skip=true > > cp -rf ./cluster/target/cluster-0.12.0-SNAPSHOT > ./cluster/target/cluster-0.12.0-SNAPSHOT1 > > cp -rf ./cluster/target/cluster-0.12.0-SNAPSHOT > ./cluster/target/cluster-0.12.0-SNAPSHOT2 > > sed -i -e 's/6667/6668/g' > ./cluster/target/cluster-0.12.0-SNAPSHOT1/conf/iotdb-engine.properties > > sed -i -e 's/6667/6669/g' > ./cluster/target/cluster-0.12.0-SNAPSHOT2/conf/iotdb-engine.properties > # 第二步: Unix/OS X/Windows (git bash or WSL) > > sed -i -e 's/31999/32000/g' > ./cluster/target/cluster-0.12.0-SNAPSHOT1/conf/iotdb-env.sh > > sed -i -e 's/31999/32001/g' > ./cluster/target/cluster-0.12.0-SNAPSHOT2/conf/iotdb-env.sh > > chmod -R 777 ./cluster/target/ > > nohup ./cluster/target/cluster-0.12.0-SNAPSHOT/sbin/start-node.sh > >/dev/null 2>&1 & > > nohup ./cluster/target/cluster-0.12.0-SNAPSHOT1/sbin/start-node.sh > -internal_meta_port 9005 -internal_data_port 40012 -cluster_rpc_port 55561 > >/dev/null 2>&1 & > > nohup ./cluster/target/cluster-0.12.0-SNAPSHOT2/sbin/start-node.sh > -internal_meta_port 9007 -internal_data_port 40014 -cluster_rpc_port 55562 > >/dev/null 2>&1 & > After that I can't connect iotdb with iotdb-cli,and there are error logs in > log_all.log. > Please refer to the attachment. > !image-2021-03-11-11-02-27-954.png!!image-2021-03-11-11-02-36-333.png! > # -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1208) [master-0.12.0-snapshot][iotdb-cluster]Cannot open transport for client Node
FengQingxin created IOTDB-1208: -- Summary: [master-0.12.0-snapshot][iotdb-cluster]Cannot open transport for client Node Key: IOTDB-1208 URL: https://issues.apache.org/jira/browse/IOTDB-1208 Project: Apache IoTDB Issue Type: Bug Components: Cluster Reporter: FengQingxin Attachments: image-2021-03-11-11-02-27-954.png, image-2021-03-11-11-02-36-333.png, log_all.log Repeat steps： # 第一步 (注意以下路径在 Windows MinGW 中并不适用) > mvn clean package -pl cluster -am -Dmaven.test.skip=true > cp -rf ./cluster/target/cluster-0.12.0-SNAPSHOT > ./cluster/target/cluster-0.12.0-SNAPSHOT1 > cp -rf ./cluster/target/cluster-0.12.0-SNAPSHOT > ./cluster/target/cluster-0.12.0-SNAPSHOT2 > sed -i -e 's/6667/6668/g' > ./cluster/target/cluster-0.12.0-SNAPSHOT1/conf/iotdb-engine.properties > sed -i -e 's/6667/6669/g' > ./cluster/target/cluster-0.12.0-SNAPSHOT2/conf/iotdb-engine.properties # 第二步: Unix/OS X/Windows (git bash or WSL) > sed -i -e 's/31999/32000/g' > ./cluster/target/cluster-0.12.0-SNAPSHOT1/conf/iotdb-env.sh > sed -i -e 's/31999/32001/g' > ./cluster/target/cluster-0.12.0-SNAPSHOT2/conf/iotdb-env.sh > chmod -R 777 ./cluster/target/ > nohup ./cluster/target/cluster-0.12.0-SNAPSHOT/sbin/start-node.sh >/dev/null > 2>&1 & > nohup ./cluster/target/cluster-0.12.0-SNAPSHOT1/sbin/start-node.sh > -internal_meta_port 9005 -internal_data_port 40012 -cluster_rpc_port 55561 > >/dev/null 2>&1 & > nohup ./cluster/target/cluster-0.12.0-SNAPSHOT2/sbin/start-node.sh > -internal_meta_port 9007 -internal_data_port 40014 -cluster_rpc_port 55562 > >/dev/null 2>&1 & After that I can't connect iotdb with iotdb-cli,and there are error logs in log_all.log. Please refer to the attachment. !image-2021-03-11-11-02-27-954.png!!image-2021-03-11-11-02-36-333.png! # -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1207) Open time partition causes stackoverflow
wangyanhong created IOTDB-1207: -- Summary: Open time partition causes stackoverflow Key: IOTDB-1207 URL: https://issues.apache.org/jira/browse/IOTDB-1207 Project: Apache IoTDB Issue Type: Bug Components: Cluster Reporter: wangyanhong Attachments: image-2021-03-11-10-26-50-700.png Open time partition causes stackoverflow when use six nodes and three replication !image-2021-03-11-10-26-50-700.png! After preliminary study,Find the problem occurs in the process of inserting data to get the schema Read remote schema in mRemoteMetaCache and if not all the schemas were obtained, it will read local schema before read remote shema ,it will try to get the corresponding device from local mNodeCache , If the device is not found, it will skip reading the remote schema and read the local schema because local mNodeCache dosen't contain remote device , it will never read remote schema from mRemoteMetaCache ,this causes the insert execution fail，forward plan failed, and then will create timeseries for fail insertion,In this process, the timeseries need to be created is empty ,it causes the process of creating timeseries to enter an infinite loop。 In order to solve this problem, I removed the code that get the corresponding device from local mNodeCache. but it causes another problem，When the amount of data is large，benchmark will get stuck and occur timeout -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1206) Clean memory states after removing partitions
[ https://issues.apache.org/jira/browse/IOTDB-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17298932#comment-17298932 ] Xiangdong Huang commented on IOTDB-1206: timePartitionIdVersionControllerMap, latestTimeForEachDevice etc.. also need tobe clean > Clean memory states after removing partitions > - > > Key: IOTDB-1206 > URL: https://issues.apache.org/jira/browse/IOTDB-1206 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Engine >Reporter: Tian Jiang >Priority: Minor > > When a partition is removed from a storage group, some of its memory states > such as device flushed time map and last caches remain uncleaned. We should > clean them to reclaim their memory and enable more data ingested as seq files. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1201) [spark-tsfile]java.lang.NumberFormatException: For input string: "unknown"
[ https://issues.apache.org/jira/browse/IOTDB-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17298805#comment-17298805 ] Kaifeng Xue commented on IOTDB-1201: This is a bug in spark jetty (not IoTDB). And when I run this command on my computer, there is no such problem > [spark-tsfile]java.lang.NumberFormatException: For input string: "unknown" > -- > > Key: IOTDB-1201 > URL: https://issues.apache.org/jira/browse/IOTDB-1201 > Project: Apache IoTDB > Issue Type: Bug > Components: Connectors/Spark-TsFile >Reporter: FengQingxin >Priority: Minor > Attachments: image-2021-03-10-17-05-50-744.png > > > Hi > when I using spark-shell, I got an exception : > java.lang.NumberFormatException: For input string: "unknown". > iotdb : d622fe88fe688e4b6e212af26e573c0581daab1a > spark : spark-2.4.7-bin-hadoop2.7/ > command : ./spark-shell --jars > spark-tsfile-0.12.0-SNAPSHOT.jar,tsfile-0.12.0-SNAPSHOT-jar-with-dependencies.jar > > log: > !image-2021-03-10-17-05-50-744.png! > 16:45:27.149 [main] DEBUG org.spark_project.jetty.util.Jetty - > java.lang.NumberFormatException: For input string: "unknown" > at > java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) > at java.lang.Long.parseLong(Long.java:589) > at java.lang.Long.valueOf(Long.java:803) > at org.spark_project.jetty.util.Jetty.formatTimestamp(Jetty.java:89) > at org.spark_project.jetty.util.Jetty.(Jetty.java:61) > at org.spark_project.jetty.server.Server.getVersion(Server.java:159) > at > org.spark_project.jetty.server.handler.ContextHandler.(ContextHandler.java:128) > at org.apache.spark.ui.JettyUtils$.createServletHandler(JettyUtils.scala:143) > at org.apache.spark.ui.JettyUtils$.createServletHandler(JettyUtils.scala:130) > at org.apache.spark.ui.WebUI.attachPage(WebUI.scala:89) > at org.apache.spark.ui.WebUI$$anonfun$attachTab$1.apply(WebUI.scala:71) > at org.apache.spark.ui.WebUI$$anonfun$attachTab$1.apply(WebUI.scala:71) > at > scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59) > at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:48) > at org.apache.spark.ui.WebUI.attachTab(WebUI.scala:71) > at org.apache.spark.ui.SparkUI.initialize(SparkUI.scala:62) > at org.apache.spark.ui.SparkUI.(SparkUI.scala:80) > at org.apache.spark.ui.SparkUI$.create(SparkUI.scala:178) > at org.apache.spark.SparkContext.(SparkContext.scala:444) > at org.apache.spark.SparkContext$.getOrCreate(SparkContext.scala:2520) > at > org.apache.spark.sql.SparkSession$Builder$$anonfun$7.apply(SparkSession.scala:930) > at > org.apache.spark.sql.SparkSession$Builder$$anonfun$7.apply(SparkSession.scala:921) > at scala.Option.getOrElse(Option.scala:121) > at > org.apache.spark.sql.SparkSession$Builder.getOrCreate(SparkSession.scala:921) > at org.apache.spark.repl.Main$.createSparkSession(Main.scala:106) > at $line3.$read$$iw$$iw.(:15) > at $line3.$read$$iw.(:43) > at $line3.$read.(:45) > at $line3.$read$.(:49) > at $line3.$read$.() > at $line3.$eval$.$print$lzycompute(:7) > at $line3.$eval$.$print(:6) > at $line3.$eval.$print() > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at scala.tools.nsc.interpreter.IMain$ReadEvalPrint.call(IMain.scala:793) > at scala.tools.nsc.interpreter.IMain$Request.loadAndRun(IMain.scala:1054) > at > scala.tools.nsc.interpreter.IMain$WrappedRequest$$anonfun$loadAndRunReq$1.apply(IMain.scala:645) > at > scala.tools.nsc.interpreter.IMain$WrappedRequest$$anonfun$loadAndRunReq$1.apply(IMain.scala:644) > at > scala.reflect.internal.util.ScalaClassLoader$class.asContext(ScalaClassLoader.scala:31) > at > scala.reflect.internal.util.AbstractFileClassLoader.asContext(AbstractFileClassLoader.scala:19) > at > scala.tools.nsc.interpreter.IMain$WrappedRequest.loadAndRunReq(IMain.scala:644) > at scala.tools.nsc.interpreter.IMain.interpret(IMain.scala:576) > at scala.tools.nsc.interpreter.IMain.interpret(IMain.scala:572) > at > scala.tools.nsc.interpreter.IMain$$anonfun$quietRun$1.apply(IMain.scala:231) > at > scala.tools.nsc.interpreter.IMain$$anonfun$quietRun$1.apply(IMain.scala:231) > at scala.tools.nsc.interpreter.IMain.beQuietDuring(IMain.scala:221) > at scala.tools.nsc.interpreter.IMain.quietRun(IMain.scala:231) > at > org.apache.spark.repl.SparkILoop$$anonfun$initializeSpark$1$$anonfun$apply$mcV$sp$1.apply(SparkILoop.scala:109) > at > org.apache.spark.repl.SparkILoop$$anonfun$initializeSpark$1$$anonfun$apply$mcV$sp$1.apply(SparkILoop.scala:109)
[jira] [Created] (IOTDB-1206) Clean memory states after removing partitions
Tian Jiang created IOTDB-1206: - Summary: Clean memory states after removing partitions Key: IOTDB-1206 URL: https://issues.apache.org/jira/browse/IOTDB-1206 Project: Apache IoTDB Issue Type: Bug Components: Core/Engine Reporter: Tian Jiang When a partition is removed from a storage group, some of its memory states such as device flushed time map and last caches remain uncleaned. We should clean them to reclaim their memory and enable more data ingested as seq files. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1205) Resource Leakage in removePartition
Xiangdong Huang created IOTDB-1205: -- Summary: Resource Leakage in removePartition Key: IOTDB-1205 URL: https://issues.apache.org/jira/browse/IOTDB-1205 Project: Apache IoTDB Issue Type: Bug Components: Server Reporter: Xiangdong Huang Attachments: image-2021-03-10-20-34-12-915.png When a time partition is removed, the latestFlushTime info in this partition has no meanining. So, we need to remove it from the hashmap, rather than define a "Long.MIN_VALUE" !image-2021-03-10-20-34-12-915.png! Besides, UT needed to confirm all garbages are cleared. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [iotdb-client-go] jixuan1989 merged pull request #17: Supporting submodule of IoTDB, and keep consistent with the parent repo
jixuan1989 merged pull request #17: URL: https://github.com/apache/iotdb-client-go/pull/17 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Assigned] (IOTDB-1198) Add generated-sources as source folder
[
https://issues.apache.org/jira/browse/IOTDB-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiangdong Huang reassigned IOTDB-1198:
--
Assignee: Eric Pai
> Add generated-sources as source folder
> --
>
> Key: IOTDB-1198
> URL: https://issues.apache.org/jira/browse/IOTDB-1198
> Project: Apache IoTDB
> Issue Type: Task
> Components: Others
>Reporter: Eric Pai
>Assignee: Eric Pai
>Priority: Minor
> Labels: needs-review, pull-request-available
> Fix For: 0.12.0
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> h1. Description
> The generated source files in _thirft/target/generated-sources_ and
> _antlr/target/generated-sources_ can't be auto discovered by IDEs like VSCode
> and IntelliJ IDEA.
> In IDEA, we can solve this by following the instructions in
> [https://iotdb.apache.org/Development/ContributeGuide.html#_2-iotdb-debugging-method].
> However, this can't be applied in VSCode Java plugin because adding a folder
> to Java source path is forbidden in a maven project. The error output is
> *Unsupported operation. Please use pom.xml file to manage the source
> directories of maven project*.
> h1. Solution
> Use *build-helper-maven-plugin* to add the folder to sources in
> *generate-sources* phase.
> Influenced modules:
> - antlr
> - thrift
> If this PR is accepted, I will submit another one to update the docs.
> h1. Note
> We must use
> {code:java}
> ${project.build.directory}/generated-sources/antlr4{code}
> instead of
> {code:java}
> ${project.build.outputDirectory}/../generated-sources/antlr4{code}
> The resaons are:
> 1. Although the two paths refer to the same dictionary, their string
> representations are different. e.g.
> _antlr/target/classes/../generated-sources/antlr4_ and
> _antlr/target/generated-sources/antlr4_.
> 2. It seems that *javac* of JDK8 will not simplify the source path, thus a
> *duplicate class* compilcation error occurs.
> 3. JDK11 and 15 fixed this issue(I guess).
> See this CI result: [https://github.com/apache/iotdb/actions/runs/635878512]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1204) set WAIT_CLIENT_TIMEOUT_MS in cluster-config.xml
Chao Wang created IOTDB-1204: Summary: set WAIT_CLIENT_TIMEOUT_MS in cluster-config.xml Key: IOTDB-1204 URL: https://issues.apache.org/jira/browse/IOTDB-1204 Project: Apache IoTDB Issue Type: Improvement Components: Core/Cluster Reporter: Chao Wang Assignee: Chao Wang Fix For: 0.12.0 The WAIT_CLIENT_TIMEOUT_MS andmaxConnectionForEachNode parameter controls the connection generation speed and affects cluster link access. Therefore, it can be configured in the cluster_config.xml file. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1203) Create interface of IMeasurementSchema
Zesong Sun created IOTDB-1203: - Summary: Create interface of IMeasurementSchema Key: IOTDB-1203 URL: https://issues.apache.org/jira/browse/IOTDB-1203 Project: Apache IoTDB Issue Type: Sub-task Components: Server Reporter: Zesong Sun Assignee: Zesong Sun Fix For: 0.12.0 We should create interface of *IMeasurementSchema*, which is implemented by both *MeasurementSchema* and *VectorMeasurementSchema* (to be implemented) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1202) reduce the size of session/jdbc library
Xiangdong Huang created IOTDB-1202: -- Summary: reduce the size of session/jdbc library Key: IOTDB-1202 URL: https://issues.apache.org/jira/browse/IOTDB-1202 Project: Apache IoTDB Issue Type: Task Reporter: Xiangdong Huang we notice that the session and jdbc lirary is large (more than 7MB), as it packs too many unused classes into the jar. It is time to reduce the size. 1. Thrift module generated thrift sources are very large. And the client (jdbc and the session) only use the rpc.thrift. So, we can seperate the original thrift module into 3 parts: rpc, sync, and the cluster. The client module depends on the rpc only; The server module depends on the rpc and the sync; The cluster module depends on the 3 parts; 2. TsFile module As the client module just needs some classes like TSDataype, so we do not need to depend on the transitive dependency of the tsfile module. So, I exclude all transitive dependency of the tsfile module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1201) [spark-tsfile]java.lang.NumberFormatException: For input string: "unknown"
FengQingxin created IOTDB-1201: -- Summary: [spark-tsfile]java.lang.NumberFormatException: For input string: "unknown" Key: IOTDB-1201 URL: https://issues.apache.org/jira/browse/IOTDB-1201 Project: Apache IoTDB Issue Type: Bug Components: Connectors/Spark-TsFile Reporter: FengQingxin Attachments: image-2021-03-10-17-05-50-744.png Hi when I using spark-shell, I got an exception : java.lang.NumberFormatException: For input string: "unknown". iotdb : d622fe88fe688e4b6e212af26e573c0581daab1a spark : spark-2.4.7-bin-hadoop2.7/ command : ./spark-shell --jars spark-tsfile-0.12.0-SNAPSHOT.jar,tsfile-0.12.0-SNAPSHOT-jar-with-dependencies.jar log: !image-2021-03-10-17-05-50-744.png! 16:45:27.149 [main] DEBUG org.spark_project.jetty.util.Jetty - java.lang.NumberFormatException: For input string: "unknown" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Long.parseLong(Long.java:589) at java.lang.Long.valueOf(Long.java:803) at org.spark_project.jetty.util.Jetty.formatTimestamp(Jetty.java:89) at org.spark_project.jetty.util.Jetty.(Jetty.java:61) at org.spark_project.jetty.server.Server.getVersion(Server.java:159) at org.spark_project.jetty.server.handler.ContextHandler.(ContextHandler.java:128) at org.apache.spark.ui.JettyUtils$.createServletHandler(JettyUtils.scala:143) at org.apache.spark.ui.JettyUtils$.createServletHandler(JettyUtils.scala:130) at org.apache.spark.ui.WebUI.attachPage(WebUI.scala:89) at org.apache.spark.ui.WebUI$$anonfun$attachTab$1.apply(WebUI.scala:71) at org.apache.spark.ui.WebUI$$anonfun$attachTab$1.apply(WebUI.scala:71) at scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59) at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:48) at org.apache.spark.ui.WebUI.attachTab(WebUI.scala:71) at org.apache.spark.ui.SparkUI.initialize(SparkUI.scala:62) at org.apache.spark.ui.SparkUI.(SparkUI.scala:80) at org.apache.spark.ui.SparkUI$.create(SparkUI.scala:178) at org.apache.spark.SparkContext.(SparkContext.scala:444) at org.apache.spark.SparkContext$.getOrCreate(SparkContext.scala:2520) at org.apache.spark.sql.SparkSession$Builder$$anonfun$7.apply(SparkSession.scala:930) at org.apache.spark.sql.SparkSession$Builder$$anonfun$7.apply(SparkSession.scala:921) at scala.Option.getOrElse(Option.scala:121) at org.apache.spark.sql.SparkSession$Builder.getOrCreate(SparkSession.scala:921) at org.apache.spark.repl.Main$.createSparkSession(Main.scala:106) at $line3.$read$$iw$$iw.(:15) at $line3.$read$$iw.(:43) at $line3.$read.(:45) at $line3.$read$.(:49) at $line3.$read$.() at $line3.$eval$.$print$lzycompute(:7) at $line3.$eval$.$print(:6) at $line3.$eval.$print() at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at scala.tools.nsc.interpreter.IMain$ReadEvalPrint.call(IMain.scala:793) at scala.tools.nsc.interpreter.IMain$Request.loadAndRun(IMain.scala:1054) at scala.tools.nsc.interpreter.IMain$WrappedRequest$$anonfun$loadAndRunReq$1.apply(IMain.scala:645) at scala.tools.nsc.interpreter.IMain$WrappedRequest$$anonfun$loadAndRunReq$1.apply(IMain.scala:644) at scala.reflect.internal.util.ScalaClassLoader$class.asContext(ScalaClassLoader.scala:31) at scala.reflect.internal.util.AbstractFileClassLoader.asContext(AbstractFileClassLoader.scala:19) at scala.tools.nsc.interpreter.IMain$WrappedRequest.loadAndRunReq(IMain.scala:644) at scala.tools.nsc.interpreter.IMain.interpret(IMain.scala:576) at scala.tools.nsc.interpreter.IMain.interpret(IMain.scala:572) at scala.tools.nsc.interpreter.IMain$$anonfun$quietRun$1.apply(IMain.scala:231) at scala.tools.nsc.interpreter.IMain$$anonfun$quietRun$1.apply(IMain.scala:231) at scala.tools.nsc.interpreter.IMain.beQuietDuring(IMain.scala:221) at scala.tools.nsc.interpreter.IMain.quietRun(IMain.scala:231) at org.apache.spark.repl.SparkILoop$$anonfun$initializeSpark$1$$anonfun$apply$mcV$sp$1.apply(SparkILoop.scala:109) at org.apache.spark.repl.SparkILoop$$anonfun$initializeSpark$1$$anonfun$apply$mcV$sp$1.apply(SparkILoop.scala:109) at scala.collection.immutable.List.foreach(List.scala:392) at org.apache.spark.repl.SparkILoop$$anonfun$initializeSpark$1.apply$mcV$sp(SparkILoop.scala:109) at org.apache.spark.repl.SparkILoop$$anonfun$initializeSpark$1.apply(SparkILoop.scala:109) at org.apache.spark.repl.SparkILoop$$anonfun$initializeSpark$1.apply(SparkILoop.scala:109) at scala.tools.nsc.interpreter.ILoop.savingReplayStack(ILoop.scala:91) at org.apache.spark.repl.SparkILoop.initializeSpark(SparkILoop.scala:108) at org.apache.spark.repl.SparkILoop$$anonfun$process$
[jira] [Commented] (IOTDB-1198) Add generated-sources as source folder
[
https://issues.apache.org/jira/browse/IOTDB-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17298650#comment-17298650
]
Eric Pai commented on IOTDB-1198:
-
Pull Request: https://github.com/apache/iotdb/pull/2789
> Add generated-sources as source folder
> --
>
> Key: IOTDB-1198
> URL: https://issues.apache.org/jira/browse/IOTDB-1198
> Project: Apache IoTDB
> Issue Type: Task
> Components: Others
>Reporter: Eric Pai
>Priority: Minor
> Labels: needs-review
> Fix For: master branch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> h1. Description
> The generated source files in _thirft/target/generated-sources_ and
> _antlr/target/generated-sources_ can't be auto discovered by IDEs like VSCode
> and IntelliJ IDEA.
> In IDEA, we can solve this by following the instructions in
> [https://iotdb.apache.org/Development/ContributeGuide.html#_2-iotdb-debugging-method].
> However, this can't be applied in VSCode Java plugin because adding a folder
> to Java source path is forbidden in a maven project. The error output is
> *Unsupported operation. Please use pom.xml file to manage the source
> directories of maven project*.
> h1. Solution
> Use *build-helper-maven-plugin* to add the folder to sources in
> *generate-sources* phase.
> Influenced modules:
> - antlr
> - thrift
> If this PR is accepted, I will submit another one to update the docs.
> Note
> We must use
> {code:java}
> ${project.build.directory}/generated-sources/antlr4{code}
> instead of
> {code:java}
> ${project.build.outputDirectory}/../generated-sources/antlr4{code}
> The resaons are:
> 1. Although the two paths refer to the same dictionary, their string
> representations are different. e.g.
> _antlr/target/classes/../generated-sources/antlr4_ and
> _antlr/target/generated-sources/antlr4_.
> 2. It seems that *javac* of JDK8 will not simplify the source path, thus a
> *duplicate class* compilcation error occurs.
> 3. JDK11 and 15 fixed this issue(I guess).
> See this CI result: [https://github.com/apache/iotdb/actions/runs/635878512]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1200) Support device template
Zesong Sun created IOTDB-1200:
-
Summary: Support device template
Key: IOTDB-1200
URL: https://issues.apache.org/jira/browse/IOTDB-1200
Project: Apache IoTDB
Issue Type: New Feature
Reporter: Zesong Sun
Assignee: Zesong Sun
Fix For: 0.12.0
To avoid create timeseries repeatedly when a number of devices / storage groups
have same sensors, we intend to introduce the concept of **device template**.
For example:
{code}
set storage group root.beijing
create device template temp1(
(s1 INT32 with encoding=Gorilla, compression=SNAPPY),
(s2 FLOAT with encoding=RLE, compression=SNAPPY)
)
set device template temp1 to root.beijing
{code}
So that root.beijing has the template temp1.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1199) Support aligned timeseries
Zesong Sun created IOTDB-1199:
-
Summary: Support aligned timeseries
Key: IOTDB-1199
URL: https://issues.apache.org/jira/browse/IOTDB-1199
Project: Apache IoTDB
Issue Type: New Feature
Reporter: Zesong Sun
Assignee: Zesong Sun
Fix For: 0.12.0
In some occasions, we may need to define aligned timeseries such as:
{code:java}
create aligned timeseries root.sg.d1.(s1(alias1) FLOAT, s2 INT32)
with encoding=(RLE, Grollia), compression=SNAPPY
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1198) Add generated-sources as source folder
Eric Pai created IOTDB-1198:
---
Summary: Add generated-sources as source folder
Key: IOTDB-1198
URL: https://issues.apache.org/jira/browse/IOTDB-1198
Project: Apache IoTDB
Issue Type: Task
Components: Others
Reporter: Eric Pai
Fix For: master branch
h1. Description
The generated source files in _thirft/target/generated-sources_ and
_antlr/target/generated-sources_ can't be auto discovered by IDEs like VSCode
and IntelliJ IDEA.
In IDEA, we can solve this by following the instructions in
[https://iotdb.apache.org/Development/ContributeGuide.html#_2-iotdb-debugging-method].
However, this can't be applied in VSCode Java plugin because adding a folder to
Java source path is forbidden in a maven project. The error output is
*Unsupported operation. Please use pom.xml file to manage the source
directories of maven project*.
h1. Solution
Use *build-helper-maven-plugin* to add the folder to sources in
*generate-sources* phase.
Influenced modules:
- antlr
- thrift
If this PR is accepted, I will submit another one to update the docs.
Note
We must use
{code:java}
${project.build.directory}/generated-sources/antlr4{code}
instead of
{code:java}
${project.build.outputDirectory}/../generated-sources/antlr4{code}
The resaons are:
1. Although the two paths refer to the same dictionary, their string
representations are different. e.g.
_antlr/target/classes/../generated-sources/antlr4_ and
_antlr/target/generated-sources/antlr4_.
2. It seems that *javac* of JDK8 will not simplify the source path, thus a
*duplicate class* compilcation error occurs.
3. JDK11 and 15 fixed this issue(I guess).
See this CI result: [https://github.com/apache/iotdb/actions/runs/635878512]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1197) add iotdb-client-go as a submodule of iotdb repo
Xiangdong Huang created IOTDB-1197: -- Summary: add iotdb-client-go as a submodule of iotdb repo Key: IOTDB-1197 URL: https://issues.apache.org/jira/browse/IOTDB-1197 Project: Apache IoTDB Issue Type: Task Reporter: Xiangdong Huang The discussion is on https://lists.apache.org/thread.html/r99e9b72e6f3779acb0888c3ad7acf56a54ffe230cea0ff4bdd6c88f3%40%3Cdev.iotdb.apache.org%3E ## How to get source codes of the submodule when you git clone or git pull the repo, the git command does not clone/pull codes in the submodules automatically; (1) for the first time, you need to run: cd client-go && git submodule update --init (2) for the 2nd time or the future usage, just run git submodule update to get latest codes of the submodule. Notice: when you pull the codes, the submodule is on an anonymous branch. you need to use `git checkout ` or `git checkout -b ` in the client-go folder. ## How to modify codes of the submodule 1. cd client-go, and do whatever you want to do, and then commit codes here by `git add`, `git commit` and `git push` command; 2. cd iotdb's root folder, when you run `git status` at this time, you will find it shows `client-go` is modified, so just run `git add client-go` to let the parent repo knows the submodule's repo is updated. Notice, `git checkout` to a new/existing branch on client-go folder will be considered as a modification operation. And, if you want IoTDB repo knows you want to link a new branch of client-go to iotdb's repo, you can run `git checkout` command in client-go folder. ## Example Scenario: I want to modify the Thrift definition in IoTDB, and need to maintain the go client. Step 1: modify the thrift file and modify codes in IoTDB. Step 2: cd client-go, checkout to a new branch, modify codes.. (Especially, the client-go has to copy generated thrift codes to client-go/rpc/, there are two choices to do that: a. run `mvn generate-sources` in iotdb's folder (not supported now in this PR. will do it later) b. cd client-go, run `make generate` ) Step 3: in client-go, git add, git commit and git push Step 4: int IoTDB's root folder, git add, git commit and git push Step 5: submit a PR to IoTDB, and wait for the success of CI in IoTDB's repo; Step 6: If success, then submit a PR to iotdb-client-go repo, and paste the PR address in IoTDB. (The github action in iotdb-client-go will fail because it just clone codes of iotdb's master branch. However, our modifications of IoTDB are in another branch. So, we need the github action result in IoTDB to show the correction of the modifications in IoTDB-client-go). Step 7: After all reviewers approve the PRs in both IoTDB and IoTDB-client-go, Step 7.1. Merge PR in iotdb-client-go first, and Step 7.2. cd client-go folder, checkout back to the main branch (the iotdb-client-go repo uses `main` ratherthan `master`). Then git add, git commit and git push Step 7.3 After that, send notification on your PR and let others merge the PR in IoTDB -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1196) use this path ：paths.add(new Path("device_1.sensor_1")) for query and got java.lang.NullPointerException
刘珍 created IOTDB-1196:
-
Summary: use this path ：paths.add(new Path("device_1.sensor_1"))
for query and got java.lang.NullPointerException
Key: IOTDB-1196
URL: https://issues.apache.org/jira/browse/IOTDB-1196
Project: Apache IoTDB
Issue Type: Bug
Components: Client/Java
Reporter: 刘珍
master branch
commit 6694c5d70ff78bd1b67768b147514ec57a168990
Author: Yifu Zhou
Date: Wed Mar 10 10:56:04 2021 +0800
Update the SeedUrl Format Exception Info when using cluster mode (#2786)
《IOTDB用户手册- 0.12-snapshot-20210305.pdf》 P115 7.6.2.4 读取现有 TsFile 示例
/**
* The class is to show how to read TsFile file named "test.tsfile". The TsFile
file "test.tsfile"
* is generated from class TsFileWriteWithTSRecord or TsFileWriteWithTablet. Run
* TsFileWriteWithTSRecord or TsFileWriteWithTablet to generate the test.tsfile
first
*/
Run this class，got the exception：
Exception in thread "main" java.lang.NullPointerException
at java.util.TreeMap.getEntry(TreeMap.java:347)
at java.util.TreeMap.containsKey(TreeMap.java:232)
at
org.apache.iotdb.tsfile.read.controller.MetadataQuerierByFileImpl.loadChunkMetaDatas(MetadataQuerierByFileImpl.java:95)
at
org.apache.iotdb.tsfile.read.query.executor.TsFileExecutor.execute(TsFileExecutor.java:70)
at org.apache.iotdb.tsfile.read.ReadOnlyTsFile.query(ReadOnlyTsFile.java:47)
at org.apache.iotdb.tsfile.TsFileRead_pdf.queryAndPrint(TsFileRead_pdf.java:40)
at org.apache.iotdb.tsfile.TsFileRead_pdf.main(TsFileRead_pdf.java:59)
Change
"paths.add(new Path("device_1.sensor_1"));"
into
"paths.add(new Path("device_1", "sensor_1"));"
the result set is right.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
