Hi 😉 Still using an old Pinot version and getting reload tasks kinda locked

{
  "metadata": {
    "jobId": "d51ad5fb-e720-4356-bd49-49de439f1c13",
    "messageCount": "2",
    "submissionTimeMs": "1771840917900",
    "jobType": "RELOAD_SEGMENT",
    "segmentName": "myStuff_1_173__20260223T0207Z",
    "tableName": "myStuff_REALTIME"
  },
  "successCount": 0,
  "totalSegmentCount": 2,
  "totalServersQueried": 2,
  "totalServerCallsFailed": 0,
  "timeElapsedInMinutes": 1716.5874833333332,
  "estimatedTimeRemainingInMinutes": -1
}

Is there a way to kick them off ?

Any clues in server logs for the reload message?

Nothing even by searching with the jobId 😞

no trace in helix logs as well?

good point 😉 I will check

Any trace of

Reloading segment: myStuff_1_173__20260223T0207Z in table: myStuff_REALTIME

on server? If its not there then the message is not reaching the server

Tried to grep “`Reloading`” noting

Is there a helix message queue pile-up on the server?

still running a 0.12 (I know) I will check 😉

it should be under the zk path

/<clusterName>/INSTANCES/<instanceId>/MESSAGES

perfectly clean and empty

💀

seems like a dead task ... I will try to relaunch a reload 😇

do you see either of •

Sending reload message for segment: myStuff_1_173__20260223T0207Z in table: myStuff_REALTIME

•

Sent 2 reload messages for segment: myStuff_1_173__20260223T0207Z in table: myStuff_REALTIME

•

No reload message sent for segment: myStuff_1_173__20260223T0207Z in table: myStuff_REALTIME

on controller atleast😅

empty grep on all side on

myStuff_1_173__20260223T0207Z

or

reload

that's not possible, I give up😆

find out 😜 Finally got a message on controller I could handle and fix

No problem! what was the issue?

getting message about unable to acess folder to store temp segments on server side

Thanks @Shounak Kulkarni