[jira] [Commented] (IOTDB-6231) SchemaCache supports precise eviction
[ https://issues.apache.org/jira/browse/IOTDB-6231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17781393#comment-17781393 ] yanze chen commented on IOTDB-6231: --- https://github.com/apache/iotdb/pull/11226 > SchemaCache supports precise eviction > - > > Key: IOTDB-6231 > URL: https://issues.apache.org/jira/browse/IOTDB-6231 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: yanze chen >Assignee: yanze chen >Priority: Major > > Now once deletion of data occurs, it clears all SchemaCache on the DataNode > it is on. > Optimised to delete entries in the SchemaCache as accurately as possible if > the device does not contain wildcards. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6231) SchemaCache supports precise eviction
yanze chen created IOTDB-6231: - Summary: SchemaCache supports precise eviction Key: IOTDB-6231 URL: https://issues.apache.org/jira/browse/IOTDB-6231 Project: Apache IoTDB Issue Type: Improvement Reporter: yanze chen Assignee: yanze chen Now once deletion of data occurs, it clears all SchemaCache on the DataNode it is on. Optimised to delete entries in the SchemaCache as accurately as possible if the device does not contain wildcards. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6230) Add HEAPDUMP configuration in datanode-env.sh
Yuan Tian created IOTDB-6230:
Summary: Add HEAPDUMP configuration in datanode-env.sh
Key: IOTDB-6230
URL: https://issues.apache.org/jira/browse/IOTDB-6230
Project: Apache IoTDB
Issue Type: Improvement
Reporter: Yuan Tian
Assignee: Yuan Tian
add HeapDump configuration in datanode-env to let DBA can quickly add
{{{}-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath={}}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IOTDB-6229) Add java doc in SessionDataSet to guide user use DataIterator
Yuan Tian created IOTDB-6229: Summary: Add java doc in SessionDataSet to guide user use DataIterator Key: IOTDB-6229 URL: https://issues.apache.org/jira/browse/IOTDB-6229 Project: Apache IoTDB Issue Type: Improvement Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian add java doc for SessionDataSet.next(), and recommend users to use SessionDataSet.DataIterator to iterate their result set if possible -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6228) Improve the high availability of IoTDB
Yuan Tian created IOTDB-6228: Summary: Improve the high availability of IoTDB Key: IOTDB-6228 URL: https://issues.apache.org/jira/browse/IOTDB-6228 Project: Apache IoTDB Issue Type: Improvement Components: Core/Engine Reporter: Yuan Tian Assignee: Yuan Tian For 3C3D 2 replicas or 3 replicas dataregion, if we kill one datanode, client should keep inserting data successfully without any error. However, currently, there is no retry logic in dispatch for write, so if the leader of one DataRegionGroup is down, the dispatch phase will fail and will return a 302 status code to Session, and meet this kind of StatusCode, Session won't retry this write request, it will throw this exception to the upper layer. You will get the error msg like the following: !https://user-images.githubusercontent.com/16079446/277609629-c0987905-5816-4daa-a664-0503c0edac12.png! more details about this improvement can be found in this feishu doc([https://timechor.feishu.cn/docx/WuVJdNpGOowEGIxvaOlcwt9mngg]) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6227) Made Ratis linearizable read retriable
Song Ziyang created IOTDB-6227: -- Summary: Made Ratis linearizable read retriable Key: IOTDB-6227 URL: https://issues.apache.org/jira/browse/IOTDB-6227 Project: Apache IoTDB Issue Type: Improvement Reporter: Song Ziyang Assignee: Song Ziyang Currently if the cluster leader is not elected, the linearizable read will return failure immediately. We should retry on that condition. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6226) Fix the problem of inaccurate GC monitor detection at the beginning and adjusting the alert threshold
Peng Junzhi created IOTDB-6226: -- Summary: Fix the problem of inaccurate GC monitor detection at the beginning and adjusting the alert threshold Key: IOTDB-6226 URL: https://issues.apache.org/jira/browse/IOTDB-6226 Project: Apache IoTDB Issue Type: Improvement Reporter: Peng Junzhi When the Metric Service starts after the jvm, the gc time before the Metric Service is started will also be counted, causing the GC percentage within the initial time window to be significantly higher than expected -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-6225) Support bacth process interface in UDF api
Yuan Tian created IOTDB-6225: Summary: Support bacth process interface in UDF api Key: IOTDB-6225 URL: https://issues.apache.org/jira/browse/IOTDB-6225 Project: Apache IoTDB Issue Type: New Feature Components: Core/Query Reporter: Yuan Tian Assignee: Yuan Tian We need to support bacth process interface in UDF api which can directly process TsBlock instead of converting TsBlock to RowRecord row by row. -- This message was sent by Atlassian Jira (v8.20.10#820010)
