I am doing a PoC, Till now I used quick_start_stre...
# troubleshooting
r
I am doing a PoC, Till now I used quick_start_stream code. And did some work on that. But when I stop the Pinot, everything tables, schema and data is gone. How to make it all data should be in local permanently. And when I restart the pinot, how can I see tables, schema and data. Need your help
m
If you delete the cluster (which will happen if you delete ZK as part of stopping Pinot) then everything is deleted.
r
What should I do to stay all tables and data stay(store in secondary storage) even I stop and restart. Can you help please...
m
You can have data in deepstore and configs in ZK/helix. You can stop brokers and servers but don’t stop controller/zk, they will cause data loss
Why do you want to stop though? Is it for cost saving?
k
I also have this problem, I want to have all of data persisted in the case of a network outage for the ZK/Controller boxes. Is there any configuration required in order to have this data persisted to disk?
m
When you say data - do you mean Pinot segments, or the metadata/config in ZK?
k
pinot segments and the metadata/configs
m
Pinot segments should be persisted in deep-store
For metadata/configs, there should be a way to rebootstrap ZK from storage I suppose? If so, you can file an issue on Pinot to support that? Or give it a shot yourself, we welcome contributions 🙂
In production though, do you expect ZK/controllers to be completely stopped?
k
in production we can expect power outages so the linux boxes may go down.
what is deep storage? like HDFS?
m
yes, Pinot supports HDFS, S3, GCS, ADLS, NFS right now
You should also build in replication across fault domains to handle power outages.
k
Are there any guides for having the real time table write/save the segmentsto HDFS/NFS? I only see guides for batch job ingestion configs which read files from some file system and into another filesystem.
m
That happens under the hood based on what deepnstore you configured