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

clustering #36

Open
debonair opened this issue Jul 4, 2016 · 3 comments
Open

clustering #36

debonair opened this issue Jul 4, 2016 · 3 comments

Comments

@debonair
Copy link

debonair commented Jul 4, 2016

I am having trouble clustering the bpmn using pm2. I can only find process that were created by that node of the cluster. is it possible to refresh the process cache from what has been persisted to the data store?

@TomKaltz
Copy link

TomKaltz commented Aug 5, 2016

I'm curious about this too @debonair do you have any new findings?

@wiltshirek
Copy link

Yeah, we had the same issue a while back. Had to go with sticky LB sessions
for the mongodb connection.

On Mon, Jul 4, 2016 at 9:33 AM, Duma Mtungwa [email protected]
wrote:

I am having trouble clustering the bpmn using pm2. I can only find process
that were created by that node of the cluster. is it possible to refresh
the process cache from what has been persisted to the data store?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#36, or mute the thread
https://github.com/notifications/unsubscribe/AE3y74sO-TcHO_gWHX3qrodCV7mb2W3kks5qSQuNgaJpZM4JEX9l
.

Ken Wiltshire* |* Computer Applications Developer
5715 Ave N | Brooklyn, NY 11234

Direct (347) 675-5213

@wiltshirek
Copy link

More info here. The sticky solution works for that current session only.
If your design calls for updates that can cross sessions (which is going to
be the case in most instances by nature) then you'll have to go with one
mongodb instance.

I guess you could use two mongo instances with sticky sessions and mongo
replication to avoid having a single point of failure.

On Fri, Aug 5, 2016 at 11:26 AM, Ken Wiltshire [email protected] wrote:

Yeah, we had the same issue a while back. Had to go with sticky LB
sessions for the mongodb connection.

On Mon, Jul 4, 2016 at 9:33 AM, Duma Mtungwa [email protected]
wrote:

I am having trouble clustering the bpmn using pm2. I can only find
process that were created by that node of the cluster. is it possible to
refresh the process cache from what has been persisted to the data store?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#36, or mute the thread
https://github.com/notifications/unsubscribe/AE3y74sO-TcHO_gWHX3qrodCV7mb2W3kks5qSQuNgaJpZM4JEX9l
.

Ken Wiltshire* |* Computer Applications Developer
5715 Ave N | Brooklyn, NY 11234

Direct (347) 675-5213

Ken Wiltshire* |* Computer Applications Developer
5715 Ave N | Brooklyn, NY 11234

Direct (347) 675-5213

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

3 participants