Skip to content

New nodes not joining the cluster properly #29

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.

Sign up for GitHub

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

Jump to bottom
Closed
clintongormley opened this issue Feb 19, 2010 · 5 comments
Closed

New nodes not joining the cluster properly #29

clintongormley opened this issue Feb 19, 2010 · 5 comments
Labels
>bug v0.05.0

Comments

@clintongormley
Copy link
Contributor

I start one node, insert various documents, run some queries - I get the correct results.

I start a new node, and wait for it to settle (even running optimize/flush/refresh)

When rerunning the same queries, I get different totals and fewer hits returned, eg instead of the default 10, I may get 4 or 5

Killing the other nodes and rerunning the queries returns the correct results

ta

clint
@clintongormley
Copy link
Contributor Author

Similarly, if I start with (eg) 3 nodes, then the queries return the correct results until I remove one or more nodes.

@kimchy
Copy link
Member

kimchy commented Feb 20, 2010

Is there a chance for a bash script that index documents (with curl) on a single node, then execute the query in question, pauses (for me to start the second node), and then runs the query again?

@clintongormley
Copy link
Contributor Author

Emailed to you

@kimchy
Copy link
Member

kimchy commented Feb 28, 2010

Can you run the test again? Fixed bunch of stuff which hopefully will resolve this (and if there are errors, you will now see then in the result).

@clintongormley
Copy link
Contributor Author

Looks like this is working now ++

This was referenced Dec 7, 2014
Closed
Closed
@clintongormley clintongormley mentioned this issue Apr 14, 2015
Closed
dadoonet added a commit that referenced this issue Jun 5, 2015
@dadoonet
Old common-codecs version in use
906326d 
Closes #29.
dadoonet added a commit that referenced this issue Jun 5, 2015
@dadoonet
Revert change made with #32.
0f5f57d 
Fix missing lib in assembly. relative to #29.
Closes #33.
dadoonet added a commit that referenced this issue Jun 5, 2015
@dadoonet
Update to Lucene 4.9.0
8c28e4b 
Closes #29.

(cherry picked from commit 7dc2231)
dadoonet added a commit that referenced this issue Jun 5, 2015
@dadoonet
Update to elasticsearch 1.4.0
814ec14 
Closes #29.

(cherry picked from commit 4a87b6b)
dadoonet added a commit that referenced this issue Jun 5, 2015
@dadoonet
Docs: make the welcome page more obvious
845e525 
One of the concern we have with our documentation is that it's hard for users to understand which plugin version they should use with a given elasticsearch version.

The change will consist of:

* have a clean and simple compatibility matrix on master branch
* remove list of versions in other branches

Closes #29.
dadoonet added a commit that referenced this issue Jun 5, 2015
@dadoonet
Docs: make the welcome page more obvious
3421168 
One of the concern we have with our documentation is that it's hard for users to understand which plugin version they should use with a given elasticsearch version.

The change will consist of:

* have a clean and simple compatibility matrix on master branch
* remove list of versions in other branches

Closes #29.
dadoonet added a commit that referenced this issue Jun 5, 2015
@dadoonet
Docs: make the welcome page more obvious
45492c0 
One of the concern we have with our documentation is that it's hard for users to understand which plugin version they should use with a given elasticsearch version.

The change will consist of:

* have a clean and simple compatibility matrix on master branch
* remove list of versions in other branches

Closes #29.
dadoonet pushed a commit that referenced this issue Jun 5, 2015
@xyu @dadoonet
Add smartcn_word & smartcn_sentence back for backwards compatibility
d34a2b0 
In f4d0d27 the deprecated `smartcn_sentence` tokenizer and deprecated
`smartcn_word` token filter were removed as the new all in one
`smartcn_tokenizer` should be used instead. However for those with pre-existing
indices with mappings that reference the deprecated tokenizer and token filter
this changes causes indexing and search errors.

This change preserves the `smartcn_sentence` tokenizer name and aliases it to
the new `smartcn_tokenizer`. The change set also reintroduces a `smartcn_word`
token filter that is a noop filter. The result of these changes should allow
elasticsearch instances with the existing deprecated mappings to upgrade and
take advantage of the new tokenizer in lucene.

(cherry picked from commit 25a0071)

Closes #29
dadoonet added a commit that referenced this issue Jun 9, 2015
@dadoonet
Implement new method scriptRemoved(CompiledScript) in `ScriptEngine…
1950ad9 
…Service`

This [PR](#8062) broke ScriptEngineService by adding a new method `scriptRemoved(CompiledScript)`.

Closes #29.

(cherry picked from commit 1fd05bc)
@donkoink donkoink mentioned this issue Jun 25, 2015
Closed
@makeyang makeyang mentioned this issue Sep 7, 2015
Closed
rmuir pushed a commit to rmuir/elasticsearch that referenced this issue Nov 8, 2015
@dadoonet
Add test for asciidoc format
cfd8344 
Related to elastic#29.
@johtani johtani mentioned this issue Nov 7, 2017
Closed
@GurjinderSingh GurjinderSingh mentioned this issue Jan 25, 2018
Closed
ywelsch pushed a commit to ywelsch/elasticsearch that referenced this issue Apr 24, 2018
@DaveCTurner
Introduce the FutureExecutor (elastic#29)
f0f77c8 
The FutureExecutor allows the legislator to schedule multiple tasks for future 
execution, rather than simply relying on handleWakeUp() to work out what needs
doing each time it is called.

The test implementation of FutureExecutor also adds a little extra variation in 
the scheduling of tasks. Apart from this, the rest of the implementation
remains unchanged: handleWakeUp() still works out what needs doing each time it
is called. This will be addressed in a subsequent change.
@Tiuser4567 Tiuser4567 mentioned this issue Oct 11, 2018
Closed
ClaudioMFreitas pushed a commit to ClaudioMFreitas/elasticsearch-1 that referenced this issue Nov 12, 2019
@jakommo
Merge pull request elastic#29 from jakommo/master
a8f001a 
EL package installation from url and Java simplification
henningandersen pushed a commit to henningandersen/elasticsearch that referenced this issue Jun 4, 2020
@cdahlqvist
Added MD5 id and made forcemerging optional as it is time consuming. (e…
a15a299 
…lastic#29)

* Added MD5 id and made forcemerging optional as it is time consuming.

* Added separate warmup phase

* Updated following review
@nkakouros nkakouros mentioned this issue Jul 1, 2020
Closed
@zoeliterally zoeliterally mentioned this issue Nov 28, 2022
Closed
@Alsheh Alsheh mentioned this issue Dec 21, 2022
Closed
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
@jimczi
Merge pull request elastic#29 from jimczi/challenges/index_sorting
6ca49ce 
Add index sorting challenges to nightly
Closes elastic#27
@mrklaney mrklaney mentioned this issue May 1, 2025
Open
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>bug v0.05.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kimchy @clintongormley