[GitHub] [iotdb-client-go] HTHou merged pull request #76: Bump github.com/stretchr/testify from 1.8.1 to 1.8.2
HTHou merged PR #76: URL: https://github.com/apache/iotdb-client-go/pull/76 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (IOTDB-5589) [ compaction ] The "IoTDB-Compaction_Schedule" thread count needs to be controlled
刘珍 created IOTDB-5589: - Summary: [ compaction ] The "IoTDB-Compaction_Schedule" thread count needs to be controlled Key: IOTDB-5589 URL: https://issues.apache.org/jira/browse/IOTDB-5589 Project: Apache IoTDB Issue Type: Improvement Components: mpp-cluster Reporter: 刘珍 Assignee: 周沛辰 master_a3869ec_opt Each time partition opens a "IoTDB-Compaction_Schedule" thread，it's not a good design. 示例： 在192.168.10.68 （72CPU) , start-standalone.sh启动单节点集群，运行附件中的脚本，生成72个dataregion，每个dataregion 下目前只有1个时间分区，所以当前"IoTDB-Compaction_Schedule"线程数有72个，随着时间分区的增加，这个线程也会增大，需要控制，它的主要作用是用来选择合并文件，是比较快的操作，没必要开这么多。 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (IOTDB-5516) [ drop database + create metadata ] There are too many timeseries in memory
[ https://issues.apache.org/jira/browse/IOTDB-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 刘珍 reopened IOTDB-5516: --- master_0227_2bc29bb 运行loop_exec_5516.sh ，10次创建的devices数分别为： 20530 6814 2261 712 274 125 16 0 100 0 > [ drop database + create metadata ] There are too many timeseries in memory > --- > > Key: IOTDB-5516 > URL: https://issues.apache.org/jira/browse/IOTDB-5516 > Project: Apache IoTDB > Issue Type: Bug > Components: mpp-cluster >Affects Versions: 1.1.0-SNAPSHOT >Reporter: 刘珍 >Assignee: Yukun Zhou >Priority: Major > Labels: pull-request-available > Attachments: iotdb.sh, iotdb_5516.conf, loop_exec_5516.sh, startup.sh > > > master 0210 8757400 > drop 所有database后，再创建元数据，失败，报错： > There are too many timeseries in memory > 1. 创建元数据 > 2. drop database root.** > 3.创建元数据 > 2023-02-10 16:25:11,985 > [pool-25-IoTDB-ClientRPC-Processor-698$20230210_082511_65380_3.1.0] WARN > o.a.i.d.m.p.s.FragmentInstanceDispatcherImpl:199 - dispatch write failed. > status: TSStatus(code:302, subStatus:[TSStatus(code:502, message:There are > too many timeseries in memory, please increase MAX_HEAP_SIZE in > datanode-env.sh/bat, restart and create timeseries again.), -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [iotdb-client-go] fuliwen opened a new pull request, #77: Update README.md
fuliwen opened a new pull request, #77: URL: https://github.com/apache/iotdb-client-go/pull/77 added how to use sessionPool -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (IOTDB-5588) [Metric] Update Flush Points Internal Reporter
Hongyin Zhang created IOTDB-5588: Summary: [Metric] Update Flush Points Internal Reporter Key: IOTDB-5588 URL: https://issues.apache.org/jira/browse/IOTDB-5588 Project: Apache IoTDB Issue Type: Improvement Reporter: Hongyin Zhang Assignee: Hongyin Zhang Add region tag -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5587) [Metric] Update the prefix of IoTDB Metric
Hongyin Zhang created IOTDB-5587: Summary: [Metric] Update the prefix of IoTDB Metric Key: IOTDB-5587 URL: https://issues.apache.org/jira/browse/IOTDB-5587 Project: Apache IoTDB Issue Type: Improvement Reporter: Hongyin Zhang Assignee: Hongyin Zhang -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5586) Reduce the scope of lock in MemoryPool
Alima777 created IOTDB-5586: --- Summary: Reduce the scope of lock in MemoryPool Key: IOTDB-5586 URL: https://issues.apache.org/jira/browse/IOTDB-5586 Project: Apache IoTDB Issue Type: Improvement Reporter: Alima777 Assignee: Alima777 Every exchangeOperator will reserve or free memory in MemoryPool before adding or removing TsBlock. In condition of high concurrentcy queries or query with high dop, MemoryPool will turn into a bottleNeck. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5585) Change InternalReporterType from IoTDB to Memory to reduce performance degradation
Xinyu Tan created IOTDB-5585: Summary: Change InternalReporterType from IoTDB to Memory to reduce performance degradation Key: IOTDB-5585 URL: https://issues.apache.org/jira/browse/IOTDB-5585 Project: Apache IoTDB Issue Type: Improvement Reporter: Xinyu Tan Assignee: Xinyu Tan At present, the default value of InternalReporterType is IoTDB, which may affect the performance. We plan to change it back to Memory by default. IoTDB versions optimized for this function can be opened by default -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IOTDB-5584) [New feature]The resulte is incorrect when group by condition query
xiaozhihong created IOTDB-5584:
--
Summary: [New feature]The resulte is incorrect when group by
condition query
Key: IOTDB-5584
URL: https://issues.apache.org/jira/browse/IOTDB-5584
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Query, mpp-cluster
Affects Versions: master, 1.1.0-SNAPSHOT
Reporter: xiaozhihong
Assignee: yang caiyin
Branch : master
commit 415f68e36b88659b1e231be2b047483ea791337a
By default, start-standalone.sh, then enter CLI to execute SQL.
Like this:
{code:java}
IoTDB> select * from root.**;
+-+-+-++
|
Time|root.sg.beijing.car01.charging_status|root.sg.beijing.car01.soc|root.sg.beijing.car01.vehicle_status|
+-+-+-++
|1970-01-01T08:00:00.001+08:00| 1|
14.0| 1|
|1970-01-01T08:00:00.002+08:00| 1|
16.0| 1|
|1970-01-01T08:00:00.003+08:00| 0|
16.0| 1|
|1970-01-01T08:00:00.004+08:00| 0|
16.0| 1|
|1970-01-01T08:00:00.005+08:00| 1|
18.0| 1|
|1970-01-01T08:00:00.006+08:00| 1|
24.0| 1|
|1970-01-01T08:00:00.007+08:00| 1|
36.0| 1|
|1970-01-01T08:00:00.008+08:00| null|
36.0| 1|
|1970-01-01T08:00:00.009+08:00| 1|
45.0| 1|
|1970-01-01T08:00:00.010+08:00| 1|
60.0| 1|
+-+-+-++
Total line number = 10
It costs 0.017s
IoTDB> select
__endTime,max_time(charging_status),count(vehicle_status),last_value(soc) from
root.** group by condition(soc>=24.0,KEEP<=15);
+-+-+---+---+-+
|
Time|__endTime|max_time(root.sg.beijing.car01.charging_status)|count(root.sg.beijing.car01.vehicle_status)|last_value(root.sg.beijing.car01.soc)|
+-+-+---+---+-+
|1970-01-01T08:00:00.000+08:00| 0|
null| 0|
null|
|1970-01-01T08:00:00.006+08:00| 10|
10| 5|
60.0|
+-+-+---+---+-+
Total line number = 2
It costs 0.018s
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IOTDB-5581) [Newfeature]Aggregation by condition query incorrect
[ https://issues.apache.org/jira/browse/IOTDB-5581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693765#comment-17693765 ] xiaozhihong commented on IOTDB-5581: Branch : master commit 415f68e36b88659b1e231be2b047483ea791337a I have verified. > [Newfeature]Aggregation by condition query incorrect > > > Key: IOTDB-5581 > URL: https://issues.apache.org/jira/browse/IOTDB-5581 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Query, mpp-cluster >Affects Versions: master branch, 1.1.0 >Reporter: xiaozhihong >Assignee: yang caiyin >Priority: Major > Labels: pull-request-available > Attachments: image-2023-02-24-16-24-09-210.png > > > Branch : Master > commit d6e015eab15a7011bf69c16696106601e52ec308 > By default, start-standalone.sh,then enter CLI. > Execute SQL about aggregation by condition query, the query result is wrong. > See screenshot for details. > !image-2023-02-24-16-24-09-210.png|width=467,height=154! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [iotdb-client-go] dependabot[bot] opened a new pull request, #76: Bump github.com/stretchr/testify from 1.8.1 to 1.8.2
dependabot[bot] opened a new pull request, #76: URL: https://github.com/apache/iotdb-client-go/pull/76 Bumps [github.com/stretchr/testify](https://github.com/stretchr/testify) from 1.8.1 to 1.8.2. Commits https://github.com/stretchr/testify/commit/f36bfe3c337aa95c86f04c721acdbafb5ffb1611";>f36bfe3 Fix Subset/NotSubset when map is missing keys from the subset (https://github-redirect.dependabot.com/stretchr/testify/issues/1261";>#1261) https://github.com/stretchr/testify/commit/0ab3ce1249292a7221058b9e370472bca8f04813";>0ab3ce1 Fix CallerInfo() source file paths (https://github-redirect.dependabot.com/stretchr/testify/issues/1288";>#1288) https://github.com/stretchr/testify/commit/2b00d33aec28e4fded71d57517ed4ec9d54cb4e2";>2b00d33 Fix Call.Unset() panic (issue https://github-redirect.dependabot.com/stretchr/testify/issues/1236";>#1236) (https://github-redirect.dependabot.com/stretchr/testify/issues/1250";>#1250) https://github.com/stretchr/testify/commit/9acc22213e5fbec050904b9886c6df042188cad5";>9acc222 fix: fix bug for check unsafe.Pointer isNil (https://github-redirect.dependabot.com/stretchr/testify/issues/1319";>#1319) https://github.com/stretchr/testify/commit/1333b5d3bda8cf5aedcf3e1aaa95cac28aaab892";>1333b5d Add sub-tests to Suite (https://github-redirect.dependabot.com/stretchr/testify/issues/1246";>#1246) See full diff in https://github.com/stretchr/testify/compare/v1.8.1...v1.8.2";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@iotdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
