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

2.3 #18148

Closed
wants to merge 1,502 commits into from
Closed

2.3 #18148

wants to merge 1,502 commits into from

Conversation

lwiskowski
Copy link

@lwiskowski lwiskowski commented May 5, 2016

Bug Fixes Added for several issues #11498
and has_child and inner_hits for grandchild hit doesn't work #11118. Test suites changed as well to reflect new code.

jpountz and others added 30 commits March 3, 2016 10:29
This adds deprecation logging for the `and`, `fquery`, `filtered`, `or` an
`query` queries.

Closes #16885
Fix the object of the sentence to agree with the plural verb.
Docs: Fix bad date math index expression
With this commit we log a message to the deprecation log in case
somebody uses the deprecated 'transform' element in their mapping.

Relates #16910
… tasks

Adds task manager class and enables all activities to register with the task manager. Currently, the immutable Transport*Activity class represents activity itself shared across all requests. This PR adds and an additional structure Task that keeps track of currently running requests and can be used to communicate with these requests using TransportTaskAction.

Related to #15117
Sometimes action callers might be interested in having an access to the task that they have just initiated. This changes allows callers to get access to the Task object of the actions that they just started if the action supports the task management.
…cast actions

Now MasterNodeOperations, ReplicationAllShards, ReplicationSingleShard,  BroadcastReplication and BroadcastByNode actions keep track of their parent tasks.
Implements a simple task status for superclasses of ReplicationRequest to
show how you can do use the status.
Only tasks that extend CancellableTask can be cancelled using this mechanism. If a cancellable task has children it can elect to cancel all child tasks as well. In this case a special ban parent request is sent to all nodes. This request does two things: 1) it prevents any tasks with the banned parent task from being started, and 2) it cancels all currently running tasks that have the banned task as a parent. The ban is lifted as soon as the coordinating node notifies all other nodes that the cancelled task has finished executing. If the coordinating node leaves the cluster before it has a chance to lift its bans, all bans set by this coordinating node are automatically removed.

As an option a task can elect to automatically cancel all child tasks if their parent task was running on a node that just left the cluster. This option makes sense for cancellable heavy tasks that have no side-effects and only return results to the coordinating node. With the coordinating node gone, it doesn't make sense to run such tasks any longer since their results will be most likely discarded.
In the testCanFetchIndexStatus the task check can occur before the indexing process is started making the test to fail. This commit adds an additional lock to make sure we check tasks only after at least one of the tasks is registered.
This commit changes the URL for task operations from `/_tasks/{nodeId}/{taskId}` to `/_tasks/{taskId}`, where `{taskId}` has a form of nodeid:id
Tasks now contain timestamps indicating when the tasks were created and current run time
Test waits 10 seconds for all 10 aliases and documents to be created,
but it can take longer that that on slower machines.
…at can no longer be allocated to a node

Decommissioning a node or applying a filter inclusion / exclusion can potentially lead to many shards that need to be moved to other nodes. This commit reuses the model across all
shard movements in an allocation round: It calculates the shard model once and simulates the application of all shards that can be moved on this model.

Closes #16926
Redocument the `index.merge.scheduler.max_thread_count` setting
the examples all use `sum` for the `"score_mode"` field, but it isn't listed in the list of supported modes.
rjernst and others added 28 commits April 21, 2016 08:41
Deprecate camelCase settings magic
This commit backports commit 21b1da1
from master to 2.3.

Relates #17921
External node logs do not appear together with the "regular" node
logs but are instead printed before or after the test logs.
This makes debugging rather tricky as several test suites
can spin up external nodes with the same name and we cannot tell from the
logs which is used for which test.
Appending the class name of the test at least allows us to know
which suite the node is used in.
Update terms-query.asciidoc
Clarified which queries support the `_id` field
Sentence:
Default it `true`.
was replaced with
Defaults to `true`.
The source code example for the initial example was missing the correct JSON object formatting and syntax.  That has been fixed with my change.
Don't try to compute completion stats on a reader after we already closed it
With this commit we fix an issue that prevented to turn on
HTTP compression when using CORS. The problem boiled down
to a problematic order of the respective handlers in
Netty's pipeline.

Note that the same problem is already fixed in ES 5.0 by

Relates #18066
Fixes #18089
@jasontedor
Copy link
Member

This appears to have been opened in error.

@jasontedor jasontedor closed this May 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet