Data ingestion issue

I found that few days back all of a sudden the data is not going to S3.

Opened the aws console and found that historical data disk was full but other two historical node had data.

Mounted the new disk and as when started imply server I see that the segments were loaded to the new mount system.

Before -

druid.segmentCache.locations=[{“path”:"/data/var/druid/segment-cache",“maxSize”:1536000000000}]

druid.server.maxSize=1536000000000

It was 100% full.

After

druid.segmentCache.locations=[{“path”:"/data/var/druid/segment-cache",“maxSize”:1536000000000},{“path”:"/data2/var/druid/segment-cache",“maxSize”:1536000000000}]

druid.server.maxSize=3072000000000

I double the size of /data and added a new disk and mounted to /data2

After restarting druid on just this historical node, i see all the segments loaded to data2/var/druid/segment

On the Druid console… the segment getting loaded and it eventually loaded all the segments.

I still don’t see the data getting ingested to S3.

I restarted imply server several times. Is there a order i should follow to restart all the node ?