Email attachment via load balancer

Avatar

Avatar

Milan_Vucetic

MVP

Avatar

Milan_Vucetic

MVP

Milan_Vucetic
MVP

16-12-2019

Hi everyone,

 

I am playing with email attachments from local computer and it works fine when it is used on test environment as there exist only one app server.

When it is used on production environment where exist two app servers and load balancer in front of them, attachment is uploaded only on one server (which is current in the moment of the upload) and some temporary error is thrown:

Unable to finalize storage of resource as the file has not been uploaded...

 

So, until we start delivery execution load balancer can switch user to another server where file does not exist and brake it.

Is there a "easy & nice" way to overcome this without uploading files with workflows, etc... ?

 

Regards,

Milan

 

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

wodnicki

MVP

Avatar

wodnicki

MVP

wodnicki
MVP

18-12-2019

Hi,

 

Easy answer is to just mount resource dirs from a network share, which you should be doing anyway for workflow file uploads etc.

Another option is to list both app servers as mta child's in their instance confs, which logically should cause the first to publish attachments to the second and vice-versa.

Finally, your load balancer should be in active/passive mode, with all traffic going to the primary until it dies. There are other issues with active/active, e.g. preventing users from reliably using unconditional halt on workflows.

 

Thanks,

-Jon

Answers (1)

Answers (1)

Avatar

Avatar

_Manoj_Kumar

MVP

Avatar

_Manoj_Kumar

MVP

_Manoj_Kumar
MVP

16-12-2019

Hello Milan,

 

You can use Amazon S3 integration in this case and upload your static content there.

 

Thanks,

Manoj