-
Notifications
You must be signed in to change notification settings - Fork 24.6k
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
Deprecate replication:async #10114
Comments
+1 to deprecate in 1.5, remove in 2.0 |
+1 |
1 similar comment
+1 |
@clintongormley can you deprecate it in the docs please for 1.5 |
Doc changes to deprecate async replication in 1.5.0 and 1.x Relates to #10114
Deprecated in the docs for 1.5.0, and removed from the docs and REST spec in 2.0. Still needs to be removed in the code. |
Just a note here. It sounds like we deprecated this in docs but we did not add |
Yes I think we should @dadoonet , can you open an issue or even take care of this with a PR against 1.x? |
`replication:async` has been deprecated in elasticsearch 1.5.0 and removed in master (2.0.0). See elastic/elasticsearch#10114. We need to do the same in RabbitMQ river plugin. Closes #91.
`replication:async` has been deprecated in elasticsearch 1.5.0 and removed in master (2.0.0). See elastic/elasticsearch#10114. We need to do the same in RabbitMQ river plugin. Closes #91. (cherry picked from commit fc3f394) (cherry picked from commit 1df982b)
`replication:async` has been deprecated in elasticsearch 1.5.0 and removed in master (2.0.0). See elastic/elasticsearch#10114. We need to do the same in RabbitMQ river plugin. Closes #91. (cherry picked from commit fc3f394)
Follow up for PR elastic#10171. As we discussed elastic#10114 (comment), we should also mark the code as deprecated so plugin developers know in advance that they need to adapt their code. I also added a `log` when using `replication` parameter in REST APIs but as `info` Level. I wonder if I should better log that as a `WARN` if `debug` level is set? So people in debug mode will see this information as a `WARN` while it won't pollute logs for each call when in default `INFO` log level.
Follow up for PR elastic#10171. As we discussed elastic#10114 (comment), we should also mark the code as deprecated so plugin developers know in advance that they need to adapt their code.
Follow up for PR elastic#10171. As we discussed elastic#10114 (comment), we should also mark the code as deprecated so plugin developers know in advance that they need to adapt their code.
Follow up for PR elastic#10171. As we discussed elastic#10114 (comment), we should also mark the code as deprecated so plugin developers know in advance that they need to adapt their code.
Follow up for PR #10171. As we discussed #10114 (comment), we should also mark the code as deprecated so plugin developers know in advance that they need to adapt their code.
Asynchronous replication will be removed in Elasticsearch 2.0. (elastic/elasticsearch#10114) Closes #1264
Doc changes to deprecate async replication in 1.5.0 and 1.x Relates to elastic#10114
Hey everyone, does this document needs to be updated to state that |
@fsaravia the Guide targets ES 1.4. Yes, it does need a big update for 2.0... i know, i know |
@clintongormley oh, sorry about that. I didn't realize it targets ES 1.4 :) |
Asynchronous replication will be removed in Elasticsearch 2.0. (elastic/elasticsearch#10114) Closes #1264
Async replication clashes with index sealing (#10032). Another downside of async replication is that clients cannot be sure that changes have reached the replica. The benefits of async replication can be achieved simply by having more clients (threads or forks).
Let's deprecate this in 1.5
The text was updated successfully, but these errors were encountered: