[jira] [Created] (IOTDB-5384) add core_client_count_for_each_node_in_client_manager and max_client_count_for_each_node_in_client_manager parameters for confignode and datanode
Xinyu Tan created IOTDB-5384: Summary: add core_client_count_for_each_node_in_client_manager and max_client_count_for_each_node_in_client_manager parameters for confignode and datanode Key: IOTDB-5384 URL: https://issues.apache.org/jira/browse/IOTDB-5384 Project: Apache IoTDB Issue Type: Improvement Reporter: Xinyu Tan Assignee: Xinyu Tan Two parameters are added to confignode.properties: * cn_core_client_count_for_each_node_in_client_manager * cn_max_client_count_for_each_node_in_client_manager Two parameters are added to datanode.properties: * dn_core_client_count_for_each_node_in_client_manager * dn_max_client_count_for_each_node_in_client_manager This issue also causes all clientManager initializations to use these parameters, as well as updating the documentation -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5383) [confignode]start-confignode fail with NPE
changxue created IOTDB-5383:
---
Summary: [confignode]start-confignode fail with NPE
Key: IOTDB-5383
URL: https://issues.apache.org/jira/browse/IOTDB-5383
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Server
Affects Versions: 1.0.1
Reporter: changxue
Assignee: Xinyu Tan
[confignode]start-confignode fail with NPE
reproduction:
1. config_node_ratis_snapshot_trigger_threshold=30 append in
iotdb-common.properties
2. start 3C3D cluster
expect: start successfully
actual result:
2C3D start successfully but it failed with NPE when start the third confignode
{code}
IoTDB> show cluster
+--+--+---+---++
|NodeID| NodeType| Status|InternalAddress|InternalPort|
+--+--+---+---++
| 0|ConfigNode|Running| 172.20.70.44| 10710|
| 2|ConfigNode|Running| 172.20.70.45| 10710|
| 1| DataNode|Running| 172.20.70.44| 10730|
| 3| DataNode|Running| 172.20.70.45| 10730|
| 5| DataNode|Unknown| 172.20.70.46| 10730|
+--+--+---+---++
{code}
{code}
2023-01-07 14:42:11,745 [grpc-default-executor-0] INFO
o.a.r.g.s.GrpcServerProtocolService$ServerRequestStreamObserver:143 - 8:
Completed INSTALL_SNAPSHOT, lastRequest:
0->8#0-t1,chunk:ba310edb-b921-452d-8023-4ef2ad4f51f9,8
2023-01-07 14:42:11,746 [8@group--StateMachineUpdater] ERROR
o.a.r.s.i.StateMachineUpdater:194 - 8@group--StateMachineUpdater
caught a Throwable.
java.lang.NullPointerException: snapshot == null
at java.util.Objects.requireNonNull(Objects.java:228)
at
org.apache.ratis.server.impl.StateMachineUpdater.reload(StateMachineUpdater.java:219)
at
org.apache.ratis.server.impl.StateMachineUpdater.run(StateMachineUpdater.java:179)
at java.lang.Thread.run(Thread.java:748)
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-5382) Support DIFF as built-in scalar function in IoTDB
Yuan Tian created IOTDB-5382: Summary: Support DIFF as built-in scalar function in IoTDB Key: IOTDB-5382 URL: https://issues.apache.org/jira/browse/IOTDB-5382 Project: Apache IoTDB Issue Type: New Feature Components: Core/Query Reporter: Yuan Tian Assignee: 李伟豪 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5381) [datanode]datanode would use the environment variable of IOTDB_HOME, rather than the directory where the start-datanode.sh is
[
https://issues.apache.org/jira/browse/IOTDB-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haonan Hou reassigned IOTDB-5381:
-
Assignee: Gaofei Cao (was: Haonan Hou)
> [datanode]datanode would use the environment variable of IOTDB_HOME, rather
> than the directory where the start-datanode.sh is
> -
>
> Key: IOTDB-5381
> URL: https://issues.apache.org/jira/browse/IOTDB-5381
> Project: Apache IoTDB
> Issue Type: Bug
>Reporter: changxue
>Assignee: Gaofei Cao
>Priority: Major
> Attachments: image-2023-01-06-17-25-12-894.png,
> image-2023-01-06-17-27-25-078.png
>
>
> datanode would use the environment variable of IOTDB_HOME, rather than the
> directory where the start-datanode.sh is.
> reproduction:
> 1. start 3C3D cluster with nodes 44, 45, 46
> 2. stop confignode and datanode of node 44
> 3. start a 1C1D in another directory with the default configurations,
> directory is different from $IOTDB_HOME.
> actual result:
> 1. start 1C1D , but the logs of datanode write to $IOTDB_HOME/logs, rather
> than the directory where the start-datanode.sh is.
>
> !image-2023-01-06-17-25-12-894.png|width=600!
> log_datanode_error.log
> {code}
> 2023-01-06 17:15:19,324 [main] ERROR o.a.i.db.service.DataNode:255 - Cannot
> pull system configurations from ConfigNode-leader after 10 retries
> 2023-01-06 17:15:19,329 [main] ERROR o.a.i.db.service.DataNode:177 - Fail to
> start server
> org.apache.iotdb.commons.exception.StartupException: Cannot pull system
> configurations from ConfigNode-leader
> at
> org.apache.iotdb.db.service.DataNode.pullAndCheckSystemConfigurations(DataNode.java:258)
> at org.apache.iotdb.db.service.DataNode.doAddNode(DataNode.java:154)
> at
> org.apache.iotdb.db.service.DataNodeServerCommandLine.run(DataNodeServerCommandLine.java:79)
> at
> org.apache.iotdb.commons.ServerCommandLine.doMain(ServerCommandLine.java:58)
> at org.apache.iotdb.db.service.DataNode.main(DataNode.java:141)
> {code}
> log_datanode_warn.log
> {code}
> 023-01-06 17:14:54,315 [main] WARN o.a.i.db.service.DataNode:237 - Cannot
> pull system configurations from ConfigNode-leader, because: Fail to connect
> to any config node. Please check status of ConfigNodes
> 2023-01-06 17:14:59,316 [main] WARN o.a.i.d.c.ConfigNodeClient:268 - The
> current node may have been down TEndPoint(ip:iotdb-44, port:10710),try next
> node
> {code}
> 注意IP， 1C1D 我使用的是默认配置，所以它的IP应该是127.0.0.1，为什么会是iotdb-44内，因为它使用的是
> $IOTDB_HOME路径下的配置，日志也写在了$IOTDB_HOME路径下。这是不对的。应该使用我启动命令所在的文件夹。
> ps: confignode没有这个问题。
> 2. start-cli.sh -h iotdb-45 -e "show cluster", the result is correct.
> !image-2023-01-06-17-27-25-078.png|width=600!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-5381) [datanode]datanode would use the environment variable of IOTDB_HOME, rather than the directory where the start-datanode.sh is
changxue created IOTDB-5381:
---
Summary: [datanode]datanode would use the environment variable of
IOTDB_HOME, rather than the directory where the start-datanode.sh is
Key: IOTDB-5381
URL: https://issues.apache.org/jira/browse/IOTDB-5381
Project: Apache IoTDB
Issue Type: Bug
Reporter: changxue
Assignee: Haonan Hou
Attachments: image-2023-01-06-17-25-12-894.png,
image-2023-01-06-17-27-25-078.png
datanode would use the environment variable of IOTDB_HOME, rather than the
directory where the start-datanode.sh is.
reproduction:
1. start 3C3D cluster with nodes 44, 45, 46
2. stop confignode and datanode of node 44
3. start a 1C1D in another directory with the default configurations, directory
is different from $IOTDB_HOME.
actual result:
1. start 1C1D , but the logs of datanode write to $IOTDB_HOME/logs, rather than
the directory where the start-datanode.sh is.
!image-2023-01-06-17-25-12-894.png|width=600!
log_datanode_error.log
{code}
2023-01-06 17:15:19,324 [main] ERROR o.a.i.db.service.DataNode:255 - Cannot
pull system configurations from ConfigNode-leader after 10 retries
2023-01-06 17:15:19,329 [main] ERROR o.a.i.db.service.DataNode:177 - Fail to
start server
org.apache.iotdb.commons.exception.StartupException: Cannot pull system
configurations from ConfigNode-leader
at
org.apache.iotdb.db.service.DataNode.pullAndCheckSystemConfigurations(DataNode.java:258)
at org.apache.iotdb.db.service.DataNode.doAddNode(DataNode.java:154)
at
org.apache.iotdb.db.service.DataNodeServerCommandLine.run(DataNodeServerCommandLine.java:79)
at
org.apache.iotdb.commons.ServerCommandLine.doMain(ServerCommandLine.java:58)
at org.apache.iotdb.db.service.DataNode.main(DataNode.java:141)
{code}
log_datanode_warn.log
{code}
023-01-06 17:14:54,315 [main] WARN o.a.i.db.service.DataNode:237 - Cannot pull
system configurations from ConfigNode-leader, because: Fail to connect to any
config node. Please check status of ConfigNodes
2023-01-06 17:14:59,316 [main] WARN o.a.i.d.c.ConfigNodeClient:268 - The
current node may have been down TEndPoint(ip:iotdb-44, port:10710),try next node
{code}
注意IP， 1C1D 我使用的是默认配置，所以它的IP应该是127.0.0.1，为什么会是iotdb-44内，因为它使用的是
$IOTDB_HOME路径下的配置，日志也写在了$IOTDB_HOME路径下。这是不对的。应该使用我启动命令所在的文件夹。
ps: confignode没有这个问题。
2. start-cli.sh -h iotdb-45 -e "show cluster", the result is correct.
!image-2023-01-06-17-27-25-078.png|width=600!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-5380) Dropwizard failed to create gauge metrics
Eric Pai created IOTDB-5380: --- Summary: Dropwizard failed to create gauge metrics Key: IOTDB-5380 URL: https://issues.apache.org/jira/browse/IOTDB-5380 Project: Apache IoTDB Issue Type: Bug Components: Others Affects Versions: 1.0.0 Reporter: Eric Pai Assignee: Eric Pai Fix For: master branch, 1.0.1 Attachments: image-2023-01-06-16-28-59-399.png !image-2023-01-06-16-28-59-399.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5380) Dropwizard failed to create gauge metrics
[ https://issues.apache.org/jira/browse/IOTDB-5380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Pai reassigned IOTDB-5380: --- Assignee: Hongyin Zhang (was: Eric Pai) > Dropwizard failed to create gauge metrics > -- > > Key: IOTDB-5380 > URL: https://issues.apache.org/jira/browse/IOTDB-5380 > Project: Apache IoTDB > Issue Type: Bug > Components: Others >Affects Versions: 1.0.0 >Reporter: Eric Pai >Assignee: Hongyin Zhang >Priority: Major > Fix For: master branch, 1.0.1 > > Attachments: image-2023-01-06-16-28-59-399.png > > > !image-2023-01-06-16-28-59-399.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-5235) [SchemaFile] support props
[ https://issues.apache.org/jira/browse/IOTDB-5235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yanze chen reassigned IOTDB-5235: - Assignee: ZhaoXin (was: yanze chen) > [SchemaFile] support props > -- > > Key: IOTDB-5235 > URL: https://issues.apache.org/jira/browse/IOTDB-5235 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: yanze chen >Assignee: ZhaoXin >Priority: Major > > SchemaFile need to support props. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IOTDB-4960) [SchemaFile] Query large amounts of metadata throw ClosedChannelException
[
https://issues.apache.org/jira/browse/IOTDB-4960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yanze chen reassigned IOTDB-4960:
-
Assignee: ZhaoXin (was: yanze chen)
> [SchemaFile] Query large amounts of metadata throw ClosedChannelException
> -
>
> Key: IOTDB-4960
> URL: https://issues.apache.org/jira/browse/IOTDB-4960
> Project: Apache IoTDB
> Issue Type: Bug
>Reporter: yanze chen
>Assignee: ZhaoXin
>Priority: Major
> Attachments: image-2022-11-16-15-29-18-436.png,
> image-2022-11-16-16-01-50-022.png
>
>
> reproduce:
> 1C1D Schema_File mode 128G for DataNode
>
> run benchmark with config:
> {*}DEVICE_NUMBER{*}=5000
> {*}SENSOR_NUMBER{*}=2
> {*}CLIENT_NUMBER{*}=5
> {*}GROUP_NUMBER{*}=10
> {*}BATCH_SIZE_PER_WRITE{*}=0
> {*}LOOP{*}=1
> {*}VECTOR{*}=true
>
> execute SQL:
> count timeseries root.**
>
> !image-2022-11-16-15-29-18-436.png|width=881,height=596!
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-5379) Prometheus API reports timer metrics in nanoseconds but the names are suffixed with _second
Eric Pai created IOTDB-5379: --- Summary: Prometheus API reports timer metrics in nanoseconds but the names are suffixed with _second Key: IOTDB-5379 URL: https://issues.apache.org/jira/browse/IOTDB-5379 Project: Apache IoTDB Issue Type: Bug Components: Core/Others Affects Versions: 1.0.0 Reporter: Eric Pai Assignee: Eric Pai Fix For: master branch, 1.0.1 The timeer metrics whose name end with '_second' should report values in seconds unit. However, it reports in a nanosecond one, which will confuse our users. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5359) Use decorator pattern to refactor SchemaTreeVisitorWithLimitOffset
[ https://issues.apache.org/jira/browse/IOTDB-5359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17655289#comment-17655289 ] yanze chen commented on IOTDB-5359: --- https://github.com/apache/iotdb/pull/8721 > Use decorator pattern to refactor SchemaTreeVisitorWithLimitOffset > -- > > Key: IOTDB-5359 > URL: https://issues.apache.org/jira/browse/IOTDB-5359 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: yanze chen >Assignee: yanze chen >Priority: Major > > Use decorator pattern to refactor SchemaTreeVisitorWithLimitOffset -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5360) Release node and iterator in AbstractTreeVisitor
[ https://issues.apache.org/jira/browse/IOTDB-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17655288#comment-17655288 ] yanze chen commented on IOTDB-5360: --- https://github.com/apache/iotdb/pull/8721 > Release node and iterator in AbstractTreeVisitor > > > Key: IOTDB-5360 > URL: https://issues.apache.org/jira/browse/IOTDB-5360 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: yanze chen >Assignee: yanze chen >Priority: Major > > To support pin and unpin in SchemaFile mode, AbstractTreeVisitor should > release node and iterator after using. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-5342) Separate filtering and business logic in AbstractTreeVisitor
[ https://issues.apache.org/jira/browse/IOTDB-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17655287#comment-17655287 ] yanze chen commented on IOTDB-5342: --- https://github.com/apache/iotdb/pull/8721 > Separate filtering and business logic in AbstractTreeVisitor > > > Key: IOTDB-5342 > URL: https://issues.apache.org/jira/browse/IOTDB-5342 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: yanze chen >Assignee: yanze chen >Priority: Major > Labels: pull-request-available > > Separate filtering and business logic in AbstractTreeVisitor -- This message was sent by Atlassian Jira (v8.20.10#820010)
