web stats
Mirth "statefulness" clarifications - Mirth Community

Go Back   Mirth Community > Mirth Connect > Support

Reply
 
Thread Tools Display Modes
  #1  
Old 02-10-2020, 06:52 AM
davidepetilli davidepetilli is offline
What's HL7?
 
Join Date: Feb 2020
Posts: 1
davidepetilli is on a distinguished road
Default Mirth "statefulness" clarifications

Hello,
I need your help to understand Mirth behaviour. I want to understand how "stateful" it is.
Doing some experiments, I understand there is no risk of messages loss as they are persisted in the DB at every stage.
What I donít understand is how the processing is supposed to be resumed.
Letís say that Mirth is restarted while it is processing a message or it has some messages in a queue. After the restart I can see the messages are there, but the processing is not resumed automatically, I have to reprocess them by hand.
Is there any way to resume the processing automatically from the last persisted status? Is it possible to reconstruct the queues from the d_mm*.status column?

Another question is about handling custom persistent data. I know that GlobamMap and GlobalChannelMap are in memory data structures. Is there any alternative (fast enough) to persist some processing data between restarts (for example to use in a filter)?

The reason I am concerned about this is that in a cloud-native environment (K8s), it is quite common and it happens quite often that applications are restarted (moving Pods around is the norm). My concern is that in a K8s cluster, Mirth behaviour could be crippled. For example you cannot count on GlobalMap at all (the Pod could be restarted anytime), or message queue may need to be restarted by hand every time the Pod is recreated.
Has anybody experience in running Mirth in K8s?

Thanks.
Davide
Reply With Quote
  #2  
Old 02-13-2020, 10:37 AM
agermano agermano is offline
Mirth Guru
 
Join Date: Apr 2017
Location: Indiana, USA
Posts: 1,095
agermano is on a distinguished road
Default

There are many concerns with running mirth in any type of cluster. There is an advanced clustering plugin with paid nextgen support that addresses them.
Reply With Quote
Reply

Tags
kubernetes, stateless

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -8. The time now is 02:59 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2020, vBulletin Solutions, Inc.
Mirth Corporation