This message was deleted.
# troubleshooting
s
This message was deleted.
b
Are any historicals loading segments in the console's Services view? Anything in historical logs? Are any of the historicals at 100%?
g
seems odd; datasource availability is based on the % of segments are unavailable. if it's 100% then there would not be any unavailable segments what API / UI control are you looking at when you see the 100% availability and the unavailable segments?
perhaps knowing what you're looking at will help us figure out what's going on
s
this in the coordinator logs...
g
although, it's definitely odd for this condition to persist for a while. ordinarily such segments are marked unused relatively promptly (within a few minutes, an hour at most)
if the condition still persists i'd try checking for info on the unavailable ones using
sys.segments
. perhaps pick one datasource and one time range (a specific
"start"
value) and see what's going on there