[jira] [Created] (IOTDB-3514) Query meets BufferUnderflowException
Jialin Qiao created IOTDB-3514:
--
Summary: Query meets BufferUnderflowException
Key: IOTDB-3514
URL: https://issues.apache.org/jira/browse/IOTDB-3514
Project: Apache IoTDB
Issue Type: Bug
Affects Versions: 0.12.5
Reporter: Jialin Qiao
Attachments: 1652428226676-1162-1-0.zip
Failed to recover a TsFileResource, also failed to recover TsFileResource from
TsFile.
{code:java}
2022-06-16 08:09:14,374 [pool-126-IoTDB-Query-5] INFO
o.a.i.d.e.StorageEngine:582 - construct a processor instance, the storage group
is root.CNNP.FQ.03, Thread is 227
2022-06-16 08:09:14,374 [pool-57-IoTDB-RPC-Client-15] WARN
o.a.i.d.s.TSServiceImpl:2031 - [INTERNAL_SERVER_ERROR] Exception occurred while
executing executeQueryStatement "select last FQ_03_3RCV231MV_AVALUE from
root.CNNP.FQ.*".
java.util.concurrent.ExecutionException: java.nio.BufferUnderflowException
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at
org.apache.iotdb.db.service.TSServiceImpl.submitQueryTask(TSServiceImpl.java:848)
at
org.apache.iotdb.db.service.TSServiceImpl.executeQueryStatement(TSServiceImpl.java:780)
at
org.apache.iotdb.service.rpc.thrift.TSIService$Processor$executeQueryStatement.getResult(TSIService.java:2423)
at
org.apache.iotdb.service.rpc.thrift.TSIService$Processor$executeQueryStatement.getResult(TSIService.java:2403)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:38)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:38)
at
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:248)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.nio.BufferUnderflowException: null
at java.nio.Buffer.nextGetIndex(Buffer.java:532)
at java.nio.HeapByteBuffer.getLong(HeapByteBuffer.java:417)
at
org.apache.iotdb.tsfile.utils.ReadWriteIOUtils.readLong(ReadWriteIOUtils.java:545)
at
org.apache.iotdb.tsfile.file.metadata.MetadataIndexNode.deserializeFrom(MetadataIndexNode.java:105)
at
org.apache.iotdb.tsfile.file.metadata.TsFileMetadata.deserializeFrom(TsFileMetadata.java:55)
at
org.apache.iotdb.tsfile.read.TsFileSequenceReader.readFileMetadata(TsFileSequenceReader.java:261)
at
org.apache.iotdb.tsfile.read.TsFileSequenceReader.getAllTimeseriesMetadata(TsFileSequenceReader.java:723)
at
org.apache.iotdb.db.writelog.recover.TsFileRecoverPerformer.recoverResourceFromReader(TsFileRecoverPerformer.java:182)
at
org.apache.iotdb.db.writelog.recover.TsFileRecoverPerformer.recoverResourceFromFile(TsFileRecoverPerformer.java:174)
at
org.apache.iotdb.db.writelog.recover.TsFileRecoverPerformer.recover(TsFileRecoverPerformer.java:104)
at
org.apache.iotdb.db.engine.storagegroup.StorageGroupProcessor.recoverTsFiles(StorageGroupProcessor.java:696)
at
org.apache.iotdb.db.engine.storagegroup.StorageGroupProcessor.recover(StorageGroupProcessor.java:470)
at
org.apache.iotdb.db.engine.storagegroup.StorageGroupProcessor.(StorageGroupProcessor.java:403)
at
org.apache.iotdb.db.engine.StorageEngine.buildNewStorageGroupProcessor(StorageEngine.java:591)
at
org.apache.iotdb.db.engine.storagegroup.virtualSg.VirtualStorageGroupManager.getProcessor(VirtualStorageGroupManager.java:140)
at
org.apache.iotdb.db.engine.StorageEngine.getStorageGroupProcessorByPath(StorageEngine.java:567)
at
org.apache.iotdb.db.engine.StorageEngine.getProcessor(StorageEngine.java:510)
at
org.apache.iotdb.db.engine.StorageEngine.mergeLock(StorageEngine.java:1048)
at
org.apache.iotdb.db.query.executor.LastQueryExecutor.calculateLastPairForSeriesLocally(LastQueryExecutor.java:179)
at
org.apache.iotdb.db.query.executor.LastQueryExecutor.calculateLastPairForSeries(LastQueryExecutor.java:146)
at
org.apache.iotdb.db.query.executor.LastQueryExecutor.execute(LastQueryExecutor.java:103)
at
org.apache.iotdb.db.query.executor.QueryRouter.lastQuery(QueryRouter.java:264)
at
org.apache.iotdb.db.qp.executor.PlanExecutor.processDataQuery(PlanExecutor.java:544)
at
org.apache.iotdb.db.qp.executor.PlanExecutor.processQuery(PlanExecutor.java:228)
at
org.apache.iotdb.db.service.TSServiceImpl.createQueryDataSet(TSServiceImpl.java:1148)
at
org.apache.iotdb.db.service.TSServiceImpl.access$600(TSServiceImpl.java:157)
at
org.apache.iotdb.db.service.TSServiceImpl$QueryTask.call(TSServiceImpl.java:284)
at
org.apache.iotdb.db.service.TSServiceImpl$QueryTask.call(TSServiceImpl.java:222)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
... 3 common frames omitted
2022-06-16 08:09:14,376
[jira] [Assigned] (IOTDB-3512) Report Region leader during heartbeat
[ https://issues.apache.org/jira/browse/IOTDB-3512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongzao Dan reassigned IOTDB-3512: -- Assignee: Xinyu Tan (was: Yongzao Dan) > Report Region leader during heartbeat > - > > Key: IOTDB-3512 > URL: https://issues.apache.org/jira/browse/IOTDB-3512 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Yongzao Dan >Assignee: Xinyu Tan >Priority: Major > Fix For: 0.14.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IOTDB-3511) Show Region tool
[ https://issues.apache.org/jira/browse/IOTDB-3511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongzao Dan reassigned IOTDB-3511: -- Assignee: 任宇华 (was: Yongzao Dan) > Show Region tool > > > Key: IOTDB-3511 > URL: https://issues.apache.org/jira/browse/IOTDB-3511 > Project: Apache IoTDB > Issue Type: New Feature >Reporter: Yongzao Dan >Assignee: 任宇华 >Priority: Major > Fix For: 0.14.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3513) Avoid double-writing of the write ahead log for data under RatisConsensus
Xinyu Tan created IOTDB-3513: Summary: Avoid double-writing of the write ahead log for data under RatisConsensus Key: IOTDB-3513 URL: https://issues.apache.org/jira/browse/IOTDB-3513 Project: Apache IoTDB Issue Type: Improvement Reporter: Xinyu Tan -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3512) Report Region leader during heartbeat
Yongzao Dan created IOTDB-3512: -- Summary: Report Region leader during heartbeat Key: IOTDB-3512 URL: https://issues.apache.org/jira/browse/IOTDB-3512 Project: Apache IoTDB Issue Type: New Feature Reporter: Yongzao Dan Assignee: Yongzao Dan Fix For: 0.14.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3511) Show Region tool
Yongzao Dan created IOTDB-3511: -- Summary: Show Region tool Key: IOTDB-3511 URL: https://issues.apache.org/jira/browse/IOTDB-3511 Project: Apache IoTDB Issue Type: New Feature Reporter: Yongzao Dan Assignee: Yongzao Dan Fix For: 0.14.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3510) Read/Write Routing policy (Routing to DataNod with the lowest-loaded)
Yongzao Dan created IOTDB-3510: -- Summary: Read/Write Routing policy (Routing to DataNod with the lowest-loaded) Key: IOTDB-3510 URL: https://issues.apache.org/jira/browse/IOTDB-3510 Project: Apache IoTDB Issue Type: New Feature Reporter: Yongzao Dan Assignee: Yongzao Dan Fix For: 0.14.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3509) Read/Write Routing Policy (Routing to leader)
Yongzao Dan created IOTDB-3509: -- Summary: Read/Write Routing Policy (Routing to leader) Key: IOTDB-3509 URL: https://issues.apache.org/jira/browse/IOTDB-3509 Project: Apache IoTDB Issue Type: New Feature Reporter: Yongzao Dan Assignee: Yongzao Dan Fix For: 0.14.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IOTDB-3508) Enhance some features of the IT framework
[ https://issues.apache.org/jira/browse/IOTDB-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Irvine reassigned IOTDB-3508: - Assignee: Irvine > Enhance some features of the IT framework > - > > Key: IOTDB-3508 > URL: https://issues.apache.org/jira/browse/IOTDB-3508 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Irvine >Assignee: Irvine >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3508) Enhance some features of the IT framework
Irvine created IOTDB-3508: - Summary: Enhance some features of the IT framework Key: IOTDB-3508 URL: https://issues.apache.org/jira/browse/IOTDB-3508 Project: Apache IoTDB Issue Type: Improvement Reporter: Irvine -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IOTDB-3500) for new standalone IoTDB, there is a error when deleting storage groups
[
https://issues.apache.org/jira/browse/IOTDB-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haonan Hou reassigned IOTDB-3500:
-
Assignee: Haonan Hou (was: Yukun Zhou)
> for new standalone IoTDB, there is a error when deleting storage groups
> -
>
> Key: IOTDB-3500
> URL: https://issues.apache.org/jira/browse/IOTDB-3500
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Server
>Affects Versions: 0.14.0-SNAPSHOT
>Reporter: xiaozhihong
>Assignee: Haonan Hou
>Priority: Major
> Attachments: log_all.log
>
>
> Start a new stand-alone version, create one more storage groups in the CLI,
> and report an error when deleting the storage group containing ** in the path.
> {code:java}
> IoTDB> show storage group;
> +-++-+---+---+
> |storage group|
> ttl|schema_replication_factor|data_replication_factor|time_partition_interval|
> +-++-+---+---+
> | root.sg|null| 0| 0|
> 0|
> | root.ln|null| 0| 0|
> 0|
> +-++-+---+---+
> Total line number = 2
> It costs 0.052s
> IoTDB> delete storage group root.**;
> Msg: 500: [INTERNAL_SERVER_ERROR(500)] Exception occurred: "delete storage
> group root.**". executeStatement failed. error code: TSStatus(code:500)
> {code}
> log information view attachment.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (IOTDB-3507) Performance comparison between standalone IoTDB and Cluster IoTDB with client/partition cache
Quan Siyi created IOTDB-3507: Summary: Performance comparison between standalone IoTDB and Cluster IoTDB with client/partition cache Key: IOTDB-3507 URL: https://issues.apache.org/jira/browse/IOTDB-3507 Project: Apache IoTDB Issue Type: New Feature Reporter: Quan Siyi Assignee: Quan Siyi -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (IOTDB-3257) [cluster]lost data when restart all datanodes of 3
[ https://issues.apache.org/jira/browse/IOTDB-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554615#comment-17554615 ] Haiming Zhu commented on IOTDB-3257: I cannot reproduce this under 3C3D, it seems this issue has been fixed. > [cluster]lost data when restart all datanodes of 3 > -- > > Key: IOTDB-3257 > URL: https://issues.apache.org/jira/browse/IOTDB-3257 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Cluster >Affects Versions: 0.14.0-SNAPSHOT >Reporter: FengQingxin >Assignee: Haiming Zhu >Priority: Major > Attachments: image-2022-05-23-07-41-38-819.png, > image-2022-05-23-09-37-29-633.png > > > Reprodece step: > 1.set up a cluster with 3C3D ; > 2.using some sample sql to test it; > 3.stop all 3 datanodes; > 4.start all datanodes again and using a sql ‘select * from root.**’ to test > in iotdb -cli > No data:(got an empty dataset) > !image-2022-05-23-07-41-38-819.png! > > > > Expect:get all data which we have inserted into iotdb before -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IOTDB-3498) Add IT for group by query in MPP
[ https://issues.apache.org/jira/browse/IOTDB-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Minghui Liu reassigned IOTDB-3498: -- Assignee: Minghui Liu (was: Alima777) > Add IT for group by query in MPP > > > Key: IOTDB-3498 > URL: https://issues.apache.org/jira/browse/IOTDB-3498 > Project: Apache IoTDB > Issue Type: Task >Reporter: Alima777 >Assignee: Minghui Liu >Priority: Major > Original Estimate: 48h > Remaining Estimate: 48h > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3506) Make MQTT service support new MPP architecture
Wei Liu created IOTDB-3506: -- Summary: Make MQTT service support new MPP architecture Key: IOTDB-3506 URL: https://issues.apache.org/jira/browse/IOTDB-3506 Project: Apache IoTDB Issue Type: Improvement Reporter: Wei Liu Assignee: Wei Liu Fix For: 0.14.0-SNAPSHOT -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IOTDB-3285) createAlignedTimeseries failed java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
[ https://issues.apache.org/jira/browse/IOTDB-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Minghui Liu reassigned IOTDB-3285: -- Assignee: Minghui Liu (was: Yukun Zhou) > createAlignedTimeseries failed java.lang.IndexOutOfBoundsException: Index: > 0, Size: 0 > -- > > Key: IOTDB-3285 > URL: https://issues.apache.org/jira/browse/IOTDB-3285 > Project: Apache IoTDB > Issue Type: Bug > Components: mpp-cluster >Affects Versions: 0.14.0-SNAPSHOT >Reporter: 刘珍 >Assignee: Minghui Liu >Priority: Major > Attachments: config.properties, image-2022-05-25-13-59-40-493.png > > > master_0525_5f8c634 > 1confignode , 1datanode > schema_replication_factor=1 > data_replication_factor=1 > 注册对齐序列失败 > 2022-05-25 11:45:26,700 [pool-20-IoTDB-RPC-Client-2] WARN > o.a.i.d.u.ErrorHandlingUtils:61 - Status code: EXECUTE_STATEMENT_ERROR(400), > operation: createAlignedTimeseries failed > java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 > at java.util.ArrayList$SubList.rangeCheck(ArrayList.java:1225) > at java.util.ArrayList$SubList.get(ArrayList.java:1042) > at > org.apache.iotdb.db.mpp.common.schematree.PathPatternTree.parseNodesToString(PathPatternTree.java:131) > at > org.apache.iotdb.db.mpp.common.schematree.PathPatternTree.findAllDevicePaths(PathPatternTree.java:112) > at > org.apache.iotdb.db.mpp.common.schematree.PathPatternTree.findAllDevicePaths(PathPatternTree.java:103) > at > org.apache.iotdb.db.mpp.plan.analyze.ClusterPartitionFetcher.getOrCreateSchemaPartition(ClusterPartitionFetcher.java:134) > at > org.apache.iotdb.db.mpp.plan.analyze.Analyzer$AnalyzeVisitor.visitCreateAlignedTimeseries(Analyzer.java:958) > at > org.apache.iotdb.db.mpp.plan.analyze.Analyzer$AnalyzeVisitor.visitCreateAlignedTimeseries(Analyzer.java:128) > at > org.apache.iotdb.db.mpp.plan.statement.metadata.CreateAlignedTimeSeriesStatement.accept(CreateAlignedTimeSeriesStatement.java:191) > at > org.apache.iotdb.db.mpp.plan.statement.StatementVisitor.process(StatementVisitor.java:62) > at > org.apache.iotdb.db.mpp.plan.analyze.Analyzer.analyze(Analyzer.java:120) > at > org.apache.iotdb.db.mpp.plan.execution.QueryExecution.analyze(QueryExecution.java:182) > at > org.apache.iotdb.db.mpp.plan.execution.QueryExecution.(QueryExecution.java:121) > at > org.apache.iotdb.db.mpp.plan.Coordinator.createQueryExecution(Coordinator.java:107) > at > org.apache.iotdb.db.mpp.plan.Coordinator.execute(Coordinator.java:127) > at > org.apache.iotdb.db.service.thrift.impl.DataNodeTSIServiceImpl.createAlignedTimeseries(DataNodeTSIServiceImpl.java:403) > at > org.apache.iotdb.service.rpc.thrift.TSIService$Processor$createAlignedTimeseries.getResult(TSIService.java:3178) > at > org.apache.iotdb.service.rpc.thrift.TSIService$Processor$createAlignedTimeseries.getResult(TSIService.java:3158) > at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:38) > at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:38) > at > org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:248) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > !image-2022-05-25-13-59-40-493.png! > 复现流程 > 1. 192.168.10.68 72C256G > /data/benchmark/weekly_shell/benchmark_tool > benchmark 配置文件见附件 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3505) The ratis is not deleted when the storage group is deleted, causing the program to exit when starting the DataNode
xiaozhihong created IOTDB-3505: -- Summary: The ratis is not deleted when the storage group is deleted, causing the program to exit when starting the DataNode Key: IOTDB-3505 URL: https://issues.apache.org/jira/browse/IOTDB-3505 Project: Apache IoTDB Issue Type: Bug Components: Core/Cluster, mpp-cluster Affects Versions: 0.14.0-SNAPSHOT Reporter: xiaozhihong Assignee: Xinyu Tan Attachments: logs.zip Start 3C3D, perform SQL-related read and write operations, and then restart 3C3D. After restarting 1confignode, the program exits the program directly when starting 1DataNode. log information view attachment. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3504) Fix inferTypes, return value and column label of IN/LIKE/REGEXP in SELECT component;
李伟豪 created IOTDB-3504: -- Summary: Fix inferTypes, return value and column label of IN/LIKE/REGEXP in SELECT component; Key: IOTDB-3504 URL: https://issues.apache.org/jira/browse/IOTDB-3504 Project: Apache IoTDB Issue Type: Task Components: Core/Query Reporter: 李伟豪 Assignee: 李伟豪 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (IOTDB-3503) Migrate tests to the new IT framework
[ https://issues.apache.org/jira/browse/IOTDB-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 李伟豪 reassigned IOTDB-3503: -- Assignee: 李伟豪 > Migrate tests to the new IT framework > - > > Key: IOTDB-3503 > URL: https://issues.apache.org/jira/browse/IOTDB-3503 > Project: Apache IoTDB > Issue Type: Task > Components: Core/Others >Reporter: 李伟豪 >Assignee: 李伟豪 >Priority: Major > Original Estimate: 120h > Remaining Estimate: 120h > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3503) Migrate tests to the new IT framework
李伟豪 created IOTDB-3503: -- Summary: Migrate tests to the new IT framework Key: IOTDB-3503 URL: https://issues.apache.org/jira/browse/IOTDB-3503 Project: Apache IoTDB Issue Type: Task Components: Core/Others Reporter: 李伟豪 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3502) aborting SinkHandle won't unblock the corresponding SourceHandle
Jinrui Zhang created IOTDB-3502: --- Summary: aborting SinkHandle won't unblock the corresponding SourceHandle Key: IOTDB-3502 URL: https://issues.apache.org/jira/browse/IOTDB-3502 Project: Apache IoTDB Issue Type: Bug Reporter: Jinrui Zhang Assignee: Jinrui Zhang In current implementation, we have the timeout mechanism for FI. When the FI is aborted, it will abort its SourceHandle. But it seems that it won't unblock downstream Source Handle especially for the ResultHandle -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3501) Add IT for syntax convention in new cluster
liaolanyu created IOTDB-3501: Summary: Add IT for syntax convention in new cluster Key: IOTDB-3501 URL: https://issues.apache.org/jira/browse/IOTDB-3501 Project: Apache IoTDB Issue Type: Improvement Reporter: liaolanyu Assignee: liaolanyu -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (IOTDB-3500) for new standalone IoTDB, there is a error when deleting more than or equal to 2 storage groups
xiaozhihong created IOTDB-3500:
--
Summary: for new standalone IoTDB, there is a error when deleting
more than or equal to 2 storage groups
Key: IOTDB-3500
URL: https://issues.apache.org/jira/browse/IOTDB-3500
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Server
Affects Versions: 0.14.0-SNAPSHOT
Reporter: xiaozhihong
Assignee: Yukun Zhou
Attachments: log_all.log
Start a new stand-alone version, create 2 storage groups in the CLI, and report
an error when deleting the storage group containing ** in the path.
{code:java}
IoTDB> show storage group;
+-++-+---+---+
|storage group|
ttl|schema_replication_factor|data_replication_factor|time_partition_interval|
+-++-+---+---+
| root.sg|null| 0| 0|
0|
| root.ln|null| 0| 0|
0|
+-++-+---+---+
Total line number = 2
It costs 0.052s
IoTDB> delete storage group root.**;
Msg: 500: [INTERNAL_SERVER_ERROR(500)] Exception occurred: "delete storage
group root.**". executeStatement failed. error code: TSStatus(code:500)
{code}
log information view attachment.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
