[
https://issues.apache.org/jira/browse/SOLR-11409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16236605#comment-16236605
]
Cassandra Targett commented on SOLR-11409:
------------------------------------------
[[email protected]]: I'm reviewing this new page, and noted one
discrepancy I'm not clear about. 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.
Is it recommended to _never_ deploy a production system to EC2? Or you could do
it if you put an ensemble into place?
IOW, are there reasons other than ZK why someone should avoid deploying a
production Solr to EC2?
> 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]
