This message was deleted.
# troubleshooting
s
This message was deleted.
b
The interval seems to be saying year 20150912. What date are you trying to use?
h
Hi @Ben Krug That's the one I am setting the retention to.
This interval - 20150912-01-01T010000.000Z/20150912-01-01T020000.000Z
b
Year 20150912, ie about 20M years in the future?
h
It's actually 2015 09 12
YYYY MM DD
b
Oh, then maybe you want something like 2015-09-12T010000.000Z-2015-09-12T020000.000Z?
Oh wait, do you have segments in that time interval, and you're using the UI to try to drop them, right?
h
That's what I'm specifying, as posted above
Correct
I have the segments in that interval
b
If you mark as unused in GUI, then issue kill in GUI, this is what happens?
h
I created a datasource from the packaged tutorial
Yepp, that's the problem mate.
Check out the timestamp on the log output
Doesn't make any sense
1000 01 01
b
😞 I wonder if it's some kind of overflow. Do you need the other segments (ie, the datasource)? If not, maybe a "mark all segments unused", etc, would work?
h
Yepp that works, if I mark all as unused and then kill, it wipes out the datasource and all of the data is deleted from the deep storage
b
Which tutorial is this? If this is what it does, maybe the tutorial needs to get fixed.
h
I'm wondering whether there's something in the config I can look at
So basically I used the tutorial stuff to create a datasource with 24 hourly segments.
b
I'm not sure about the config. I thought of using API instead of GUI, but I have a feeling the same thing might happen.
h
Prolly, I'm gonna have to look into the config and setup.
There's something amiss
b
Which tutorial is it?
h
Ah actually I'm referring to the tutorial folder under the druid install path
There's a wikipedia data tar.gz file one can use as input data and then copy one of the json files to run an ingestion workload to create a datasource
But regardless, when I set up retention rules and issue a kill task it should remove the segment and wipe out the data
Have you played around with that feature? Maybe I'm missing something out
b
It should work, I don't know why the kill task is changing the interval like that. I suspect the year is too big, I'll play around and check it out, maybe file a bug. (Or, if you have the json and ingestion spec, feel free to create a bug report.) Maybe the ingestion spec isn't handling the input timestamp format correctly, causing weird years.
h
Sounds good mate. I'll try it out with a few tweaks to see whether I can go beyond this. Let me share the ingestion spec here.
Thanks for helping out 🙌
b
yw!