The biggest thing for us using Ignite Persistence on AWS was finding that we needed to use i3 instances for the SSD write performance. Ignite persistences and GP2 was a poor experience.
On Tue, May 15, 2018 at 2:43 AM, John Gardner <john.gard...@salecycle.com> wrote: > We've been running the GridGain version of Ignite 8.3.4 within AWS for a > couple of months now, we're still finding little issues here and there, so > I was wondering if anyone has any advice, tips or hints specifically when > running this within an AWS environment. Have you had any problems with > Network Segmentation? How are the cluster nodes working within > Auto-Scaling Groups? How does Ignite cope with dynamic scaling out? If you > have anything like that, it would be great to hear from anyone. > > Thanks and Regards > > John > > -- > > > Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.
