Druid cluster shows unavailable for certain segments of data of data source after data ingestion. Ex: 72.4% available (2352 segments, 647 segments unavailable) We have a clustered deployment 3 nodes : master node (coordinator amd overlord) Data node (historical and middlemanager) Query node (broker and router) Any specific reason why it is happening so.
Asked
Active
Viewed 2,015 times
1 Answers
1
The issue is resolved after clean restart of master and data nodes. However just restarting nodes without cleaning data did not work
Shashank NS
- 53
- 5
-
Hello! Could you please explain what is a _clean restart of master and data nodes_? Thanks in advance – nicodds Feb 25 '20 at 16:32
-
1Deletion of segments-cache data and indexing logs in data and master nodes – Shashank NS Feb 25 '20 at 17:28
-
but isn't this going make druid lose data? – im2kul Apr 22 '20 at 16:08
-
Since the data would be in deep storage it will be able to load the segments – Shashank NS Apr 23 '20 at 17:44