Skip to content

Don't kill master server if replica crash was expected #114

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

Merged
merged 3 commits into from
Aug 16, 2018

Conversation

sergw
Copy link
Contributor

@sergw sergw commented Aug 16, 2018

No description provided.

@sergw sergw requested a review from Totktonada August 16, 2018 07:42
Copy link
Member

@Totktonada Totktonada left a comment

Choose a reason for hiding this comment

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

LGTM, except wording in a comment (see below). No need re-review again with me after the changes in the comment.

@sergepetrenko Can you please test the fix before it will be merged into the test-run:master?

0,
-signal.SIGKILL,
-signal.SIGTERM)
# if replica crashed but this crash is exptected
Copy link
Member

Choose a reason for hiding this comment

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

exptected → expected

Copy link
Member

Choose a reason for hiding this comment

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

From test-run point there are default and non-default servers. We can write it as 'non-default server (say, replica)'.

-signal.SIGKILL,
-signal.SIGTERM)
# if replica crashed but this crash is exptected
# don't kill the master server and crash detectors
Copy link
Member

Choose a reason for hiding this comment

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

master server → default server (say, replication master)

@sergepetrenko
Copy link
Contributor

@Totktonada The fix works fine.

@sergw sergw force-pushed the fix-master-kill-if-crash-expected-on-replica branch from 8796006 to 5579ff9 Compare August 16, 2018 16:00
@sergw sergw merged commit 822eed3 into master Aug 16, 2018
@sergw sergw deleted the fix-master-kill-if-crash-expected-on-replica branch August 16, 2018 16:03
@sergw sergw self-assigned this Aug 16, 2018
Totktonada added a commit that referenced this pull request Apr 29, 2019
This update contains changes from 0.6.5 release (cited below) and usage
of yaml.safe_load() instead of yaml.load() in tarantool-python tests
(doesn't affect test-run behaviour).

The reason why it is updated here is just to keep things in sync and,
second, to eliminate usage of yaml.load() w/o an explicit loader
everywhere where it is possible. The latter is because it was banned in
recent versions of pyyaml in Gentoo Linux; see [1].

[1]: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=79ba924d94cb0cf8559565178414c2a1d687b90c

# tarantool-python 0.6.5

## Breaking changes

This release should not break existing code.

## New features

* Added MeshConnection that allows to switch between nodes from a user
  provided list if a current node is down using round-robin strategy (#106).
* Added connection_timeout parameter to Connection (#115).

## Bugfixes

* Fixed auto-reconnection in Connection.
* Eliminated deprecation warnings on Python 3 (#114).
* Added TCP_NODELAY back (it was removed in 0.6.4) (#127).

https://github.com/tarantool/tarantool-python/releases/tag/0.6.5
Totktonada added a commit that referenced this pull request Apr 30, 2019
This update contains changes from 0.6.5 release (cited below) and usage
of yaml.safe_load() instead of yaml.load() in tarantool-python tests
(doesn't affect test-run behaviour).

The reason why it is updated here is just to keep things in sync and,
second, to eliminate usage of yaml.load() w/o an explicit loader
everywhere where it is possible. The latter is because it was banned in
recent versions of pyyaml in Gentoo Linux; see [1].

There was also related change 38400e9
('Update pyyaml version') where yaml.load() was replaced with
yaml.safe_load() within test-run itself.

[1]: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=79ba924d94cb0cf8559565178414c2a1d687b90c

# tarantool-python 0.6.5

## Breaking changes

This release should not break existing code.

## New features

* Added MeshConnection that allows to switch between nodes from a user
  provided list if a current node is down using round-robin strategy (#106).
* Added connection_timeout parameter to Connection (#115).

## Bugfixes

* Fixed auto-reconnection in Connection.
* Eliminated deprecation warnings on Python 3 (#114).
* Added TCP_NODELAY back (it was removed in 0.6.4) (#127).

https://github.com/tarantool/tarantool-python/releases/tag/0.6.5
Totktonada added a commit that referenced this pull request Apr 30, 2019
This update contains changes from 0.6.5 release (cited below) and usage
of yaml.safe_load() instead of yaml.load() in tarantool-python tests
(doesn't affect test-run behaviour).

The reason why it is updated here is just to keep things in sync and,
second, to eliminate usage of yaml.load() w/o an explicit loader
everywhere where it is possible. The latter is because it was banned in
recent versions of pyyaml in Gentoo Linux; see [1].

There was also related change 38400e9
('Update pyyaml version') where yaml.load() was replaced with
yaml.safe_load() within test-run itself.

[1]: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=79ba924d94cb0cf8559565178414c2a1d687b90c

# tarantool-python 0.6.5

## Breaking changes

This release should not break existing code.

## New features

* Added MeshConnection that allows to switch between nodes from a user
  provided list if a current node is down using round-robin strategy (#106).
* Added connection_timeout parameter to Connection (#115).

## Bugfixes

* Fixed auto-reconnection in Connection.
* Eliminated deprecation warnings on Python 3 (#114).
* Added TCP_NODELAY back (it was removed in 0.6.4) (#127).

https://github.com/tarantool/tarantool-python/releases/tag/0.6.5
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

Successfully merging this pull request may close these issues.

3 participants