mcvsubbu commented on a change in pull request #3975: ReadTheDocs documentation 
for Table Configs, Monitoring, and Deployment
URL: https://github.com/apache/incubator-pinot/pull/3975#discussion_r268339141
 
 

 ##########
 File path: docs/in_production.rst
 ##########
 @@ -40,11 +40,14 @@ Recommended environment
 Deploying Pinot
 ---------------
 
-Direct deployment of Pinot
-~~~~~~~~~~~~~~~~~~~~~~~~~~
+In general, when deploying Pinot services, it is best to adhere to a specific 
ordering in which the various components should be deployed. This deployment 
order is recommended incase of the scenario that there might be protocol or 
other significant differences, the deployments go out in a predictable order in 
which failure  due to these changes can be avoided.
 
 Review comment:
   Can you update the requirments section to be not as vague as it is now? A 
paragraph would do. Here is a suggestion. We can iterate and modify later, but 
let us have something in place now. Feel free to modify/add to as you please.
   
   You will need the following in order to run pinot in production:
   * Hardware for controller/broker/servers as per your load
   * Working installation of Zookeeper that Pinot can use. We recommend setting 
aside a path within zookpeer and including that path in pinot.controller.zkStr. 
Pinot will create its own cluster under this path (cluster name decided by 
pinot.controller.helixClusterName)
   * Shared storage mounted on controllers (if you plan to have multiple 
controllers for the same cluster). Alternatively, an implementation of PinotFS 
that the Pinot hosts have access to.
   * HTTP load balancers for spraying queries across brokers (or other 
mechanism to balance queries)
   * HTTP load balancers for spraying controller requests (e.g. segment push, 
or other controller APIs) or other mechanisms for distribution of these 
requests.

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


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to