Hi team, we were facing an access issue with our S3 based deep-store and we wanted to disable it. So I went ahead and removed all S3 related configs from the controller config as:

controller.helix.cluster.name=myCluster
    controller.port=9000
    controller.data.dir=/tmp/controller
    controller.zk.str=myZKStr
    pinot.set.instance.id.to.hostname=true

And it doesn’t seem to be trying to connect with S3 anymore. Wanted to confirm if this is the right way to do this? Thanks!

You're going to use another deep store, right? As another Pinot user, I'd highly recommend using some deep store, doesn't have to be S3 necessarily. Because not using one causes the reliability to drop significantly.

@Diogo Baeder Not for now, no. This is in our perf testing env and we don’t really care a whole lot about reliability that much. Nonetheless, we do have a deep store configured that’s facing some issues rn. So to unblock our users, I had to resort to this.

Ah, got it. In a test setting I don't think it would be necessary indeed... (at least in our company we don't use a deep store when doing integration or manual testing against Pinot, at least)

Yup this is the right way. I assume you have only one controller?

@Neha Pawar We have 3 actually for this cluster.

in that case, it won’t work correctly. By default, if no deep store, Pinot will use controller disk. So if the 3 controllers aren’t using a shared volume (e.g. attached NFS), then this setup won’t work

Yes, got it, thanks @Neha Pawar Is there a way to sanely disable deep-store for such use-cases?