You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used JBeret for a simple quarkus application. Everything is working fine, thanks a lot for developing it.
I configured a jdbc data source to store the batch execution, all is stored in sqlserver.
My question is about having multiple pods sharing this database: we want to scale the service up and down, and in future even do active/passive deployment of our services. Is it possible to use JBeret in such configuration? Will I end up in having batchlet started on one node and executed on another, or everything remains local to the node that stated the processing. Also if one pod is killed while running a batchlet, will another node retry the execution, or we have just to restart a new batchlet?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I used JBeret for a simple quarkus application. Everything is working fine, thanks a lot for developing it.
I configured a jdbc data source to store the batch execution, all is stored in sqlserver.
My question is about having multiple pods sharing this database: we want to scale the service up and down, and in future even do active/passive deployment of our services. Is it possible to use JBeret in such configuration? Will I end up in having batchlet started on one node and executed on another, or everything remains local to the node that stated the processing. Also if one pod is killed while running a batchlet, will another node retry the execution, or we have just to restart a new batchlet?
Thanks in advance for the info
Beta Was this translation helpful? Give feedback.
All reactions