[GitHub] clintropolis commented on a change in pull request #6911: Remove DataSegmentFinder, InsertSegmentToDb, and descriptor.json file in deep storage

[GitBox <gi...@apache.org>]

clintropolis commented on a change in pull request #6911: Remove DataSegmentFinder, InsertSegmentToDb, and descriptor.json file in deep storage
URL: https://github.com/apache/incubator-druid/pull/6911#discussion_r258291052
 
 

 ##########
 File path: docs/content/dependencies/metadata-storage.md
 ##########
 @@ -32,7 +32,9 @@ Derby is the default metadata store for Druid, however, it is not suitable for p
 [MySQL](../development/extensions-core/mysql.html) and [PostgreSQL](../development/extensions-core/postgresql.html) are more production suitable metadata stores.
 
 <div class="note caution">
-Derby is not suitable for production use as a metadata store. Use MySQL or PostgreSQL instead.
+The Metadata Storage stores the entire metadata which is essential for a Druid cluster to work.
+For production clusters, consider using MySQL or PostgreSQL instead of Derby.
+Also, it's highly recommended to set up a high availability environment.
 
 Review comment:
   It might be worth stressing the importance of not losing this data, since there is no longer a way to rebuild it in the event of a failure.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org