[ 
https://issues.apache.org/jira/browse/SOLR-11409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237607#comment-16237607
 ] 

Amrit Sarkar commented on SOLR-11409:
-------------------------------------

Thank you Cassandra,

bq .At the top of the page, you write that the quick start is not meant for 
production systems, but in the Appendix you note that for production one should 
have a ZK ensemble of at least 3 nodes.

We can remove "Note for production one should have a ZK ensemble of at least 3 
nodes." as this qucik start is not meant for production and leave that bit of 
information to "Setting Zookeeper ensemble .....", I understand it contradict 
the intro statement. I can remove that "bold" NOTE and upload new patch, let me 
know.

bq. Is it recommended to never deploy a production system to EC2? Or you could 
do it if you put an ensemble into place?

No, we can safely deploy production system on EC2 instances. The quick start is 
the base to understand how to establish a dev environment but need further 
pointers for production and this page doesn't serve that.

> A ref guide page on setting up solr on aws
> ------------------------------------------
>
>                 Key: SOLR-11409
>                 URL: https://issues.apache.org/jira/browse/SOLR-11409
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Varun Thacker
>            Priority: Minor
>         Attachments: SOLR-11409.patch, quick-start-aws-key.png, 
> quick-start-aws-security-1.png, quick-start-aws-security-2.png
>
>
> It will be nice if we have a dedicated page on installing solr on aws . 
> At the end we could even link to 
> http://lucene.apache.org/solr/guide/6_6/taking-solr-to-production.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to