[jira] [Created] (IOTDB-2125) Create a session,open 2 “pool-14-IoTDB-RPC-Client” threads

2021-12-07 Thread Jira
刘珍 created IOTDB-2125:
-

 Summary: Create a session,open 2 “pool-14-IoTDB-RPC-Client” threads
 Key: IOTDB-2125
 URL: https://issues.apache.org/jira/browse/IOTDB-2125
 Project: Apache IoTDB
  Issue Type: Bug
  Components: Core/Server
Reporter: 刘珍
 Attachments: config.properties

rel/0.12  *strong text*
Benchmark connects to IoTDB,and opens 2 “pool-14-IoTDB-RPC-Client” threads per 
session.
cli doesn't have this problem.

1. Run benchmark (config.properties)
CLIENT_NUMBER={color:#DE350B}20{color}
2. jstack iotdb_pid > a.out

grep "pool-14-IoTDB-RPC-Client" a.out |wc -l
{color:#DE350B}*40*{color}






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (IOTDB-2124) After enable_last_cache is disabled, the filtering condition does not take effect in cluster

2021-12-07 Thread Chao Wang (Jira)
Chao Wang created IOTDB-2124:


 Summary: After enable_last_cache is disabled, the filtering 
condition does not take effect in cluster
 Key: IOTDB-2124
 URL: https://issues.apache.org/jira/browse/IOTDB-2124
 Project: Apache IoTDB
  Issue Type: Bug
  Components: Core/Cluster
Affects Versions: 0.12.3
Reporter: Chao Wang
Assignee: Chao Wang
 Fix For: 0.13.0, 0.12.4


After enable_last_cache is disabled, the filter criteria are not pushed to the 
remote node. As a result, the query result is incorrect.

5 node , 3 rep in cluster 

 1. enable_last_cache = false

2. insert into root.sg1.d1(time,s1) values(1,1);

3. flush;

4. select last s1 from root.sg1.d1 where time > 1;

the query result is incorrect.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Assigned] (IOTDB-2122) MQTT / REST module migrate to the correct path

2021-12-07 Thread Steve Yurong Su (Jira)


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

Steve Yurong Su reassigned IOTDB-2122:
--

Assignee: xieqijun

> MQTT / REST module migrate to the correct path
> --
>
> Key: IOTDB-2122
> URL: https://issues.apache.org/jira/browse/IOTDB-2122
> Project: Apache IoTDB
>  Issue Type: Improvement
>Reporter: xieqijun
>Assignee: xieqijun
>Priority: Major
>
> influxdb service module is now under the path of org.apache.iotdb.db.protocol 
> ,
> and mqtt and rest service module is now under the path of org.apache.iotdb.db.
> We should put mqtt and rest under this path like influxdb, which will be 
> clearer.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (IOTDB-2123) Accelerate recovery process

2021-12-07 Thread Haonan Hou (Jira)
Haonan Hou created IOTDB-2123:
-

 Summary: Accelerate recovery process
 Key: IOTDB-2123
 URL: https://issues.apache.org/jira/browse/IOTDB-2123
 Project: Apache IoTDB
  Issue Type: Improvement
  Components: Core/Engine
Reporter: Haonan Hou






--
This message was sent by Atlassian Jira
(v8.20.1#820001)


[jira] [Created] (IOTDB-2122) MQTT / REST module migrate to the correct path

2021-12-07 Thread xieqijun (Jira)
xieqijun created IOTDB-2122:
---

 Summary: MQTT / REST module migrate to the correct path
 Key: IOTDB-2122
 URL: https://issues.apache.org/jira/browse/IOTDB-2122
 Project: Apache IoTDB
  Issue Type: Improvement
Reporter: xieqijun


influxdb service module is now under the path of org.apache.iotdb.db.protocol ,
and mqtt and rest service module is now under the path of org.apache.iotdb.db.
We should put mqtt and rest under this path like influxdb, which will be 
clearer.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)