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

Flush API: remove refresh flag #3689

Closed
kimchy opened this Issue Sep 13, 2013 · 0 comments

Comments

Projects
None yet
1 participant
@kimchy
Copy link
Member

commented Sep 13, 2013

Refresh flag in flush is problematic, since the shards refresh is allowed to execute on is different compared to the flush shards. In order to do flush and then refresh, they should be executed as separate APIs when needed.

@kimchy kimchy closed this in 7cc48c8 Sep 13, 2013

kimchy added a commit that referenced this issue Sep 13, 2013

Flush API: remove refresh flag
Refresh flag in flush is problematic, since the shards refresh is allowed to execute on is different compared to the flush shards. In order to do flush and then refresh, they should be executed as separate APIs when needed.
closes #3689

kimchy added a commit that referenced this issue Sep 13, 2013

Flush API: remove refresh flag
Refresh flag in flush is problematic, since the shards refresh is allowed to execute on is different compared to the flush shards. In order to do flush and then refresh, they should be executed as separate APIs when needed.
closes #3689

mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015

Flush API: remove refresh flag
Refresh flag in flush is problematic, since the shards refresh is allowed to execute on is different compared to the flush shards. In order to do flush and then refresh, they should be executed as separate APIs when needed.
closes elastic#3689

mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015

Flush API: remove refresh flag
Refresh flag in flush is problematic, since the shards refresh is allowed to execute on is different compared to the flush shards. In order to do flush and then refresh, they should be executed as separate APIs when needed.
closes elastic#3689
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.