Skip to content

Conversation

@s1monw
Copy link
Contributor

@s1monw s1monw commented Sep 21, 2016

This commit changes the default behavior of _flush to block if other flushes are ongoing.
This also removes the use of FlushNotAllowedException and instead simply return immediately
by skipping the flush. Users should be aware if they set this option that the flush might or might
not flush everything to disk ie. no transactional behavior of some sort.

Closes #20569

This commit changes the default behavior of `_flush` to block if other flushes are ongoing.
This also removes the use of `FlushNotAllowedException` and instead simply return immediately
by skipping the flush. Users should be aware if they set this option that the flush might or might
not flush everything to disk ie. no transactional behavior of some sort.

Closes elastic#20569
@bleskes
Copy link
Contributor

bleskes commented Sep 21, 2016

LGTM. Thx @s1monw !

@s1monw
Copy link
Contributor Author

s1monw commented Sep 21, 2016

FYI - I will open a sep issue for the migration guide since this goes in to master and we only need that entry on 5.x and 5.0

@s1monw s1monw merged commit 0151974 into elastic:master Sep 21, 2016
s1monw added a commit that referenced this pull request Sep 21, 2016
This commit changes the default behavior of `_flush` to block if other flushes are ongoing.
This also removes the use of `FlushNotAllowedException` and instead simply return immediately
by skipping the flush. Users should be aware if they set this option that the flush might or might
not flush everything to disk ie. no transactional behavior of some sort.

Closes #20569
s1monw added a commit that referenced this pull request Sep 21, 2016
This commit changes the default behavior of `_flush` to block if other flushes are ongoing.
This also removes the use of `FlushNotAllowedException` and instead simply return immediately
by skipping the flush. Users should be aware if they set this option that the flush might or might
not flush everything to disk ie. no transactional behavior of some sort.

Closes #20569
s1monw added a commit to s1monw/elasticsearch that referenced this pull request Sep 21, 2016
This change adds a note to the migration guide for the change of the
default value from `false` to `true`.

Relates to elastic#20597
s1monw added a commit that referenced this pull request Sep 21, 2016
This change adds a note to the migration guide for the change of the
default value from `false` to `true`.

Relates to #20597
s1monw added a commit that referenced this pull request Sep 21, 2016
This change adds a note to the migration guide for the change of the
default value from `false` to `true`.

Relates to #20597
@s1monw s1monw added the >bug label Sep 21, 2016
s1monw added a commit to s1monw/elasticsearch that referenced this pull request Sep 22, 2016
This is a issue in all 2.x releases that if we run into a FlushNotAllowedEngineException
on a replica (ie. a flush is already running) we fail the replica. We should just ignore this
excepiton and not fail the shard.

Note: this is against 2.x only. Master changed in elastic#20597
Relates to elastic#20569
s1monw added a commit that referenced this pull request Sep 23, 2016
This is a issue in all 2.x releases that if we run into a FlushNotAllowedEngineException
on a replica (ie. a flush is already running) we fail the replica. We should just ignore this
excepiton and not fail the shard.

Note: this is against 2.x only. Master changed in #20597
Relates to #20569
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