We are going to go a similar route in AWS (.Net client with .Net standard artifacts inning on Kubernetes).
Currently we are looking at whether EBS or EFS is the best option, but the comments here are concerning re Ignite IO bandwidth on those services. What page size are you using? If you are using the default 1Kb page size this could cause problems as EBS writes are 4Kb, so each flush of a 1KB page is underutilising bandwidth), assuming there is more data that would be saved than the standard 1Kb write. This may tie into recent discussions about the default conservative flush mode. If you are forcing large numbers of small writes then EBS won't be as good as local SSD for sure. Given I3 based storage is ephemeral how are you ensuring non-ephemeral backup of your data? Thanks, Raymond. Sent from my iPhone > On 16/05/2018, at 12:23 AM, David Harvey <[email protected]> wrote: > > 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 <[email protected]> >> 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 Click Here.
