| 688ecce | Jason Tedor | 16 February 2018, 12:30:15 UTC | Fix test concurrent remote connection updates This test has a race condition. The action listener used to listen for connections has a guard against being executed twice. However, this listener can be executed twice. After on success is invoked the test starts to tear down. At this point, the threads the test forked will terminate and the remote cluster connection will be closed. However, a thread forked to the management thread pool by the remote cluster connection can still be executing and try to continue connecting. This thread will be cancelled when the remote cluster connection is closed and this leads to the action listener being invoked again. To address this, we explicitly check that the reason that on failure was invoked was cancellation, and we assert that the listener was already previously invoked. Interestingly, this issue has always been present yet a recent change (#28667) exposed errors that occur on tasks submitted to the thread pool and were silently being lost. Relates #28695 | 16 February 2018, 12:43:16 UTC |
| 2fc2c67 | Martijn van Groningen | 16 February 2018, 10:09:56 UTC | Muted test Relates to #28695 | 16 February 2018, 10:11:38 UTC |
| b107bc9 | Russ Cam | 16 February 2018, 03:20:46 UTC | Update description for using a stored script (#27803) | 16 February 2018, 03:20:46 UTC |
| 187674c | Andy Bristol | 16 February 2018, 00:04:26 UTC | [TEST] AwaitsFix a test in ESLoggingHandlerIT For #27306 | 16 February 2018, 00:06:25 UTC |
| 84e066d | Cladis | 15 February 2018, 23:56:50 UTC | Grammar: "by geographically" → "geographically" (#28595) | 16 February 2018, 00:00:22 UTC |
| 1e0eeb4 | Clinton Gormley | 15 February 2018, 19:30:43 UTC | Fixed es_release_notes.pl script to work with the new github labels It also now ignores docs, test, non-issue, refactoring, and build | 15 February 2018, 19:31:40 UTC |
| d9b40cd | Jason Tedor | 15 February 2018, 16:59:12 UTC | Handle throws on tasks submitted to thread pools When we submit a task to a thread pool for asynchronous execution, we are returned a future. Since we submitted to go asynchronous, these futures are not inspected for failure (we would have to block a thread to do that). While we have on failure handlers for exceptions that are thrown during execution, we do not handle throwables that are not exceptions and these end up silently lost. This commit adds a check after the runnable returns that inspects the status of the future. If an unhandled throwable occurred during execution, this throwable is propogated out where it will land in the uncaught exception handler. Relates #28667 | 15 February 2018, 17:13:23 UTC |
| c6f23d4 | Jason Tedor | 15 February 2018, 17:12:10 UTC | Fix location of exceptions helper tests These tests were dropped into the wrong location after a backport from master where where core has been moved to server. Yet, this is not the case in 5.6 so this commit moves this test suite from server to core in 5.6. Relates #28691 | 15 February 2018, 17:12:57 UTC |
| 3920f51 | Jason Tedor | 15 February 2018, 14:48:52 UTC | Lift error finding utility to exceptions helpers We have code used in the networking layer to search for errors buried in other exceptions. This code will be useful in other locations so with this commit we move it to our exceptions helpers. Relates #28691 | 15 February 2018, 14:57:21 UTC |
| 12a170c | Alex Moros Marco | 03 February 2018, 11:41:22 UTC | [Docs] Add missing word in nested.asciidoc (#28507) | 15 February 2018, 14:03:12 UTC |
| 14664ab | Nhat Nguyen | 02 February 2018, 16:20:38 UTC | Synced-flush should not seal index of out of sync replicas (#28464) Today the correctness of synced-flush is guaranteed by ensuring that there is no ongoing indexing operations on the primary. Unfortunately, a replica might fall out of sync with the primary even the condition is met. Moreover, if synced-flush mistakenly issues a sync_id for an out of sync replica, then that replica would not be able to recover from the primary. ES prevents that peer-recovery because it detects that both indexes from primary and replica were sealed with the same sync_id but have a different content. This commit modifies the synced-flush to not issue sync_id for out of sync replicas. This change will report the divergence issue earlier to users and also prevent replicas from getting into the "unrecoverable" state. Relates #10032 | 14 February 2018, 19:51:42 UTC |
| 3569db8 | Andrew Anderson | 13 February 2018, 07:47:01 UTC | Fixed typo in search for wrong type (#28645) | 13 February 2018, 18:42:54 UTC |
| 24c10ad | Colin Goodheart-Smithe | 12 February 2018, 14:54:16 UTC | [TEST] Adds extra information to failing assertion | 12 February 2018, 15:12:27 UTC |
| 32d7b5e | Martijn van Groningen | 12 February 2018, 10:28:40 UTC | [TEST] Changed how stash dumps are logged in yaml tests in case of failures Currently if a yaml test has a teardown and a test is failing then a stash dump of a request in the teardown is logged instead of a stash dump of a request in the test itself. By handling the logging of stash dumps separately for setup, tests and teardown yaml sections we shouldn't miss the stash dump of request/response that is actually causing the yaml test to fail. | 12 February 2018, 14:04:11 UTC |
| 327bc19 | Boaz Leskes | 12 February 2018, 10:56:13 UTC | TransportShardBulkAction#shardOperationOnReplica - log unexpected exception's trace We have an assertion that checks that we only get mapping exceptions or version conflicts as document failures. If we get something else we should log what it is. | 12 February 2018, 10:56:13 UTC |
| efb0cc9 | Jason Tedor | 11 February 2018, 16:10:40 UTC | Disable console logging in the Windows service When Elasticsearch is run as a service we should not use the console logger otherwise we end up duplicating logging (to the Elasticsearch logs and whereever standard output is captured). Previously we disabled the console logger when started as a service using systemd (otherwise the console logs are duplicated to the journal). This commit does the same for the Windows service, starting Elasticsearch with the --quiet flag to avoid standard output being written to the service stdout logs. Relates #28618 | 11 February 2018, 16:11:57 UTC |
| d370b1f | Martijn van Groningen | 08 February 2018, 23:25:37 UTC | Fixed a bug that prevents pipelines to load that use stored scripts after a restart. The bug was caused because the ScriptService had no reference to a ClusterState instance, because it received the ClusterState after the PipelineStore. This only is the case after a restart. A bad side effect is that during a restart, any pipeline to be loaded after the pipeline that uses a stored script, was never loaded, which caused many pipeline to be missing in bulk / index request api calls. | 09 February 2018, 17:39:18 UTC |
| 070c3ec | Islam Heggo | 07 February 2018, 16:30:03 UTC | Correct the explanation of load time percentiles (#28510) * Correct the explanation of load time percentiles * Adjusting the percentile clarification Eliminating the false sentence about majority of load time | 09 February 2018, 00:18:44 UTC |
| c8b042c | Jason Tedor | 08 February 2018, 19:23:24 UTC | Fix race condition in queue size test The queue size test has a race condition. Namely the offering thread can run so quickly completing all of its offering iterations before the queue size thread ever has a chance to run a single size poll iteration. This means that the size will never actually be polled and the test can spuriously fail. What we really want to do here, since this test is checking for a race condition between polling the size of the queue and offers to the queue, we want to execute each iteration in lockstep giving the threads multiple changes for the race between polling the size and offers to occur. This commit addresses this by running the two threads in lockstep for multiple iterations so that they have multiple chances to race. Relates #28584 | 08 February 2018, 19:26:33 UTC |
| 234c00e | Jason Tedor | 08 February 2018, 11:54:39 UTC | Fix size blocking queue to not lie about its weight Today when offering an item to a size blocking queue that is at capacity, we first increment the size of the queue and then check if the capacity is exceeded or not. If the capacity is indeed exceeded, we do not add the item to the queue and immediately decrement the size of the queue. However, this incremented size is exposed externally even though the offered item was never added to the queue (this is effectively a race on the size of the queue). This can lead to misleading statistics such as the size of a queue backing a thread pool. This commit fixes this issue so that such a size is never exposed. To do this, we replace the hidden CAS loop that increments the size of the queue with a CAS loop that only increments the size of the queue if we are going to be successful in adding the item to the queue. Relates #28557 | 08 February 2018, 13:42:19 UTC |
| c5d48f7 | Christoph Büscher | 07 February 2018, 16:26:08 UTC | [Tests] Relax assertion in SuggestStatsIT (#28544) The test expects suggest times in milliseconds that are strictly positive. Internally they are measured in nanos, it is possible that on really fast execution this is rounded to 0L, so this should also be an accepted value. Closes #28543 | 07 February 2018, 16:30:51 UTC |
| f8bc432 | Jason Tedor | 07 February 2018, 03:49:35 UTC | Skip verify versions for buggy cgroup2 handling Versions 5.1.1 to 5.3.0 of Elasticsearch had a problem where these versions did not handle new kernels properly due to improper handling of cgroup v2. On Linux kernels that support cgroup2 and the unified hierarchy is mounted, Elasticsearch would never start. This means tests on such systems where we try to start Elasticsearch will never succeed. This commit skips these tests on OS that have the unified cgroup v2 hierarchy. | 07 February 2018, 03:54:02 UTC |
| d11a352 | Martijn van Groningen | 01 November 2017, 06:34:14 UTC | Include the _index, _type and _id to nested search hits in the top_hits and inner_hits response. Also include _type and _id for parent/child hits inside inner hits. In the case of top_hits aggregation the nested search hits are directly returned and are not grouped by a root or parent document, so it is important to include the _id and _index attributes in order to know to what documents these nested search hits belong to. Closes #27053 | 05 February 2018, 14:29:02 UTC |
| 542def4 | Jim Ferenczi | 02 February 2018, 15:33:48 UTC | Mark synonym_graph as beta in the docs (#28496) We do want to keep this functionality in the future and we provide support for it. This change is a first step towards replacing the `synonym` token filter with `synonym_graph`. | 02 February 2018, 15:38:18 UTC |
| 79fe64e | Christoph Büscher | 02 February 2018, 10:00:07 UTC | [Docs] Move callouts in range.asciidoc (#28264) Currently the callouts for this section are below all the examples, making it harder to relate them to the snippets. Instead they should be moved closer to the examples. | 02 February 2018, 10:30:29 UTC |
| 576c47e | Lisa Cawley | 01 February 2018, 21:36:06 UTC | [DOCS] Build Elasticsearch Reference from elasticsearch repo (#28469) | 01 February 2018, 21:43:10 UTC |
| 3f065c7 | Luca Cavanna | 25 January 2018, 13:34:56 UTC | REST high-level client: move to POST when calling API to retrieve which support request body (#28342) It has been pointed out that GET with body may cause problems to some proxies. We are then switching to POST the API that retrieve info and support a request body. Closes #28326 | 01 February 2018, 11:03:22 UTC |
| 24c1a59 | Molly Struve | 01 February 2018, 08:01:12 UTC | Update 5.6 Breaking Changes doc (#28470) Added a section about the breaking changes made to referencing parent docs in aggregations and scripts. | 01 February 2018, 08:01:12 UTC |
| bfad8c3 | Luca Cavanna | 30 January 2018, 12:19:08 UTC | REST high-level client: Fix parsing of script fields (#28395) Script fields can get a bit more complicated than just stored fields. A script can return null, an object and also an array. Extended parsing to support such valid values. Also renamed util method from `parseStoredFieldsValue` to `parseFieldsValue` given that it can parse stored fields but also script fields, anything that's returned as `fields`. Closes #28380 | 31 January 2018, 11:24:31 UTC |
| 12101ed | Vlad Holubiev | 31 January 2018, 10:55:53 UTC | [Docs] Fix typo in inner-hits.asciidoc (#27998) | 31 January 2018, 11:00:17 UTC |
| f3d4fd9 | Alexander Reelsen | 30 January 2018, 18:15:33 UTC | Version: Bump to 5.6.8 Also add BWC indices | 30 January 2018, 18:15:52 UTC |
| bbb1911 | Nik Richers | 30 January 2018, 15:36:23 UTC | Update version to 5.6.7 (#28445) Update version to 5.6.7 for the release today. | 30 January 2018, 15:36:23 UTC |
| cb566af | Lee Hinman | 29 January 2018, 16:23:15 UTC | Add descriptions to bulk tasks Related to #21768 | 29 January 2018, 16:23:15 UTC |
| 0b1faef | Christoph Büscher | 29 January 2018, 11:11:59 UTC | [Tests] Fix potential NPE in RequestTests (#28391) Previuosly SearchRequest#source would rarely be null because the empty constructor was used. We shouldn't use that constructor in the test. Closes #28388 | 29 January 2018, 11:11:59 UTC |
| 7fad929 | Boaz Leskes | 29 January 2018, 08:38:12 UTC | added release notes for 5.6.7 | 29 January 2018, 08:38:12 UTC |
| ae751b4 | Jason Tedor | 26 January 2018, 14:07:12 UTC | Add note to docs regarding multi-get ordering The implementation maintains the order of the original requests yet this functionality is not documented. This commit adds a note to the docs regarding the ordering of responses to an multi-get request. Relates #28356 | 26 January 2018, 14:10:09 UTC |
| 40f09d7 | Antonio Matarrese | 26 January 2018, 11:22:42 UTC | Fix string terms get key as number to see integers Currently this method parses the string as a double. This means that it might lose accuracy if the value is a long that is greater than 2^52. This commit changes this method to try to detect whether the string represents a long first. | 26 January 2018, 11:34:15 UTC |
| 4669214 | Alex Moros Marco | 25 January 2018, 10:35:50 UTC | [Docs] Fix explanation for `from` and `size` example (#28320) | 25 January 2018, 10:37:52 UTC |
| f13a490 | Alex Moros Marco | 24 January 2018, 16:43:01 UTC | [Doc] Fixs typo in reverse-nested-aggregation.asciidoc (#28348) | 24 January 2018, 16:45:48 UTC |
| 0fa58d2 | Simon Willnauer | 23 January 2018, 15:57:26 UTC | Ensure we protect Collections obtained from scripts from self-referencing (#28335) Self referencing maps can cause SOE if they are iterated ie. in their toString methods. This chance adds some protected to the usage of those collections. | 24 January 2018, 15:32:37 UTC |
| bbf9edd | Christoph Büscher | 18 January 2018, 18:43:23 UTC | [Docs] Remove typo in painless-getting-started.asciidoc | 19 January 2018, 09:24:02 UTC |
| 2142af6 | Jason Tedor | 18 January 2018, 21:00:10 UTC | Fix packaging test when checking for cgroups v2 This commit fixes the packaging tests that check for whether or not cgroups v2 are enabled. The problem was that if cgroups v2 were not enabled the mount | grep command would fail with non-zero exit status killing the test. This commit fixes the issue by avoiding that command failing if cgroups v2 are not enabled. | 18 January 2018, 21:03:14 UTC |
| 09effca | Jason Tedor | 18 January 2018, 15:54:09 UTC | Skip rolling upgrades for buggy cgroup2 handling Versions 5.1.1 to 5.3.0 of Elasticsearch had a problem where these versions did not handle new kernels properly due to improper handling of cgroup v2. On Linux kernels that support cgroup2 and the unified hierarchy is mounted, Elasticsearch would never start. This means rolling upgrade tests on such systems will never succeed. This commit skips these tests on OS that have the unified cgroup v2 hierarchy. Relates #28267 | 18 January 2018, 15:54:09 UTC |
| 16f9c04 | Jason Tedor | 18 January 2018, 15:50:27 UTC | Skip packaging upgrade test when cgroups v2 enabled Versions 5.1.1 to 5.3.0 of Elasticsearch had a problem where these versions did not handle new kernels properly due to improper handling of cgroup v2. On Linux kernels that support cgroup2 and the unified hierarchy is mounted, Elasticsearch would never start. This means that the packaging upgrade tests on such systems will never succeed. This commit skips these tests on OS that have the unified cgroup v2 hierarchy. Relates #28278 | 18 January 2018, 15:52:49 UTC |
| 88436ff | javanna | 18 January 2018, 11:56:54 UTC | [TEST] fix RequestTests#testSearch in case search source is not set The search request body can never be null as `SearchRequest` doesn't allow the inner `SearchSourceBuilder` to be null. Instead, when search source is not set, the request body is going to be an empty json object (`{}``) | 18 January 2018, 12:04:09 UTC |
| 3a92ca2 | Tanguy Leroux | 17 January 2018, 12:35:29 UTC | [Test] Wait for no relocating shards in indices.stats/13_fields tests MixedClusterClientYamlTestSuiteIT sometimes fails when executing the indices.stats/13_fields/* REST tests. It does not reproduce locally but the execution logs show that it failed when a shard is relocating during the set up execution. This commit change the set up so that it now waits for all shards to be active before executing the tests. closes #26732, #27146 | 17 January 2018, 14:32:26 UTC |
| a10a918 | Nik Everett | 16 January 2018, 20:08:54 UTC | Handle 5.6.6 release Bump version constant Generate BWC zips | 16 January 2018, 20:08:54 UTC |
| b8d33d5 | Christoph Büscher | 16 January 2018, 16:38:03 UTC | Revert "[Docs] Fix Java Api index administration usage (#28133)" This reverts commit 7aa1a8d04a6961ee9a4563ede8b21efc627d56c0. | 16 January 2018, 16:38:41 UTC |
| 572060d | lcawley | 16 January 2018, 16:36:30 UTC | [DOCS] Updated version to 5.6.6 | 16 January 2018, 16:36:30 UTC |
| 7aa1a8d | Christoph Büscher | 16 January 2018, 11:05:03 UTC | [Docs] Fix Java Api index administration usage (#28133) The Java API documentation for index administration currenty is wrong because the PutMappingRequestBuilder#setSource(Object... source) and CreateIndexRequestBuilder#addMapping(String type, Object... source) methods delegate to methods that check that the input arguments are valid key/value pairs: https://www.elastic.co/guide/en/elasticsearch/client/java-api/current/java-admin-indices.html This changes the docs so the java api code examples are included from documentation integration tests so we detect compile and runtime issues earlier. Closes #28131 | 16 January 2018, 14:52:34 UTC |
| 597b9c2 | Jason Tedor | 16 January 2018, 14:42:37 UTC | Add note on bootstrap checks applying to link-local This commit adds a note to the 5.6 migration guide that the bootstrap checks now apply to link-local addresses. | 16 January 2018, 14:42:37 UTC |
| d6051c3 | Jason Tedor | 16 January 2018, 11:36:37 UTC | Add 5.6.6 release notes | 16 January 2018, 11:36:37 UTC |
| 5f35ec9 | Yannick Welsch | 16 January 2018, 10:08:48 UTC | Never return null from Strings.tokenizeToStringArray (#28224) This method has a different contract than all the other methods in this class, returning null instead of an empty array when receiving a null input. While switching over some methods from delimitedListToStringArray to this method tokenizeToStringArray, this resulted in unexpected nulls in some places of our code. | 16 January 2018, 11:08:43 UTC |
| 5a78dc4 | Yannick Welsch | 16 January 2018, 10:10:38 UTC | Fallback to TransportMasterNodeAction for cluster health retries (#28195) ClusterHealthAction does not use the regular retry logic, possibly causing StackOverflowErrors. | 16 January 2018, 10:17:02 UTC |
| 827fee2 | fbsolo | 16 January 2018, 08:35:35 UTC | [Docs] Changes to ingest.asciidoc (#28212) | 16 January 2018, 08:38:25 UTC |
| 53b169a | Adrien Grand | 16 January 2018, 08:31:37 UTC | Fix ParentFieldMapperTests failure. | 16 January 2018, 08:31:37 UTC |
| 8476bb8 | Adrien Grand | 15 January 2018, 17:34:10 UTC | Allow update of `eager_global_ordinals` on `_parent`. (#28014) A bug introduced in #24407 currently prevents `eager_global_ordinals` from being updated. This new approach should fix the issue while still allowing mapping updates to not specify the `_parent` field if it doesn't need updating, which was the goal of #24407. | 15 January 2018, 20:11:58 UTC |
| ed19090 | Tanguy Leroux | 08 January 2018, 14:03:40 UTC | Avoid concurrent snapshot finalizations when deleting an INIT snapshot (#28078) This commit removes the finalization of a snapshot by the snapshot deletion request. This way, the deletion marks the snapshot as ABORTED in cluster state and waits for the snapshot completion. It is the responsability of the snapshot execution to detect the abortion and terminates itself correctly. This avoids concurrent snapshot finalizations and also ordinates the operations: the deletion aborts the snapshot and waits for the snapshot completion, the creation detects the abortion and stops by itself and finalizes the snapshot, then the deletion resumes and continues the deletion process. | 15 January 2018, 15:27:14 UTC |
| 84503a1 | Tanguy Leroux | 22 December 2017, 14:21:21 UTC | Do not start snapshots that are deleted during initialization (#27931) When a new snapshot is created it is added to the cluster state as a snapshot-in-progress in INIT state, and the initialization is kicked off in a new runnable task by SnapshotService.beginSnapshot(). The initialization writes multiple files before updating the cluster state to change the snapshot-in-progress to STARTED state. This leaves a short window in which the snapshot could be deleted (let's say, because the snapshot is stuck in INIT or because it takes too much time to upload all the initialization files for all snapshotted indices). If the INIT snapshot is deleted, the snapshot-in-progress becomes ABORTED but once the initialization in SnapshotService.beginSnapshot() finished it is change back to STARTED state again. This commit avoids an ABORTED snapshot to be started if it has been deleted during initialization. It also adds a test that would have failed with the previous behavior, and changes few method names here and there. | 15 January 2018, 15:26:49 UTC |
| 804c918 | hanbj | 15 January 2018, 14:09:27 UTC | [Docs] Fix an error in painless-types.asciidoc (#28221) | 15 January 2018, 14:19:14 UTC |
| eb62de0 | akadko | 12 January 2018, 15:36:48 UTC | [DOCS] Removed differencies between text and code (#27993) | 12 January 2018, 15:53:45 UTC |
| f453e46 | Boudewijn | 10 January 2018, 17:00:12 UTC | Update getting-started.asciidoc (#28145) Replaced single quotation marks with double quotation marks surrounding localhost address | 12 January 2018, 15:13:56 UTC |
| a1f530a | Andrew Banchich | 10 January 2018, 16:59:01 UTC | text fixes (#28136) | 12 January 2018, 15:11:59 UTC |
| 4b0669a | Andrew Banchich | 12 January 2018, 10:47:39 UTC | [Docs] Spelling fix in painless-getting-started.asciidoc (#28187) | 12 January 2018, 10:51:31 UTC |
| dc56f13 | Yannick Welsch | 11 January 2018, 15:42:12 UTC | [TEST] Do not call RandomizedTest.scaledRandomIntBetween from multiple threads KeyedLockTests calls RandomizedTest.scaledRandomIntBetween from multiple threads which uses RandomizedTest.isNightly() whereas that method is not concurrency-safe (see implementation of GroupEvaluator.isGroupEnabled) | 11 January 2018, 15:45:01 UTC |
| f2a51de | Tatsuya Oiwa | 11 January 2018, 14:04:58 UTC | Add missing double quotes to Index API response example (#28164) | 11 January 2018, 14:04:58 UTC |
| 12d27df | Colin Goodheart-Smithe | 11 January 2018, 11:12:55 UTC | [DOCS] typo | 11 January 2018, 11:12:55 UTC |
| 4badb66 | Colin Goodheart-Smithe | 11 January 2018, 11:09:48 UTC | [DOCS] Add another alternative to geo_distance_range deprecation | 11 January 2018, 11:09:48 UTC |
| 6fa581c | Andrew Banchich | 11 January 2018, 09:57:46 UTC | [Docs] Improvements in script-fields.asciidoc (#28174) | 11 January 2018, 10:00:28 UTC |
| 771fdc7 | Christoph Büscher | 10 January 2018, 12:00:32 UTC | [Test] Prevent errors on occasionally invalid range query Tests failed on rare occasions where from/to on integer range fields were just one step apart and both includeLower and includeUpper was set to false. This could lead to invalid ranges being rejected. | 10 January 2018, 19:10:44 UTC |
| 05a6b91 | Tyler Smalley | 10 January 2018, 18:23:06 UTC | [Docs] Remove Kerberos/SPNEGO Shield plugin (#28019) Plugin has not been updated in over two years and requires Shield and ES 2.3.1 | 10 January 2018, 18:31:32 UTC |
| 7d99d36 | Ryan Ernst | 09 January 2018, 23:01:37 UTC | Docs: Clarify password protection support with keystore (#28157) closes #27932 | 09 January 2018, 23:05:13 UTC |
| 5c7d373 | Jason Tedor | 09 January 2018, 22:20:55 UTC | Fix task ordering in rolling upgrade tests The configuration of the upgraded cluster task was missing a dependency on the stopping of the second old node in the cluster. In some cases (e.g., --parallel) Gradle would then try to run the configuration of a node in the upgraded cluster before it had even configured the old nodes in the cluster. Relates #28036 | 09 January 2018, 22:22:27 UTC |
| 8b2659d | Jason Tedor | 09 January 2018, 17:51:50 UTC | Set watermarks in single-node test cases We set the watermarks to low values in other test cases to prevent test failures on nodes with low disk space (if the disk space is too low, the test will fail anyway but we should not prematurely fail). This commit sets the watermarks in the single-node test cases to avoid test failures in such situations. Relates #28134 | 09 January 2018, 17:53:54 UTC |
| 80e78e9 | Jason Tedor | 09 January 2018, 05:40:59 UTC | Declare empty package dirs as output dirs Otherwise newer versions of Gradle will see the outputs as stale and remove the directory between having created the directory and copying files into the directory (leading to the directory being created again, this time missing some sub-directories). | 09 January 2018, 05:40:59 UTC |
| 1c2fc09 | Maxime Gréau | 08 January 2018, 18:36:33 UTC | Fix Licenses values for CDDL and Custom URL (#27999) * Fix license SPDX identifiers (CDDL) * Fix license type for Custom URL: * If the license is identified but not listed as an SPDX identifier, the character `;` is used after the identifier to set the license URL. | 08 January 2018, 18:38:49 UTC |
| 02ed139 | Andrew Banchich | 08 January 2018, 15:55:48 UTC | [Docs] Fix Date Math example descriptions (#28125) | 08 January 2018, 15:59:11 UTC |
| 52fd64b | Tim Vernum | 08 January 2018, 01:11:41 UTC | Use the underlying connection version for CCS connections (#28093) Previously this would default to the version of the remote Node. However, if the remote cluster was mixed-version (e.g. it was part way through a rolling upgrade), then the TransportService may have negotiated a connection version that is not identical to connected Node's version. This mismatch would cause the Stream and the (Remote)Connection to report different version numbers, which could cause data to be sent over the wire using an incorrect serialization version. | 08 January 2018, 09:34:20 UTC |
| 32674ef | Jason Tedor | 07 January 2018, 03:44:43 UTC | Clarify reproduce info on Windows This commit correct the test failure reproduction line on Windows. Relates #28104 | 07 January 2018, 03:51:51 UTC |
| d4f18c8 | Jason Tedor | 06 January 2018, 18:03:44 UTC | Remove out-of-date projectile file This commit removes an out-of-date projectile file from the top-level directory. Relates #28115 | 06 January 2018, 18:05:28 UTC |
| 0ba2137 | Jason Tedor | 06 January 2018, 13:47:23 UTC | Fix reproduction info to point to Gradle wrapper With the Gradle wrapper in place, we should point the reproduction info to specify using the Gradle wrapper too. Relates #28104 | 06 January 2018, 13:49:23 UTC |
| 1734e8f | Jason Tedor | 05 January 2018, 22:25:10 UTC | Update platforms tests to use Gradle wrapper Gradle will no longer be needed in the test VMs as the Gradle wrapper can be used to run the platform tests. This commit updates the platform tests to use the Gradle wrapper, and removes installing Gradle in the VM which will speed up VM provisioning. Relates #28105 | 05 January 2018, 22:26:20 UTC |
| 15fd6fc | Jason Tedor | 05 January 2018, 22:19:34 UTC | Update testing docs to reflect Gradle wrapper This commit updates the testing docs to reflect the usage of the Gradle wrapper. Relates #28107 | 05 January 2018, 22:24:31 UTC |
| 24ac8a9 | hyeonyoung na | 05 January 2018, 17:16:15 UTC | Update contributing docs to use the Gradle wrapper This commit updates the contributing docs to reference the introduction of the Gradle wrapper. Relates #28103 | 05 January 2018, 17:37:54 UTC |
| b169dfc | Francis Gulotta | 05 January 2018, 08:38:54 UTC | Fix link to parent join (#28085) | 05 January 2018, 08:40:15 UTC |
| 297c91a | Jason Tedor | 04 January 2018, 21:36:13 UTC | Introduce Gradle wrapper We have agreed to introduce the Gradle wrapper to simplify workflows for developers, and managing infrastructure (e.g., CI, release builds, etc.) as well as consideration for the fact that other projects in our stack use Gradle and do not necessarily want to be tied to our Gradle version. Relates #28065 | 04 January 2018, 21:41:25 UTC |
| 78daa52 | Jason Tedor | 04 January 2018, 19:58:34 UTC | Ignore GIT_COMMIT when calculating commit hash When finding the commit hash for the build to place in the JAR manifest (which is used to identity the build), the scm-info plugin assumes that GIT_COMMIT is the commit for this build. That assumption is wrong, this build could be a sub-build of another build that GIT_COMMIT belongs to. If GIT_COMMIT is set, we ignore the commit hash calculated by scm-info and calculate the hash ourselves. Relates #28082 | 04 January 2018, 19:59:53 UTC |
| 91b6b97 | Jason Tedor | 03 January 2018, 02:19:24 UTC | Enable Wildfly tests on JDK 9 and JDK 10 Previously we disabled these tests on JDK 9 and JDK 10 because Wildfly 10 did not support JDK 9 and JDK 10. With the release of Wildfly 11 supporting JDK 9 and JDK 10 and now that we depend on Wildfly 11 in these tests, we can enable these tests on JDK 9 and JDK 10. Relates #28042 | 03 January 2018, 02:21:18 UTC |
| 14060cb | Jason Tedor | 02 January 2018, 12:04:09 UTC | Only bind loopback addresses when binding to local * Only bind loopback addresses when binding to local Today when binding to local (the default) we bind to any address that is a loopback address, or any address on an interface that declares itself as a loopback interface. Yet, not all addresses on loopback interfaces are loopback addresses. This arises on macOS where there is a link-local address assigned to the loopback interface (fe80::1%lo0) and in Docker services where virtual IPs of the service are assigned to the loopback interface (docker/libnetwork#1877). These situations cause problems: - because we do not handle the scope ID of a link-local address, we end up bound to an address for which publishing of that address does not allow that address to be reached (since we drop the scope) - the virtual IPs in the Docker situation are not loopback addresses, they are not link-local addresses, so we end up bound to interfaces that cause the bootstrap checks to be enforced even though the instance is only bound to local We address this by only binding to actual loopback addresses, and skip binding to any address on a loopback interface that is not a loopback address. This lets us simplify some code where in the bootstrap checks we were skipping link-local addresses, and in writing the ports file where we had to skip link-local addresses because again the formatting of them does not allow them to be connected to by another node (to be clear, they could be connected to via the scope-qualified address, but that information is not written out). Relates #28029 | 02 January 2018, 12:13:31 UTC |
| 9cd92cb | Jason Tedor | 01 January 2018, 23:03:15 UTC | Fix assertion in Wildfly build This commit fixes a flubbed assertion in the Wildfly build file; the intention was to assert that we have only set the value of the management port once except the assertion that the management port was equal to zero when finding a matching log line was left off. | 01 January 2018, 23:06:06 UTC |
| ace2fe8 | Jason Tedor | 01 January 2018, 21:29:53 UTC | Fix typo in comment in Wildfly build This commit fixes a typographical error in the Wildfly tests build file. Oops. | 01 January 2018, 21:32:34 UTC |
| 85733ce | Jason Tedor | 01 January 2018, 21:27:30 UTC | Use ephemeral ports in Wildfly tests The Wildfly tests previously needed hardcoded ports which would sometimes already be in use leading to Wildfly test failures because the server could not bind during startup. We had to wait until some upstream changes (wildfly/wildfly#9943) and (wildfly/wildfly-core#2390) were released before we could use ephemeral ports in these tests. These changes are released now so this commit changes the Wildfly tests to use ephemeral ports when starting Wildfly. Relates #28040 | 01 January 2018, 21:28:35 UTC |
| cfc901f | Maxime Gréau | 26 December 2017, 09:51:47 UTC | Build: Add 3rd party dependencies report generation (#27727) * Adds task dependenciesInfo to BuildPlugin to generate a CSV file with dependencies information (name,version,url,license) * Adds `ConcatFilesTask.groovy` to concatenates multiple files into one * Adds task `:distribution:generateDependenciesReport` to concatenate `dependencies.csv` files into a single file (`es-dependencies.csv` by default) # Examples: $ gradle dependenciesInfo :distribution:generateDependenciesReport ## Use `csv` system property to customize the output file path $ gradle dependenciesInfo :distribution:generateDependenciesReport -Dcsv=/tmp/elasticsearch-dependencies.csv ## When branch is not master, use `build.branch` system property to generate correct licenses URLs $ gradle dependenciesInfo :distribution:generateDependenciesReport -Dbuild.branch=6.x -Dcsv=/tmp/elasticsearch-dependencies.csv | 26 December 2017, 10:08:56 UTC |
| 7ec88b3 | Nhat Nguyen | 20 December 2017, 17:43:05 UTC | TEST: reduce blob size #testExecuteMultipartUpload If a large blob size and small buffer size are picked, this test causes out of memory. https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+intake/1061/ https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+5.6+multijob-unix-compatibility/os=sles/466/console | 24 December 2017, 18:22:15 UTC |
| 12db6ad | Jason Tedor | 23 December 2017, 13:37:57 UTC | Disable reindex from old tests on JDK 10 We disable these tests because the JVM flags we use will not start with JDK 10. Since we do not support running these old versions on newer JDKs anyway, this commit disables testing of these when running on JDK 10. | 23 December 2017, 13:40:59 UTC |
| e1b4bb5 | Jason Tedor | 22 December 2017, 12:34:00 UTC | Also skip Javadoc task for client JARs on JDK 10 We disabled the Javadoc task on JDK 10 due to an apparent bug in Javadoc generation on JDK 10. However, the client JAR task sets up its own Javadoc task for client JARs (because it merely copies the non-client Javadoc JAR). This commit diables that task too, since the Javadocs for the non-client JAR will not exist. Relates #27962 | 22 December 2017, 12:35:30 UTC |
| 8a04236 | Tanguy Leroux | 12 December 2017, 08:51:18 UTC | Fail restore when the shard allocations max retries count is reached (#27493) This commit changes the RestoreService so that it now fails the snapshot restore if one of the shards to restore has failed to be allocated. It also adds a new RestoreInProgressAllocationDecider that forbids such shards to be allocated again. This way, when a restore is impossible or failed too many times, the user is forced to take a manual action (like deleting the index which failed shards) in order to try to restore it again. This behaviour has been implemented because when the allocation of a shard has been retried too many times, the MaxRetryDecider is engaged to prevent any future allocation of the failed shard. If it happens while restoring a snapshot, the restore hanged and was never completed because it stayed around waiting for the shards to be assigned (and that won't happen). It also blocked future attempts to restore the snapshot again. With this commit, the restore does not hang and is marked as failed, leaving failed shards around for investigation. This is the second part of the #26865 issue. Closes #26865 | 22 December 2017, 11:26:12 UTC |
| 0b2b2bc | Alexander Reelsen | 22 December 2017, 11:16:17 UTC | Tests: Fix packaging tests after attachment plugin upgrade (#27959) The tests explicitely check for the version of some java dependencies and thus needed to be fixed. Relates #27824 Closes #27916 | 22 December 2017, 11:17:58 UTC |
| 1f00f37 | Tanguy Leroux | 22 December 2017, 08:58:02 UTC | [Test] Do not rely on MockZenPing for Azure tests (#27945) This commit changes some Azure tests so that they do not rely on MockZenPing and TestZenDiscovery anymore, but instead use a mocked AzureComputeService that exposes internal test cluster nodes as if they were real Azure nodes. Related to #27859 Closes #27917, #11533 | 22 December 2017, 10:17:34 UTC |
| c3486eb | Jason Tedor | 21 December 2017, 22:26:20 UTC | Disable Javadocs on JDK 10 There appears to be a bug in JDK 10 for generating Javadocs with some nested anonymous classes. This commit disables these on JDK 10 until the upstream issue is resolved. Relates #27952 | 21 December 2017, 22:27:48 UTC |
