This message was deleted.

You can change replicant count from datasource> load rule , by default replica is 2 so if you have two historical then they will replicated on two historical. You can add new rule specific to datasource and change replication . Note editing defaults will change for all datasources .

Still, if i shutdown one data node everything is inaccessible...

What error you are getting when you try to query ?

The segment seems to be only on one node

coordinator will take care of replication . do you see any errors in coordinator logs and historical that is running. https://druid.apache.org/docs/latest/design/coordinator.html#segment-availability

For some reason I was able to fix it by setting replicas to two in my data source ingestion config. Is that what I was missing? I'm just checking as i'm not sure if that is the right thing to do or maybe there's another solution.

you can also set from the replica from retention rule as well

Well, it only worked after i edited ingestion config for some reason. May I also ask what is now happening with segments after they are no longer in use? Are they always stored on both servers or only while being used.

With druid you always define load rule with (rentienton) how data can be stored on druid and rest will be dropped. Only spcified period of data will be loaded by historical . https://druid.apache.org/docs/latest/operations/rule-configuration.html

By dropped you mean fully removed or just moved out of druid fast access cache? Thank you very much for your help so far btw :)

it will be dropped from druid historical server but segments will be there in deep storage until you fully remove from deep storage as well.

Now, for instance, I have the following situation