Hi Vishwas, I watched many Mule related videos on youtube and can confidently say that yours are one of the best. I really enjoy watching them - they are informative, deep, and very well presented. Thank you for this!
Persistent VM queues provide the same result as transient queues in RTF. Despite being persistent (persisted to disk) the queues would be wiped off if the pod/container crashes. The only case where the persistent queue would survive is when the wrapper restarts the runtime (in this case pod/container doesn't restart). Other case would be when you choose "Run in Runtime Cluster Mode" from Runtime Manger and deploy more than 1 replica. In this case the vm queues will be replicated across each replica by Hazelcast, in this case irrespective of the transient or persistent nature of queue, it would survive restarts provided that at least one replica remains alive.
Excellent Video. Let's say I have configured persistent VM and my listener flow failed during processing the message to target system whether the message will be deleted or comes back for next attempt ? in APQ the message goes in flight until consumer is successful otherwise the original message comes back If consumer process failed to process?
Hi Vishwas, I have one query Query: I am reading 400 MB data(thousands of zip files) from one location and placing in archive location after that unzip and proccess the data. I used vm queue ( transient mode) 0.2vcores & 2workers used in cloudhub but not working it restart automatically due to jvm memory How to resolve this issue? can I use persistent mode for this? Plz rly thanks
Hi Vishwas. In cluster environment VM Queue stores the data in memory. When cluster goes down data is lost. Is there any way we can store data in DB or design it using Redis
you are the best concept ex-plainer . i request you to have more videos on mule admin part.. you find very less videos on Mule administration if possible 1. clustering using on premise env 2. SLB, DLB on cloudhub 3.Runtime Fabric
you are best concept ex plainer . would request to put more videos on mule admin 1.creating load balances on premise env 2.SLB , dlb concepts on cloud hub 3.runtime Fabric
I can try to come up with conceptual videos, but setting up those components like DLB on cloud hub usually require paid subscription on cloud hub, which I can't afford.
In batch processing under the hood as it uses Amazon SQS, there is no chance of getting out of memory error right? Because it doesn't depend on vcore anymore.
@@Vishwasp13 ok. If persistent queues are not enabled then it will use disk space automatically not the heap memory or we have to change some configuration to have this behaviour.
Awesome guide. I implemented as you suggested but did not observe same behavior in VMQ. Deployed to CH with 2 workers, having created a scheduler, then 2 VM publish within scatter-gather. Each VM-Listener listens to input messages and wait for 5 secs. Observed that, every time app is running in single node and never runs in other node, any reason? What should I make to run in both workers?. Scheduler->for-each(scatter-gather(VM-publish)). VM-listener1->DW(wait-5secs) VM-listener2->DW(wait-5secs)
Transient remains in memory (JVM Heap space probably) due which it is local to a worker. Since its in-memory and restricted to a worker it doesn't gets shared, unless you enable the Persistent Queue option in Runtime Manager queues remain isolated.
Hi Vishwas, Will we be able to scale applications horizontally using a free subscription? Workers drop down is disabled for me. I see that it is enabled for you. Is there a permission which i am missing?
Hi Vishwas, I watched many Mule related videos on youtube and can confidently say that yours are one of the best. I really enjoy watching them - they are informative, deep, and very well presented. Thank you for this!
Very Good Explanation Vishwas. Thank you so much!
Thank you so much for the information shared.. Yes it indeed cleared many of our doubts..
Thanks Vishwas. This video cleared by doubts
This is the best content on the subject
Beautifully Explained..Thank you so much
Thank you, could you please let me know how VM works with RTF ?
Premium content - as always. Thank you!
Can you please provide some information on how transient VM queue and persistent VM queue works in RTF? Thanks.
Persistent VM queues provide the same result as transient queues in RTF. Despite being persistent (persisted to disk) the queues would be wiped off if the pod/container crashes. The only case where the persistent queue would survive is when the wrapper restarts the runtime (in this case pod/container doesn't restart).
Other case would be when you choose "Run in Runtime Cluster Mode" from Runtime Manger and deploy more than 1 replica. In this case the vm queues will be replicated across each replica by Hazelcast, in this case irrespective of the transient or persistent nature of queue, it would survive restarts provided that at least one replica remains alive.
@@Vishwasp13 excellent!! Thank you very much. Mule should have a clear answer like this in their documentations.
Excellent Video. Let's say I have configured persistent VM and my listener flow failed during processing the message to target system whether the message will be deleted or comes back for next attempt ? in APQ the message goes in flight until consumer is successful otherwise the original message comes back If consumer process failed to process?
VM queues are transactional, you won't lose messages.
Hi Vishwas, I have one query
Query: I am reading 400 MB data(thousands of zip files) from one location and placing in archive location after that unzip and proccess the data.
I used vm queue ( transient mode)
0.2vcores & 2workers used in cloudhub but not working it restart automatically due to jvm memory
How to resolve this issue?
can I use persistent mode for this? Plz rly thanks
Hi Vishwas. In cluster environment VM Queue stores the data in memory. When cluster goes down data is lost. Is there any way we can store data in DB or design it using Redis
Very informative. Thank you
Please make a video on Logging in Mule. Cloud hub logging, how to configure log4j Appenders to use external logging solutions like Splunk etc .
good tutorial. bro. what tools you use for recording such videos.. they are crystal clear in voice
Thanks, I use maono au 100 microphone for audio recording and obs for screen recording.
you are the best concept ex-plainer . i request you to have more videos on mule admin part.. you find very less videos on Mule administration if possible
1. clustering using on premise env
2. SLB, DLB on cloudhub
3.Runtime Fabric
you are best concept ex plainer . would request to put more videos on mule admin
1.creating load balances on premise env
2.SLB , dlb concepts on cloud hub
3.runtime Fabric
I can try to come up with conceptual videos, but setting up those components like DLB on cloud hub usually require paid subscription on cloud hub, which I can't afford.
In batch processing under the hood as it uses Amazon SQS, there is no chance of getting out of memory error right? Because it doesn't depend on vcore anymore.
Persistent queues should be enabled, if not it utilizes the workers disk space to create the queues.
@@Vishwasp13 ok. If persistent queues are not enabled then it will use disk space automatically not the heap memory or we have to change some configuration to have this behaviour.
Yes persistent storage will be used. You need not configure anything.
Sir what is the major difference between vm queue and JMS queue
Awesome guide. I implemented as you suggested but did not observe same behavior in VMQ.
Deployed to CH with 2 workers, having created a scheduler, then 2 VM publish within scatter-gather. Each VM-Listener listens to input messages and wait for 5 secs. Observed that, every time app is running in single node and never runs in other node, any reason? What should I make to run in both workers?.
Scheduler->for-each(scatter-gather(VM-publish)).
VM-listener1->DW(wait-5secs)
VM-listener2->DW(wait-5secs)
is that persistent option checked ?
Good one. what if we have horizontal scaling in cloud with transient option selected in vm config. Does the message shared across workers ?
Transient remains in memory (JVM Heap space probably) due which it is local to a worker. Since its in-memory and restricted to a worker it doesn't gets shared, unless you enable the Persistent Queue option in Runtime Manager queues remain isolated.
Hi Vishwas, Will we be able to scale applications horizontally using a free subscription? Workers drop down is disabled for me. I see that it is enabled for you. Is there a permission which i am missing?
Scalability is not available on a free subscription, hence it's disabled for you.
VM queue don't have ACK operation?
Since this is not a full fledged messaging , you don't get access to these operations.