[jira] [Assigned] (IOTDB-4521) ERROR o.a.t.s.AbstractNonblockingServer$FrameBuffer:356 - Read a frame size of 562223808, which is bigger than the maximum allowable buffer size for ALL connections
[
https://issues.apache.org/jira/browse/IOTDB-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jialin Qiao reassigned IOTDB-4521:
--
Assignee: Jinrui Zhang (was: Jialin Qiao)
> ERROR o.a.t.s.AbstractNonblockingServer$FrameBuffer:356 - Read a frame size
> of 562223808, which is bigger than the maximum allowable buffer size for ALL
> connections
>
>
> Key: IOTDB-4521
> URL: https://issues.apache.org/jira/browse/IOTDB-4521
> Project: Apache IoTDB
> Issue Type: Bug
> Components: mpp-cluster
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: 刘珍
>Assignee: Jinrui Zhang
>Priority: Major
> Attachments: image-2022-09-26-10-04-30-709.png,
> image-2022-09-26-10-05-57-896.png, ip72_datanode_logs.tar.gz, more_ts.conf
>
>
> m_0922_0d65058
> 3副本3C3D
> schemaregion ：RatisConsensus
> dataregion ：MultiLeaderConsensus
> DEVICE_NUMBER=600
> SENSOR_NUMBER=5
> CLIENT_NUMBER=100
> （5万dev，600sensor /dev 全部数据写入成功）600dev，5万序列/dev，写入 datanode error ：
> 2022-09-24 00:00:02,666
> [pool-25-IoTDB-ClientRPC-Processor-142$20220923_155931_09082_3.1.0] ERROR
> {color:#DE350B}*o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:179 -
> null*{color}
> 2022-09-24 00:00:02,685 [Thread-18] ERROR
> {color:#DE350B}*o.a.t.s.AbstractNonblockingServer$FrameBuffer:356 - Read a
> frame size of 722859150, which is bigger than the maximum allowable buffer
> size for ALL connections.*{color}
> 2022-09-24 00:00:02,726
> [pool-25-IoTDB-ClientRPC-Processor-83$20220923_155931_09083_3.1.0] ERROR
> o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:179 - null
> 2022-09-24 00:00:03,501
> [pool-25-IoTDB-ClientRPC-Processor-23$20220923_155932_09084_3.1.0] ERROR
> o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:179 - null
> 2022-09-24 00:00:05,059
> [pool-25-IoTDB-ClientRPC-Processor-113$20220923_155934_09085_3.1.0] ERROR
> o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:179 - null
> 2022-09-24 00:00:05,138 [Thread-18] ERROR
> o.a.t.s.AbstractNonblockingServer$FrameBuffer:356 - Read a frame size of
> 803176833, which is bigger than the maximum allowable buffer size for ALL
> connections.
> 2022-09-24 00:00:07,448
> [pool-25-IoTDB-ClientRPC-Processor-47$20220923_155935_09086_3.1.0] ERROR
> o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:179 - null
> 2022-09-24 00:00:08,220
> [pool-25-IoTDB-ClientRPC-Processor-59$20220923_155937_09087_3.1.0] ERROR
> o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:179 - null
> 2022-09-24 00:00:09,320 [Thread-18] ERROR
> o.a.t.s.AbstractNonblockingServer$FrameBuffer:356 - Read a frame size of
> 669314043, which is bigger than the maximum allowable buffer size for ALL
> connections.
> 2022-09-24 00:00:12,375 [Thread-18] ERROR
> o.a.t.s.AbstractNonblockingServer$FrameBuffer:356 - Read a frame size of
> 803176825, which is bigger than the maximum allowable buffer size for ALL
> connections.
> 测试环境
> 1. 192.168.10.72/73/74 48CPU 384GB
> bm在71
> ConfigNode
> MAX_HEAP_SIZE="8G"
> schema_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus
> data_region_consensus_protocol_class=org.apache.iotdb.consensus.multileader.MultiLeaderConsensus
> schema_replication_factor=3
> data_replication_factor=3
> connection_timeout_ms=3600
> DataNode
> MAX_HEAP_SIZE="256G"
> MAX_DIRECT_MEMORY_SIZE="32G"
> connection_timeout_ms=3600
> max_connection_for_internal_service=300
> enable_timed_flush_seq_memtable=true
> seq_memtable_flush_interval_in_ms=360
> seq_memtable_flush_check_interval_in_ms=60
> enable_timed_flush_unseq_memtable=true
> unseq_memtable_flush_interval_in_ms=360
> unseq_memtable_flush_check_interval_in_ms=60
> max_waiting_time_when_insert_blocked=360
> query_timeout_threshold=3600
> 2. bm配置见附件
> 600dev，5万序列/dev, bm结果
> !image-2022-09-26-10-04-30-709.png!
> 5万dev，600sensor 全部数据写入成功
> !image-2022-09-26-10-05-57-896.png!
> 3. ip72 datanode log见附件
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IOTDB-4540) [cluster]Set ratis protocol does not generate mlog
[
https://issues.apache.org/jira/browse/IOTDB-4540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jialin Qiao reassigned IOTDB-4540:
--
Assignee: Yukun Zhou (was: Jialin Qiao)
> [cluster]Set ratis protocol does not generate mlog
> --
>
> Key: IOTDB-4540
> URL: https://issues.apache.org/jira/browse/IOTDB-4540
> Project: Apache IoTDB
> Issue Type: Improvement
> Components: mpp-cluster, Tools/Others
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: xiaozhihong
>Assignee: Yukun Zhou
>Priority: Major
> Attachments: image-2022-09-27-13-54-56-701.png,
> image-2022-09-27-15-03-41-005.png
>
>
> Set ratis protocol does not generate mlog, so that can not parse the
> specified metadata file.
> Step 1: Modify SchemaRegion consensus protocol type in
> iotdb-confignode.properties.
> {code:java}
> schema_region_consensus_protocol_class=org.apache.iotdb.consensus.ratis.RatisConsensus{code}
> Step 2: Start 3C3D
> Step 3: Execute SQL in CLI
> But can't generate mLog. Like this:
> !image-2022-09-27-13-54-56-701.png|width=528,height=134!
> Modify parameters in iotdb-confignode.properties:
> {code:java}
> schema_region_consensus_protocol_class=org.apache.iotdb.consensus.standalone.StandAloneConsensus
> {code}
> Like this can generate mlog
> !image-2022-09-27-15-03-41-005.png|width=530,height=237!
> Therefore, it is necessary to add a description in the MLogParser-Tool module
> of the UserGuide.
> refer to:
> https://iotdb.apache.org/zh/UserGuide/Master/Maintenance-Tools/MLogParser-Tool.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-4572) Support order by time in align by device query
Jialin Qiao created IOTDB-4572: -- Summary: Support order by time in align by device query Key: IOTDB-4572 URL: https://issues.apache.org/jira/browse/IOTDB-4572 Project: Apache IoTDB Issue Type: New Feature Reporter: Jialin Qiao Currently, we return results device by device in align by device query. In some cases, users would like to sort all results by time then return. E.g., select s1 from root.sg.d align by device [order by time acs/desc] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4571) Add javadoc and example in IPartitionFetcher.
张洪胤 created IOTDB-4571: -- Summary: Add javadoc and example in IPartitionFetcher. Key: IOTDB-4571 URL: https://issues.apache.org/jira/browse/IOTDB-4571 Project: Apache IoTDB Issue Type: Improvement Reporter: 张洪胤 Assignee: 张洪胤 Add javadoc and example in IPartitionFetcher. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-4517) [Atmos]Cross_space and unseq_space compaction are slower at common timeseries and template timeseries
[ https://issues.apache.org/jira/browse/IOTDB-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17612824#comment-17612824 ] FengQingxin commented on IOTDB-4517: !image-2022-10-05-08-01-42-440.png|width=578,height=281! 性能检测发现有恢复现象，但是跨空间合并普通时间序列原本耗时低于对齐时间序列，目前却高于了对齐时间序列的合并耗时；因此还有部分优化空间。 > [Atmos]Cross_space and unseq_space compaction are slower at common timeseries > and template timeseries > - > > Key: IOTDB-4517 > URL: https://issues.apache.org/jira/browse/IOTDB-4517 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Compaction >Affects Versions: 0.14.0-SNAPSHOT >Reporter: FengQingxin >Assignee: Liuxuxin >Priority: Major > Labels: pull-request-available > Fix For: 0.14.0 > > Attachments: image-2022-09-23-17-42-33-888.png, > image-2022-10-05-08-01-42-440.png > > > [Atmos]Cross_space and unseq_space compaction are slower at common timeseries > and template timeseries > [http://111.202.73.147:13000/d/ta84fXYnz/atm-biao-zhun-da-qi-ya-huan-jing-he-bing?orgId=1] > !image-2022-09-23-17-42-33-888.png|width=781,height=380! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-4570) Move SerializationRunTimeException to node-commons
yanze chen created IOTDB-4570: - Summary: Move SerializationRunTimeException to node-commons Key: IOTDB-4570 URL: https://issues.apache.org/jira/browse/IOTDB-4570 Project: Apache IoTDB Issue Type: Improvement Reporter: yanze chen Assignee: yanze chen -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IOTDB-4551) NPE while fetching schema
[ https://issues.apache.org/jira/browse/IOTDB-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17612498#comment-17612498 ] Yukun Zhou commented on IOTDB-4551: --- https://github.com/apache/iotdb/pull/7511 > NPE while fetching schema > - > > Key: IOTDB-4551 > URL: https://issues.apache.org/jira/browse/IOTDB-4551 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Yuan Tian >Assignee: Yukun Zhou >Priority: Major > Attachments: image-2022-09-28-15-22-14-813.png > > > sql is: > SELECT s_321, s_15, s_176, s_747, s_701, s_588, s_549, s_748, s_291, s_363 > FROM root.test.g_0.d_1846 WHERE time >= 166187520 AND time <= > 166187880 > !image-2022-09-28-15-22-14-813.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
