Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replicas >0 #9

Closed
erbg opened this issue Nov 2, 2022 · 6 comments
Closed

Replicas >0 #9

erbg opened this issue Nov 2, 2022 · 6 comments

Comments

@erbg
Copy link

erbg commented Nov 2, 2022

Hello,

I was trying to understand if BC supports more than 1 replica (POD) connected to an external Database.
Do you have some information about that?

Best regards

@lippertmarkus
Copy link
Owner

lippertmarkus commented Nov 2, 2022

Hello,
yes it's possible, but there are limitations:

  1. Multiple BC service tiers are not able to share session data between each other, so you need to enable sticky sessions (same person is always directed to the same pod) in your ingress controller.
  2. With sticky sessions enabled, if one of the pod fails, the users sticking to the failing instance can't transparently continue working on another one. If their "assigned" instance fails they would be redirected to the login prompt and need to log in again.

@erbg
Copy link
Author

erbg commented Nov 2, 2022

Wow, great.
Sticky sessions are already in place.

My i ask a second thing, what about Job Queue, how do you handle this?

@lippertmarkus
Copy link
Owner

What do you mean? Jobs are stored in the external database and are executed by any service tier that has the Job Queue enabled.

@erbg
Copy link
Author

erbg commented Nov 7, 2022

My question is always connected to a multi pod environment. If i have 2 PODs that have a Job Queue enabled. Is BC then executing a timer job just once on one POD or will it execute twice? Just to understand if i need a special deployment for the pods with Job Queue enabled.
Thanks.

@lippertmarkus
Copy link
Owner

BC will execute it just once

@erbg
Copy link
Author

erbg commented Nov 7, 2022

Great! Thanks

@erbg erbg closed this as completed Nov 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants