zachjsh opened a new issue, #13208:
URL: https://github.com/apache/druid/issues/13208
Please provide a detailed title (e.g. "Broker crashes when using TopN query
with Bound filter" instead of just "Broker crashes").
### Affected Version
Tested on latest master branch 25.0.0-SNAPSHOT
### Description
Ingested a json file with only the following 2 rows through MSQ
```
% cat lookup_data_small.json
{"k": "stringggggggggggggggggggggggggggggggggggggggggg0", "v":
"stringValuegggggggggggggggggggggggggggggggggggggg0"}
{"k": "stringggggggggggggggggggggggggggggggggggggggggg1", "v":
"stringValuegggggggggggggggggggggggggggggggggggggg1"}
%
```
I just kept clicking through the web-console screens, taking whatever
defaults were provided. The spec generated produced an insert with a
`PARTITIONED BY ALL` clause. The interval detected by this is
```
"intervals": {
"type": "intervals",
"intervals": [
"-146136543-09-08T08:23:32.096Z/146140482-04-24T15:36:27.903Z"
]
},
```
After the table is ingested configure auto-compaction on the table. To do
this I simply changed the default config to the following
```
{
"dataSource": "lookup_data_small",
"granularitySpec": {
"segmentGranularity": "DAY"
},
"tuningConfig": {
"partitionsSpec": {
"type": "dynamic"
}
}
}
```
The only difference here is the addition of the granulartySpec.
Wait for the next coorindator indexer cycle to run (I just changed by
setting `druid.coordinator.period.indexingPeriod=PT60s` in coordinator runtime
properties file)
This causes the Coordinator to crash and take up a ton of CPU and memory
before doing so. I believe the issue is in building the interval to segments
map here:
https://github.com/apache/druid/blob/691e26d2429cd81afef092dbda32e24ad56bb510/server/src/main/java/org/apache/druid/server/coordinator/duty/NewestSegmentFirstIterator.java#L121.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
