You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a use case where we want 90% of topics written to ephemeral ramdisk since persistence doesn't matter for these and the data is required to not be stored on disk, but we require a few select topics to be persistent and stored on disk. Is there a way to have individual topic locations in one broker or do we need to spin up a second broker for the ones we need on file system?
hey @Andrew9317 yeh we've seen similar use cases. redpanda doesn't provide that level of granularity of data placement yet, but I'm pretty sure that at least one cluster has worked around it with some clever use of file system mounting to get the desired layout. lemme know if that doesn't work there might be some other tricks. also, it should be noted, that we don't test this kind of setup. it should work, but i'm not sure what kind of issues you might encounter. happy to field questions though with what you find!
We have a use case where we want 90% of topics written to ephemeral ramdisk since persistence doesn't matter for these and the data is required to not be stored on disk, but we require a few select topics to be persistent and stored on disk. Is there a way to have individual topic locations in one broker or do we need to spin up a second broker for the ones we need on file system?
JIRA Link: CORE-8519
The text was updated successfully, but these errors were encountered: