Fix LocalIndexFollowingIT#testRemoveRemoteConnection() test#38709
Merged
martijnvg merged 2 commits intoelastic:masterfrom Feb 14, 2019
Merged
Fix LocalIndexFollowingIT#testRemoveRemoteConnection() test#38709martijnvg merged 2 commits intoelastic:masterfrom
martijnvg merged 2 commits intoelastic:masterfrom
Conversation
* During fetching remote mapping if remote client is missing then `NoSuchRemoteClusterException` was not handled. * When adding remote connection, check that it is really connected before continue-ing to run the tests. Relates to elastic#38695
Collaborator
|
Pinging @elastic/es-distributed |
dnhatn
approved these changes
Feb 13, 2019
Member
dnhatn
left a comment
There was a problem hiding this comment.
LGTM. Thanks @martijnvg for fixing the test.
jasontedor
added a commit
to jasontedor/elasticsearch
that referenced
this pull request
Feb 14, 2019
* elastic/master: Remove immediate operation retry after mapping update (elastic#38873) Remove mentioning of types from bulk API docs (elastic#38896) SQL: change JDBC setup URL in the documentation (elastic#38564) Skip BWC tests in checkPart1 and checkPart2 (elastic#38730) Enable silent FollowersCheckerTest (elastic#38851) Update TESTING.asciidoc with platform specific instructions (elastic#38802) Use consistent view of realms for authentication (elastic#38815) Stabilize RareClusterState (elastic#38671) Increase Timeout in UnicastZenPingTests (elastic#38893) Do not recommend installing vagrant-winrm elastic#38887 _cat/indices with Security, hide names when wildcard (elastic#38824) SQL: fall back to using the field name for column label (elastic#38842) Fix LocalIndexFollowingIT#testRemoveRemoteConnection() test (elastic#38709) Remove joda time mentions in documentation (elastic#38720) Add enabled status for token and api key service (elastic#38687)
martijnvg
added a commit
that referenced
this pull request
Feb 18, 2019
* During fetching remote mapping if remote client is missing then `NoSuchRemoteClusterException` was not handled. * When adding remote connection, check that it is really connected before continue-ing to run the tests. Relates to #38695
martijnvg
added a commit
that referenced
this pull request
Feb 18, 2019
* During fetching remote mapping if remote client is missing then `NoSuchRemoteClusterException` was not handled. * When adding remote connection, check that it is really connected before continue-ing to run the tests. Relates to #38695
martijnvg
added a commit
that referenced
this pull request
Feb 18, 2019
* During fetching remote mapping if remote client is missing then `NoSuchRemoteClusterException` was not handled. * When adding remote connection, check that it is really connected before continue-ing to run the tests. Relates to #38695
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
NoSuchRemoteClusterExceptionwas not handled. (Should fix the error in LocalIndexFollowingIT#testRemoveRemoteConnection failure #38695's issue description)before continue-ing to run the tests. (Should fix failure described in LocalIndexFollowingIT#testRemoveRemoteConnection failure #38695 (comment), the leader index will be created after the test verified that the remove connection is really connected, which reduces the time spent in assertBusy(...))