Skip to main content

friendica (DFRN) - Link to source

Locks with hostname

!Friendica Developers
Calling @Hypolite Petovan and @Michael Vogel for support at github.com/friendica/friendica…

I do want to alter the way how locks are working to make parallel hosts/nodes possible. I think the logic itself is pretty straight forward and final.

BUT - how can I upgrade the lock table without using it during the update process itself, it's a gordon knot :-/
I think about using a new method at DBStructure: github.com/friendica/friendica… and execute it before using the lock.

Do you think it works? At least my local nodes are working, but I'm totally unsure about it yet ..

I'd like to finish this PR for 2021.12 as another preparation for making Friendica "cluster ready" :D


Add hostname to Locks by nupplaphil · Pull Request #10601 · friendica/friendica

Superseded #9114 This should help with #9095 We now add the hostname to each lock as well. The hostname is detected based on either uname -n or per environment variable NODE_NAME. This will have th...
GitHub
#9114 #9095 @Hypolite Petovan @Michael Vogel !Friendica Developers
This entry was edited (3 years ago)

Friendica Developers reshared this.

in reply to Philipp Holzer

Philipp Holzer
friendica (DFRN) - Link to source
Philipp Holzer
•
The preupdate routine is called during the overall update process before the dbstructure update but after the lock "dbupdate" is acquired.
in reply to Philipp Holzer

Philipp Holzer
friendica (DFRN) - Link to source
Philipp Holzer
•
Any idea @Michael Vogel ? :) I'm really stuck here and it's one major piece in the puzzle to make Friendica cluster-ready ;-)
@Michael Vogel
Unknown parent

Philipp Holzer
friendica (DFRN) - Link to source
Philipp Holzer
•
@Michael Vogel @Hypolite Petovan @Friendica Developers but wouldn't that possibly create a race condition, because a 2nd worker would start another update and wouldn't find the lock anymore so update it again?
@Hypolite Petovan @Michael Vogel @Friendica Developers
⇧