[jira] [Commented] (IOTDB-1224) The query is pushed down to the DataGroup node.
[ https://issues.apache.org/jira/browse/IOTDB-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17300092#comment-17300092 ] Tian Jiang commented on IOTDB-1224: --- I did not quite get your point. For aggregation without value filter, the current coordinator only fetches the aggregation result from data groups, not the raw data, so I think this differs little from pushing down. > The query is pushed down to the DataGroup node. > --- > > Key: IOTDB-1224 > URL: https://issues.apache.org/jira/browse/IOTDB-1224 > Project: Apache IoTDB > Issue Type: Improvement > Components: Cluster >Reporter: Chao Wang >Assignee: Chao Wang >Priority: Major > Labels: pull-request-available > Fix For: 0.12.0 > > > Currently, in the aggregation query, the coordinator queries data from the > data group in which the sequence is located, and then collects statistics. > This increases the number of RPC times. We can push the statistics down to > the data group for processing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1224) The query is pushed down to the DataGroup node.
[ https://issues.apache.org/jira/browse/IOTDB-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17300083#comment-17300083 ] Chao Wang commented on IOTDB-1224: -- Chinese： 1.all push.当查询语句中的所有序列都在一个data group上时， 我们可以将此语句的执行计划下推到data group上进行处理。 2. partital push. 当查询语句中的序列分布在不同的dataGroup上时。 2.1 如果是不带值过滤查询， 那么可以将按照data group划分plan， 将同一个datagroup上的操作一起下发，然后在协调者处进行拼接合并。 比如： select s1, s2 from root where time > 123 可以拆分成 select s1 from where time > 123 的执行计划 另外一个是select s2 from where time > 123 的执行计划。 然后在协调者处进行拼接。 聚合查询同上。select count(s1), count(s2) from root where time > 123 可以拆分成 select count(s1) from where time > 123 的执行计划AggPlan推向dataGroup 另外一个是select count(s2) from where time > 123 的执行计划推向dataGroup。 然后在协调者处进行拼接结果。 2.2 如果是带值过滤的查询，那么进行现有优化逻辑处理。 > The query is pushed down to the DataGroup node. > --- > > Key: IOTDB-1224 > URL: https://issues.apache.org/jira/browse/IOTDB-1224 > Project: Apache IoTDB > Issue Type: Improvement > Components: Cluster >Reporter: Chao Wang >Assignee: Chao Wang >Priority: Major > Labels: pull-request-available > Fix For: 0.12.0 > > > Currently, in the aggregation query, the coordinator queries data from the > data group in which the sequence is located, and then collects statistics. > This increases the number of RPC times. We can push the statistics down to > the data group for processing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1224) The query is pushed down to the DataGroup node.
[ https://issues.apache.org/jira/browse/IOTDB-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17300082#comment-17300082 ] Chao Wang commented on IOTDB-1224: -- 1. all push. When all sequences in a query statement are in a data group, the execution plan of the statement can be pushed down to the data group for processing. 2. Partial push. When the sequence in the query statement is distributed on different datagroups, 2.1 If the query is performed without a value, you can divide plans by data group, deliver operations in the same data group together, and combine the operations at the coordinator. For example, select s1, s2 from root where time > 123 The execution plan can be split into select s1 from where time > 123. The other is the execution plan of select s2 from where time > 123. The stitching is then done at the coordinator. Aggregate Query Same as above. select count(s1), count(s2) from root where time > 123 The execution plan AggPlan can be split into select count(s1) from where time > 123 and pushed to dataGroup. The other is to push the execution plan of select count(s2) from where time > 123 to dataGroup. The results are then spliced at the coordinator. 2.2 If the query contains value filtering, the existing optimization logic is used. > The query is pushed down to the DataGroup node. > --- > > Key: IOTDB-1224 > URL: https://issues.apache.org/jira/browse/IOTDB-1224 > Project: Apache IoTDB > Issue Type: Improvement > Components: Cluster >Reporter: Chao Wang >Assignee: Chao Wang >Priority: Major > Labels: pull-request-available > Fix For: 0.12.0 > > > Currently, in the aggregation query, the coordinator queries data from the > data group in which the sequence is located, and then collects statistics. > This increases the number of RPC times. We can push the statistics down to > the data group for processing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1224) The query is pushed down to the DataGroup node.
Chao Wang created IOTDB-1224: Summary: The query is pushed down to the DataGroup node. Key: IOTDB-1224 URL: https://issues.apache.org/jira/browse/IOTDB-1224 Project: Apache IoTDB Issue Type: Improvement Components: Cluster Reporter: Chao Wang Assignee: Chao Wang Fix For: 0.12.0 Currently, in the aggregation query, the coordinator queries data from the data group in which the sequence is located, and then collects statistics. This increases the number of RPC times. We can push the statistics down to the data group for processing. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1223) Data type （INT32 and INT64）should support encoding method (REGULAR)
xiaozhihong created IOTDB-1223: -- Summary: Data type （INT32 and INT64）should support encoding method (REGULAR) Key: IOTDB-1223 URL: https://issues.apache.org/jira/browse/IOTDB-1223 Project: Apache IoTDB Issue Type: Bug Components: Server Affects Versions: 0.12.0 Environment: Linux System:192.168.31.50 Reporter: xiaozhihong Attachments: image-2021-03-12-14-25-58-940.png, image-2021-03-12-14-28-53-942.png, image-2021-03-12-14-29-25-564.png User Help Manual: !image-2021-03-12-14-25-58-940.png! Actual Result: INT32 and INT64 don't support REGULAR encoding method. Picture 1: !image-2021-03-12-14-28-53-942.png! Picture 2: !image-2021-03-12-14-29-25-564.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1222) The verification rule of LayerName does not match the actual
xiaozhihong created IOTDB-1222: -- Summary: The verification rule of LayerName does not match the actual Key: IOTDB-1222 URL: https://issues.apache.org/jira/browse/IOTDB-1222 Project: Apache IoTDB Issue Type: Bug Components: Client/CLI, Server Affects Versions: 0.12.0 Environment: 192.168.31.50 Linux System Reporter: xiaozhihong Attachments: image-2021-03-12-11-50-49-870.png, image-2021-03-12-13-42-11-945.png, image-2021-03-12-13-43-30-502.png IOTDB User Help Manual：Page23 !image-2021-03-12-11-50-49-870.png! Actual Results： Picture one !image-2021-03-12-13-42-11-945.png! Picture two !image-2021-03-12-13-43-30-502.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1221) Compaction module: chunk metadata lists returned by the getMeasurementChunkMetadataListMapIterator method are not lexicographically ordered by the measurement names
Steve Yurong Su created IOTDB-1221: -- Summary: Compaction module: chunk metadata lists returned by the getMeasurementChunkMetadataListMapIterator method are not lexicographically ordered by the measurement names Key: IOTDB-1221 URL: https://issues.apache.org/jira/browse/IOTDB-1221 Project: Apache IoTDB Issue Type: Bug Components: Core/Engine Reporter: Steve Yurong Su Fix For: 0.12.0 Chunk metadata lists returned by the *getMeasurementChunkMetadataListMapIterator* method are not lexicographically ordered by the measurement names, which will cause compaction errors. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1220) MQTT insert 10 rows ，elapsed time is 5s ，and the inserted row count is less than 10.
刘珍 created IOTDB-1220:
-
Summary: MQTT insert 10 rows ，elapsed time is 5s ，and the inserted
row count is less than 10.
Key: IOTDB-1220
URL: https://issues.apache.org/jira/browse/IOTDB-1220
Project: Apache IoTDB
Issue Type: Bug
Components: Server
Reporter: 刘珍
master branch.
commit id :5fcff40f2299caeb0c8a9ae42f68bc18ecf8fee7
## Usage
* Update configuration to enable MQTT service. (`enable_mqtt_service=true` in
iotdb-engine.properties)
* Launch the IoTDB server.
* Setup storage group `SET STORAGE GROUP TO root.sg` and create time timeseries
`CREATE TIMESERIES root.sg.d1.s1 WITH DATATYPE=DOUBLE, ENCODING=PLAIN`.
* Run `org.apache.iotdb.mqtt.MQTTClient` to run the mqtt client and send events
to server.
cat ../../src/main/java/org/apache/iotdb/mqtt/MQTTClient.java
package org.apache.iotdb.mqtt;
import org.fusesource.mqtt.client.BlockingConnection;
import org.fusesource.mqtt.client.MQTT;
import org.fusesource.mqtt.client.QoS;
import java.util.Random;
public class MQTTClient {
public static void main(String[] args) throws Exception {
MQTT mqtt = new MQTT();
mqtt.setHost("127.0.0.1", 1883);
mqtt.setUserName("root");
mqtt.setPassword("root");
BlockingConnection connection = mqtt.blockingConnection();
connection.connect();
Random random = new Random();
for (int i = 0; i < 10; i++) {
String payload =
String.format(
"{\n"
+ "\"device\":\"root.sg.d1\",\n"
+ "\"timestamp\":%d,\n"
+ "\"measurements\":[\"s1\"],\n"
+ "\"values\":[%f]\n"
+ "}",
System.currentTimeMillis(), random.nextDouble());
connection.publish("root.sg.d1.s1", payload.getBytes(), QoS.AT_LEAST_ONCE,
false);
}
connection.disconnect();
}
}
run time java -classpath ".:" org/apache/iotdb/mqtt/MQTTClient
2 times,the elapsed time:
real 0m5.573s
user 0m0.352s
sys 0m0.055s
real 0m0.584s
user 0m0.371s
sys 0m0.039s
IoTDB> select s1 from root.sg.d1;
+-+-+
| Time|root.sg.d1.s1|
+-+-+
|2021-03-12T11:52:50.687+08:00| 0.338776|
|2021-03-12T11:52:50.692+08:00| 0.250776|
|2021-03-12T11:52:50.694+08:00| 0.575861|
|2021-03-12T11:52:50.695+08:00| 0.229369|
|2021-03-12T11:52:50.696+08:00| 0.149007|
|2021-03-12T11:52:50.697+08:00| 0.182348|
|2021-03-12T11:52:50.698+08:00| 0.334755|
|2021-03-12T11:52:50.699+08:00| 0.757181|
|2021-03-12T11:53:02.649+08:00| 0.618037|
|2021-03-12T11:53:02.655+08:00| 0.789077|
|2021-03-12T11:53:02.656+08:00| 0.797554|
|2021-03-12T11:53:02.657+08:00| 0.660189|
|2021-03-12T11:53:02.658+08:00| 0.70841|
|2021-03-12T11:53:02.659+08:00| 0.09|
|2021-03-12T11:53:02.660+08:00| 0.130961|
+-+-+
Total line number = 15
It costs 0.014s
the "Total line number" should be 20.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1219) A potential NPE issue in ElasticSerializableRowRecordList#applyNewMemoryControlParameters
Steve Yurong Su created IOTDB-1219: -- Summary: A potential NPE issue in ElasticSerializableRowRecordList#applyNewMemoryControlParameters Key: IOTDB-1219 URL: https://issues.apache.org/jira/browse/IOTDB-1219 Project: Apache IoTDB Issue Type: Bug Components: Server Reporter: Steve Yurong Su Fix For: 0.12.0 The bug was reported by LGTM.com: [https://lgtm.com/projects/g/apache/iotdb/snapshot/ad13f1d09d54d7f98ab09a6b3572d64e1217644c/files/server/src/main/java/org/apache/iotdb/db/query/udf/datastructure/row/ElasticSerializableRowRecordList.java?sort=name&dir=ASC&mode=heatmap] Dereferencing a variable whose value may be 'null' may cause a 'NullPointerException'. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IOTDB-1218) System properties is not persist in cluster version
[ https://issues.apache.org/jira/browse/IOTDB-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Houliang Qi reassigned IOTDB-1218: -- Assignee: Houliang Qi > System properties is not persist in cluster version > --- > > Key: IOTDB-1218 > URL: https://issues.apache.org/jira/browse/IOTDB-1218 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Houliang Qi >Assignee: Houliang Qi >Priority: Major > Fix For: 0.12.0 > > > In the single-server mode, when we start one IoTDB instance, we can see that > the file _data/system/schema/system.properties_ contains some system > properties, however, when we set up the cluster, the file is lost. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1218) System properties is not persist in cluster version
Houliang Qi created IOTDB-1218: -- Summary: System properties is not persist in cluster version Key: IOTDB-1218 URL: https://issues.apache.org/jira/browse/IOTDB-1218 Project: Apache IoTDB Issue Type: Bug Reporter: Houliang Qi In the single-server mode, when we start one IoTDB instance, we can see that the file _data/system/schema/system.properties_ contains some system properties, however, when we set up the cluster, the file is lost. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1217) Trigger module: API, executor and management services
Steve Yurong Su created IOTDB-1217: -- Summary: Trigger module: API, executor and management services Key: IOTDB-1217 URL: https://issues.apache.org/jira/browse/IOTDB-1217 Project: Apache IoTDB Issue Type: Sub-task Components: Core/Engine Reporter: Steve Yurong Su Fix For: 0.12.0 Runtime core for trigger module, including: 1. user API 2. trigger executor 3. several management services -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1216) User with 'READ_TIMESERIES' privilege execute UDTF query , "Msg: 602: No permissions for this operation UDTF"
刘珍 created IOTDB-1216:
-
Summary: User with 'READ_TIMESERIES' privilege execute UDTF query
, "Msg: 602: No permissions for this operation UDTF"
Key: IOTDB-1216
URL: https://issues.apache.org/jira/browse/IOTDB-1216
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Engine
Reporter: 刘珍
Attachments: image-2021-03-11-17-45-21-522.png
master branch
commit id : 5fcff40f2299caeb0c8a9ae42f68bc18ecf8fee7
root connect iotdb:
SET STORAGE GROUP TO root.sg3;
CREATE TIMESERIES root.sg3.d1.s1 WITH DATATYPE=INT32, ENCODING=PLAIN;
CREATE TIMESERIES root.sg3.d1.s2 WITH DATATYPE=INT32, ENCODING=PLAIN;
INSERT INTO root.sg3.d1(timestamp, s1, s2) VALUES (10, -11, 11);
INSERT INTO root.sg3.d1(timestamp, s1, s2) VALUES (11, -12, 12);
INSERT INTO root.sg3.d1(timestamp, s1, s2) VALUES (12, -13, 13);
CREATE USER ln_write_user 'write_pwd'
grant user ln_write_user privileges 'READ_TIMESERIES' on root.sg3;
ln_write_user connect iotdb to execute UDTF(max) query:
select max(s1) from root.sg3.d1;
{color:#FF}Msg: 602: No permissions for this operation UDTF{color}
!image-2021-03-11-17-45-21-522.png!
Max.java :
package org.apache.iotdb.udf;
import org.apache.iotdb.db.query.udf.api.UDTF;
import org.apache.iotdb.db.query.udf.api.access.Row;
import org.apache.iotdb.db.query.udf.api.collector.PointCollector;
import org.apache.iotdb.db.query.udf.api.customizer.config.UDTFConfigurations;
import org.apache.iotdb.db.query.udf.api.customizer.parameter.UDFParameters;
import
org.apache.iotdb.db.query.udf.api.customizer.strategy.RowByRowAccessStrategy;
import org.apache.iotdb.tsfile.file.metadata.enums.TSDataType;
import java.io.IOException;
public class Max implements UDTF {
private Long time;
private int value;
@Override
public void beforeStart(UDFParameters parameters, UDTFConfigurations
configurations) {
configurations
.setOutputDataType(TSDataType.INT32)
.setAccessStrategy(new RowByRowAccessStrategy());
}
@Override
public void transform(Row row, PointCollector collector) {
int candidateValue = row.getInt(0);
if (time == null || value < candidateValue) {
time = row.getTime();
value = candidateValue;
}
}
@Override
public void terminate(PointCollector collector) throws IOException {
if (time != null) {
collector.putInt(time, value);
}
}
create function max as "org.apache.iotdb.udf.Max";
}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IOTDB-1215) Store aligned timeseries data in Memtable
[ https://issues.apache.org/jira/browse/IOTDB-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haonan Hou reassigned IOTDB-1215: - Assignee: Haonan Hou > Store aligned timeseries data in Memtable > - > > Key: IOTDB-1215 > URL: https://issues.apache.org/jira/browse/IOTDB-1215 > Project: Apache IoTDB > Issue Type: Sub-task >Reporter: Haonan Hou >Assignee: Haonan Hou >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1215) Store aligned timeseries data in Memtable
Haonan Hou created IOTDB-1215: - Summary: Store aligned timeseries data in Memtable Key: IOTDB-1215 URL: https://issues.apache.org/jira/browse/IOTDB-1215 Project: Apache IoTDB Issue Type: Sub-task Reporter: Haonan Hou -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1214) Flink-IoTDB document in English and Chinese
[ https://issues.apache.org/jira/browse/IOTDB-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17299424#comment-17299424 ] Steve Yurong Su commented on IOTDB-1214: [https://github.com/apache/iotdb/issues/2784|https://github.com/apache/iotdb/issues/2784] > Flink-IoTDB document in English and Chinese > --- > > Key: IOTDB-1214 > URL: https://issues.apache.org/jira/browse/IOTDB-1214 > Project: Apache IoTDB > Issue Type: Improvement > Components: site >Reporter: 赵家贝 >Priority: Minor > Labels: easy-fix > Fix For: master branch > > > Add Flink IoTDB documents to website and docs. The documents include English > and Chinese version -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1214) Flink-IoTDB document in English and Chinese
赵家贝 created IOTDB-1214: -- Summary: Flink-IoTDB document in English and Chinese Key: IOTDB-1214 URL: https://issues.apache.org/jira/browse/IOTDB-1214 Project: Apache IoTDB Issue Type: Improvement Components: site Reporter: 赵家贝 Fix For: master branch Add Flink IoTDB documents to website and docs. The documents include English and Chinese version -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1213) Flink-IoTDB document in English and Chinese
赵家贝 created IOTDB-1213: -- Summary: Flink-IoTDB document in English and Chinese Key: IOTDB-1213 URL: https://issues.apache.org/jira/browse/IOTDB-1213 Project: Apache IoTDB Issue Type: Improvement Components: site Reporter: 赵家贝 Fix For: master branch Add Flink-IoTDB documents to website and doc. The documents include English and Chinese version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1207) Open time partition causes stackoverflow
[ https://issues.apache.org/jira/browse/IOTDB-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17299399#comment-17299399 ] wangyanhong commented on IOTDB-1207: For reference https://github.com/apache/iotdb/pull/2809 > 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 >Priority: Major > Labels: pull-request-available > 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] [Created] (IOTDB-1212) select sin(not_exist) from root.sg1.d1; The error message is not right.
刘珍 created IOTDB-1212:
-
Summary: select sin(not_exist) from root.sg1.d1; The error
message is not right.
Key: IOTDB-1212
URL: https://issues.apache.org/jira/browse/IOTDB-1212
Project: Apache IoTDB
Issue Type: Bug
Components: Client/Java
Reporter: 刘珍
master branch
commit id : 5fcff40f2299caeb0c8a9ae42f68bc18ecf8fee7
SET STORAGE GROUP TO root.sg1;
CREATE TIMESERIES root.sg1.d1.s1 WITH DATATYPE=INT32, ENCODING=PLAIN;
CREATE TIMESERIES root.sg1.d1.s2 WITH DATATYPE=INT32, ENCODING=PLAIN;
INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (0, -1, 1);
INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (1, -2, 2);
INSERT INTO root.sg1.d1(timestamp, s1, s2) VALUES (2, -3, 3);
select sin(not_exist) from root.sg1.d1;
Msg: 411: Error occurred in query process: Error occurred during executing
UDTF#validate(UDFParameterValidator):
{color:#FF}org.apache.iotdb.db.query.udf.api.exception.UDFInputSeriesNumberNotValidException:
the number of the input series is not valid. expected: 1. actual: 0.{color}
{color:#FF}The error message is not right.{color}
{color:#ff}The actual is the input series does not exist.{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (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:all-tabpanel ] Houliang Qi reassigned IOTDB-1208: -- Assignee: Houliang Qi > [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 >Assignee: Houliang Qi >Priority: Major > Labels: pull-request-available > 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)
