Skip to content

[Lock] Describe reliability in Lock #8847

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

Closed
wants to merge 2 commits into from

Conversation

jderusse
Copy link
Member

@jderusse jderusse commented Dec 7, 2017

No description provided.

@xabbuh xabbuh added the Lock label Jan 2, 2018
@xabbuh xabbuh added this to the 3.4 milestone Jan 2, 2018
To avoid that someone else acquires a lock after a restart, we recommend
to delayed service start and wait at least as long as the longest lock TTL.

.. tips::
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

.. tip::

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed. Sorry for the delay

All concurrent processes MUST use the same configuration. with the same
amount of managed stored and the same endpoint.

.. tips::
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here

@javiereguiluz
Copy link
Member

Thanks Jérémy.

javiereguiluz added a commit that referenced this pull request Mar 23, 2018
This PR was merged into the 3.4 branch.

Discussion
----------

[Lock] Describe reliability in Lock

Commits
-------

b41a457 Describe reliability in Lock
xabbuh added a commit that referenced this pull request Mar 23, 2018
xabbuh added a commit that referenced this pull request Mar 23, 2018
javiereguiluz added a commit to javiereguiluz/symfony-docs that referenced this pull request Mar 26, 2018
* 3.4: (21 commits)
  added Sam in the core team
  minor symfony#9494 [Console] Change use statement for Process Helper (krizon)
  Specify how provide a high availability
  Use FQCN as service ID
  [symfony#8847] fix another directive
  [symfony#8847] fix tip directive
  Describe reliability in Lock
  Propose identical comparison
  [symfony#9195] fix a minor typo
  Fixed some variable names
  fix some security config examples
  Made explicit testing dependencies
  No more ambiguity on prod mode
  Mention the adder/remover support of PropertyInfo
  ...
@jderusse jderusse deleted the lock-reliability branch April 18, 2020 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants