| b727a60 | Adrien Grand | 06 June 2018, 14:44:51 UTC | Add an escape hatch to increase the maximum amount of memory that IndexWriter gets. (#31133) Relates #31105 | 06 June 2018, 14:44:51 UTC |
| c29e9e8 | Christoph Büscher | 06 June 2018, 07:53:14 UTC | [Docs] Delete superfluous callouts (#31111) Those callout create rendering problems on the subsequent page. Closes #30532 | 06 June 2018, 07:56:27 UTC |
| 97124ed | Christoph Büscher | 31 May 2018, 13:05:03 UTC | [Docs] Fix typo in Min Aggregation reference (#30899) | 31 May 2018, 13:08:47 UTC |
| d15aa21 | Yannick Welsch | 30 May 2018, 08:15:12 UTC | Fsync state file before exposing it (#30929) With multiple data paths, we write the state files for index metadata to all data paths. We only properly fsync on the first location, though. For other locations, we possibly expose the file before its contents is properly fsynced. This can lead to situations where, after a crash, and where the first data path is not available anymore, ES will see a partially-written state file, preventing the node to start up. | 30 May 2018, 09:54:35 UTC |
| a22121b | Tanguy Leroux | 29 May 2018, 17:11:20 UTC | Remove log traces in AzureStorageServiceImpl and fix test This commit removes some log traces in AzureStorageServiceImpl and also fixes the AzureStorageServiceTests so that is uses the real implementation to create Azure clients. | 29 May 2018, 17:11:20 UTC |
| e521a9a | Christoph Büscher | 28 May 2018, 21:07:43 UTC | Mute UnicastZenPingTests#testSimplePings with @AwaitsFix. This failure is being tracked in #28685. | 28 May 2018, 21:07:43 UTC |
| 02b67a5 | Yannick Welsch | 23 May 2018, 11:25:41 UTC | Use correct cluster state version for node fault detection (#30810) Since its introduction in ES 1.4, node fault detection has been using the wrong cluster state version to send as part of the ping request, by using always the constant -1 (ClusterState.UNKNOWN_VERSION). This can, in an unfortunate series of events, lead to a situation where a previous stale master can regain its authority and revert the cluster to an older state. This commit makes NodesFaultDetection use the correct current cluster state for sending ping requests, avoiding the situation where a stale master possibly forces a newer master to step down and rejoin the stale one. | 23 May 2018, 16:34:58 UTC |
| 9fac131 | Tal Levy | 21 May 2018, 19:13:47 UTC | fix GeoDistanceTests.testReadFromSerializationBWC of the actual BWC change. this test was not appropriately updated. This test failed because it was trying to read from a 5.3.1 stream incorrectly. Closes #30764. | 21 May 2018, 19:13:47 UTC |
| a39d387 | Andy Bristol | 21 May 2018, 19:07:23 UTC | [test] mute GeoDistanceTests.testReadFromSerializationBWC Tracked by #30764 | 21 May 2018, 19:07:23 UTC |
| 0fac258 | Tal Levy | 18 May 2018, 15:00:25 UTC | Fix BWC serialization for GeoDistance (#29501) The BWC portion of the writeTo code was incorrectly version-bounding against 5.3.3 when the real bw-incompatible change was made in 5.3.0. | 18 May 2018, 15:00:25 UTC |
| 9667780 | David Turner | 16 May 2018, 17:44:57 UTC | Suppress hdfsFixture if there are spaces in the path (#30533) HDFS sets its thread-name format based partly on a URL-encoded version of the path, but the URL-encoding of spaces as `%20` is interpreted as a field in the formatted string of type `2`, which is nonsensical. This change simply skips these tests in this case. Backport of #30302 | 16 May 2018, 17:44:57 UTC |
| 13fe1f3 | lcawl | 15 May 2018, 17:53:27 UTC | [DOCS] Restores 5.6 release notes and highlights | 15 May 2018, 17:53:27 UTC |
| ada8147 | javanna | 15 May 2018, 10:41:46 UTC | [DOCS] Remove references to changelog and to highlights highlights reference the changelog and it currently breaks the docs. | 15 May 2018, 10:41:46 UTC |
| 4203a84 | lcawl | 14 May 2018, 23:29:27 UTC | [DOCS] Adds 5.6.10 release highlights page | 14 May 2018, 23:29:27 UTC |
| fd7dfc5 | Lisa Cawley | 14 May 2018, 22:49:00 UTC | [DOCS] Adds release highlight pages (#30590) | 14 May 2018, 23:17:04 UTC |
| 6f0267c | Jason Tedor | 09 May 2018, 15:52:38 UTC | Avoid deadlocks in cache (#30461) This commit avoids deadlocks in the cache by removing dangerous places where we try to take the LRU lock while completing a future. Instead, we block for the future to complete, and then execute the handling code under the LRU lock (for example, eviction). | 09 May 2018, 16:03:37 UTC |
| f835fad | Jason Tedor | 07 May 2018, 18:12:04 UTC | Fix line length violation in cache tests This commit fixes a line-length violation in the cache tests that was hidden by the IDE folding the generics. | 07 May 2018, 18:14:05 UTC |
| 37e5fcd | Jason Tedor | 07 May 2018, 17:00:50 UTC | Add failing test for core cache deadlock The core cache implementation has a deadlock bug. This commit adds a failing test case. | 07 May 2018, 17:03:22 UTC |
| fa39bbf | Boaz Leskes | 07 May 2018, 12:34:57 UTC | testDynamicMappingDisabled - don't use <5 randomized auto create index patterns The can be mistakenly interpreted as booleans :D i.e., "no", "yes", "false" | 07 May 2018, 12:35:40 UTC |
| e864427 | Boaz Leskes | 04 May 2018, 14:29:34 UTC | Bulk operation fail to replicate operations when a mapping update times out (#30379) Starting with the refactoring in https://github.com/elastic/elasticsearch/pull/22778 (released in 5.3) we may fail to properly replicate operation when a mapping update on master fails. If a bulk operations needs a mapping update half way, it will send a request to the master before continuing to index the operations. If that request times out or isn't acked (i.e., even one node in the cluster didn't process it within 30s), we end up throwing the exception and aborting the entire bulk. This is a problem because all operations that were processed so far are not replicated any more to the replicas. Although these operations were never "acked" to the user (we threw an error) it cause the local checkpoint on the replicas to lag (on 6.x) and the primary and replica to diverge. This PR changes the logic to treat *any* mapping update failure as a document level failure, meaning only the relevant indexing operation will fail. Back port of #30244 * remove | 04 May 2018, 14:29:34 UTC |
| fff2e09 | David Turner | 01 May 2018, 13:41:42 UTC | Suppress reindex-from-old tests if there are spaces in the path | 01 May 2018, 13:42:43 UTC |
| fabbdc7 | Sue Gallagher | 27 April 2018, 16:29:27 UTC | [DOCS] Added 'on a single shard' to description of max_thread_count. Closes 28518 (#29686) | 27 April 2018, 17:46:22 UTC |
| a071fc4 | Saren Currie | 26 April 2018, 08:45:48 UTC | Clarify documentation of scroll_id (#29424) * Clarify documentation of scroll_id The Scroll API may return the same scroll ID for multiple requests due to server side state. This is not clear from the current documentation. * Further clarify scroll ID return behaviour | 26 April 2018, 08:48:22 UTC |
| 1c1a370 | Jason Tedor | 25 April 2018, 19:49:54 UTC | Correct transport compression algorithm in docs (#29645) We use DEFLATE when compressing byte streams on the transport layer yet the docs say we use LZF. This commit correct this. | 25 April 2018, 19:52:16 UTC |
| dadf7aa | Jason Tedor | 18 April 2018, 20:02:21 UTC | Protect against NPE in RestNodesAction (#29059) * Protect against NPE in RestNodesAction | 18 April 2018, 20:02:21 UTC |
| 28e2924 | Clinton Gormley | 18 April 2018, 10:47:17 UTC | Added release notes for 5.6.9 | 18 April 2018, 10:47:17 UTC |
| 9c0223b | Julie Tibshirani | 17 April 2018, 22:32:00 UTC | Fix the version ID for v5.6.10. | 17 April 2018, 22:32:00 UTC |
| dfd3609 | Hendrik Muhs | 17 April 2018, 18:33:00 UTC | Generate BWC zips for 5.6.9 | 17 April 2018, 18:33:00 UTC |
| 98451d8 | Dimitris Athanasiou | 17 April 2018, 17:02:24 UTC | Bumping ES Version to 5.6.10 | 17 April 2018, 17:31:03 UTC |
| 7071cb7 | lcawley | 17 April 2018, 15:36:25 UTC | [DOCS] Updated version to 5.6.9 | 17 April 2018, 15:36:25 UTC |
| 877a590 | Juan Domenech Fernandez | 11 April 2018, 13:41:10 UTC | Missing 's' on `discovery.zen.minimum_master_nodes` in migration docs (#29473) | 11 April 2018, 13:41:10 UTC |
| ff070b1 | yangyang.liu | 09 April 2018, 08:39:28 UTC | [Docs] Update painless-lang-spec.asciidoc (#29425) Remove redundant word. | 09 April 2018, 08:41:48 UTC |
| 4b23b63 | Martijn van Groningen | 10 January 2018, 17:03:14 UTC | docs: Replaces indexed script java api docs with stored script api docs Closes #28144 | 06 April 2018, 12:35:52 UTC |
| d38c583 | Stéphane Campinas | 04 April 2018, 10:11:29 UTC | [Docs] Correct javadoc of GetIndexRequest (#29364) | 04 April 2018, 10:15:19 UTC |
| 84eb8c9 | Ragnar Nevries | 03 April 2018, 12:57:42 UTC | [Docs] Update getting-started.asciidoc (#29294) Description after first use of search API with body does not refer to verb POST. | 03 April 2018, 13:00:50 UTC |
| e1f7ffb | Yannick Welsch | 03 April 2018, 11:58:57 UTC | Fix compilation | 03 April 2018, 11:58:57 UTC |
| 2242d69 | Yannick Welsch | 03 April 2018, 11:53:15 UTC | [DOCS] Refer back to index API for full-document updates in _update API section (#28677) This clarifies how full-document updates are performed in ES. | 03 April 2018, 11:54:59 UTC |
| 4fddb70 | Yannick Welsch | 03 April 2018, 09:51:06 UTC | Don't break allocation if resize source index is missing (#29311) DiskThresholdDecider currently assumes that the source index of a resize operation (e.g. shrink) is available, and throws an IndexNotFoundException otherwise, thereby breaking any kind of shard allocation. This can be quite harmful if the source index is deleted during a shrink, or if the source index is unavailable during state recovery. While this behavior has been partly fixed in 6.1 and above (due to #26931), it relies on the order in which AllocationDeciders are executed (i.e. that ResizeAllocationDecider returns NO, ensuring that DiskThresholdDecider does not run, something that for example does not hold for the allocation explain API). This change adds a more complete fix, and also solves the situation for 5.6. | 03 April 2018, 10:08:45 UTC |
| 20552a2 | David Leatherman | 02 April 2018, 18:24:13 UTC | Java versions for ci 5.6 (#29333) * Add test matrix axis files for periodic java testing * Add properties file defining java versions to use | 02 April 2018, 18:24:13 UTC |
| fba8741 | Jason Tedor | 29 March 2018, 22:33:35 UTC | Increase timeout on Netty client latch for tests We use a latch when sending requests during tests so that we do not hang forever waiting for replies on those requests. This commit increases the timeout on that latch to 30 seconds because sometimes 10 seconds is just not enough. | 29 March 2018, 22:35:26 UTC |
| 4dc0257 | Jason Tedor | 28 March 2018, 12:22:06 UTC | Remove leftover tests.rest.spec property from docs (#29279) We previously had a property to specify the location of the REST test spec files but this was removed in a previous refactoring yet left behind in the docs. This commit removes the last remaining vestige of this parameter. | 28 March 2018, 12:34:36 UTC |
| c9191bd | Jason Tedor | 23 March 2018, 01:23:52 UTC | Add note to low-level client docs for DNS caching (#29213) This commit adds a note to the low-level REST client docs regarding the possibility of being impacted by the JVM DNS cache policy under a default security manager policy. | 23 March 2018, 01:25:13 UTC |
| da6e49a | lcawley | 22 March 2018, 17:23:28 UTC | [DOCS] Updated attributes file | 22 March 2018, 17:23:28 UTC |
| 73b8856 | Tim Brooks | 21 March 2018, 18:02:00 UTC | Call addBytesSent with correct number of bytes (#29194) This is related to #27258. Currently we call the transport service adaptor with the number of readable bytes once a message has been sent. However, the number of readable bytes should be zero as the bytebuf has been consumed. This commit fixes that issue by recording the number of bytes. | 21 March 2018, 18:02:00 UTC |
| 13a6f02 | Nhat Nguyen | 21 March 2018, 14:53:18 UTC | Revert "Do not renew sync-id if all shards are sealed" We discussed and agreed to include #29103 in 6.3.0+ but not in 5.6.9. We will re-evaluate the urgency and importance of the issue then decide which versions that the change should be included. This reverts commit 25b4d9e130b9e5537d39b5f6379576ecd96ced37. | 21 March 2018, 14:53:18 UTC |
| 2d8849e | Nhat Nguyen | 20 March 2018, 17:47:09 UTC | Fix BWC issue for PreSyncedFlushResponse I misunderstood how the bwc versions works. If we backport to 5.x, we need to backport to all supported 6.*. This commit corrects the BWC versions for PreSyncedFlushResponse. Relates #29103 | 20 March 2018, 17:51:36 UTC |
| e588079 | Nhat Nguyen | 20 March 2018, 17:42:04 UTC | Revert "Revert "Do not renew sync-id if all shards are sealed (#29103)"" Let re-enable this commit, then fix the BWC issue. | 20 March 2018, 17:42:04 UTC |
| c9c824d | tnsatish | 20 March 2018, 16:46:11 UTC | Fix typo in percolate-query.asciidoc (#29155) | 20 March 2018, 16:51:03 UTC |
| ec4db0f | David Turner | 20 March 2018, 13:02:48 UTC | Revert "Do not renew sync-id if all shards are sealed (#29103)" This reverts commit 25b4d9e130b9e5537d39b5f6379576ecd96ced37. | 20 March 2018, 13:02:48 UTC |
| 93370aa | David Turner | 19 March 2018, 07:04:47 UTC | Update allocation awareness docs (#29116) Update allocation awareness docs Today, the docs imply that if multiple attributes are specified the the whole combination of values is considered as a single entity when performing allocation. In fact, each attribute is considered separately. This change fixes this discrepancy. It also replaces the use of the term "awareness zone" with "zone or domain", and reformats some paragraphs to the right width. Fixes #29105 | 19 March 2018, 07:08:05 UTC |
| 25b4d9e | Nhat Nguyen | 16 March 2018, 15:16:30 UTC | Do not renew sync-id if all shards are sealed (#29103) Today the synced-flush always issues a new sync-id even though all shards haven't been changed since the last seal. This causes active shards to have different a sync-id from offline shards even though all were sealed and no writes since then. This commit adjusts not to renew sync-id if all active shards are sealed with the same sync-id. Closes #27838 | 17 March 2018, 18:54:14 UTC |
| c6b6fec | Jiri Tyr | 16 March 2018, 13:13:17 UTC | [Docs] Fix link to Grok patterns (#29088) | 16 March 2018, 13:26:59 UTC |
| 9635b2c | Martijn van Groningen | 15 March 2018, 19:36:00 UTC | Added minimal docs for reindex api in java-api docs Additionally: * Included the existing update by query java api docs in java-api docs. (for some reason it was never included, it needed some tweaking and then it was good to go) * moved delete-by-query / update-by-query code samples to java file so that we can verify that these samples at least compile. Closes #24203 | 16 March 2018, 06:47:18 UTC |
| 3635909 | Jason Tedor | 14 March 2018, 17:02:55 UTC | Fix typo in terminate after API docs This commit fixes a minor typo in the terminate after Java API docs. Relates #29065 | 14 March 2018, 17:06:11 UTC |
| c01e3c2 | Martijn van Groningen | 14 March 2018, 16:16:48 UTC | Removed outdated docs about shading Elasticsearch | 14 March 2018, 16:54:56 UTC |
| c4592c2 | Martijn van Groningen | 14 March 2018, 13:53:42 UTC | Revert "added docs for `wrapper` query." This reverts commit 76a9a375459b64f08ea9e6965837d00e7f9b3198. | 14 March 2018, 13:53:42 UTC |
| 76a9a37 | Martijn van Groningen | 14 March 2018, 10:51:22 UTC | added docs for `wrapper` query. Closes #11591 | 14 March 2018, 10:58:29 UTC |
| bdfb889 | Jason Tedor | 13 March 2018, 22:27:14 UTC | Add search slowlog level to docs (#29040) This commit adds an indication how to set the search slowlog level to the docs. | 13 March 2018, 22:28:15 UTC |
| fd763c3 | Adrien Grand | 13 March 2018, 17:40:17 UTC | Clarify that dynamic date formats are only checked for values that contain `-`, `/` or `:`. (#28375) This only applies to 5.x and earlier versions, it was addressed in 6.0. Closes #26499 | 13 March 2018, 17:40:17 UTC |
| 6d5f7a2 | Jason Tedor | 12 March 2018, 12:42:02 UTC | Avoid class cast exception from index writer (#28989) When an index writer encounters a tragic exception, it could be a Throwable and not an Exception. Yet we blindly cast the tragic exception to an Exception which can encounter a ClassCastException. This commit addresses this by checking if the tragic exception is an Exception and otherwise wrapping the Throwable in a RuntimeException if it is not. We choose to wrap the Throwable instead of passing it around because passing it around leads to changing a lot of places where we handle Exception to handle Throwable instead. In general, we have tried to avoid handling Throwable and instead let those bubble up to the uncaught exception handler. | 12 March 2018, 12:44:58 UTC |
| 72986db | Jason Tedor | 10 March 2018, 12:41:51 UTC | Maybe die before failing engine (#28973) Today we check for a few cases where we should maybe die before failing the engine (e.g., when a merge fails). However, there are still other cases where a fatal error can be hidden from us (for example, a failed index writer commit). This commit modifies the mechanism for failing the engine to always check for a fatal error before failing the engine. | 10 March 2018, 13:09:36 UTC |
| 890ee15 | 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 | 10 March 2018, 13:04:09 UTC |
| 90bde12 | David Turner | 09 March 2018, 09:57:53 UTC | Use String.join() to describe a list of tasks (#28941) This change replaces the use of string concatenation with a call to String.join(). String concatenation might be quadratic, unless the compiler can optimise it away, whereas String.join() is more reliably linear. There can sometimes be a large number of pending ClusterState update tasks and #28920 includes a report that this operation sometimes takes a long time. | 09 March 2018, 09:57:53 UTC |
| 924247d | Holger Bartnick | 08 March 2018, 12:14:50 UTC | [Docs] REST high-level client: Fix code for most basic search request (#28916) We also need to add the query to the request. | 08 March 2018, 12:20:41 UTC |
| 781d830 | Thomas Kappler | 01 March 2018, 23:30:32 UTC | Fix upgrading indices which use a custom similarity plugin (#28795) Use a fake similarity map that always returns a value in MetaDataIndexUpgradeService.checkMappingsCompatibility instead of an empty map. Closes #25350 relates #26985 | 01 March 2018, 23:30:32 UTC |
| ab8ef4e | FUJI Goro | 27 February 2018, 18:29:43 UTC | [Docs] Specify function score logarithm modifiers (#28821) The logarithm with base 10 is called "Common Logarithm". | 27 February 2018, 18:36:20 UTC |
| 7d7ecc0 | Jason Tedor | 27 February 2018, 18:31:44 UTC | Add note regarding quoting values for network.host Values for the network.host setting can often contain a colon which is a character that is considered special by YAML (these arise in IPv6 addresses and some of the special tags like ":ipv4"). As such, these values need to be quoted or a YAML parser will be unhappy with them. This commit adds a note to the docs regarding this. | 27 February 2018, 18:34:44 UTC |
| 481a41e | Jason Tedor | 26 February 2018, 15:47:57 UTC | Move search concurrency and parallelism paragraphs These paragraphs should be on the top-level search page for visibility so this commit moves them, and puts them under a clear heading. | 26 February 2018, 15:51:18 UTC |
| 9d3d070 | lzh3636 | 26 February 2018, 14:55:32 UTC | Fix log message when virtual lock not possible (#28829) When virtual lock is not possible because JNA is unavailable, we log a warning message. Yet, this log message refers to mlockall rather than virtual lock, presumably because of a copy/paste error. This commit fixes this issue. | 26 February 2018, 14:56:41 UTC |
| a5ce97d | Daniel Mitterdorfer | 22 February 2018, 15:36:01 UTC | Reduce max javac memory to 512mb (#28783) With this commit we reduce the maximum amount of memory that the javac compiler can use from 1g to 512mb. While the build would succeed even with 256mb, it influences compile time slightly negatively. We have measured that the runtime overhead stays tolerable by running the following command five times under repeatable conditions (i.e. we execute `./gradlew clean`, then drop the caches and TRIM the disk): ``` ./gradlew compileGroovy compileJava compileJava9Java\ compileTestGroovy compileTestJava compileGroovy ``` The results in seconds (as reported by Gradle) are: * 1gb: avg: 253s, min: 252s, max: 256s * 512mb: avg: 257s, min: 256s, max: 259s | 23 February 2018, 09:30:53 UTC |
| 43169c5 | Luca Cavanna | 15 February 2018, 16:22:45 UTC | REST high-level client: encode path parts (#28663) The REST high-level client supports now encoding of path parts, so that for instance documents with valid ids, but containing characters that need to be encoded as part of urls (`#` etc.), are properly supported. We also make sure that each path part can contain `/` by encoding them properly too. Closes #28625 | 21 February 2018, 15:29:33 UTC |
| b25208a | Lokesh Mohanty | 21 February 2018, 09:40:18 UTC | [Docs] Update links to java9 docs (#28750) Closes #28683 | 21 February 2018, 09:43:03 UTC |
| fd4df46 | Michael Basnight | 20 February 2018, 21:28:27 UTC | Fix compile error caused by version bump | 20 February 2018, 21:28:27 UTC |
| 65fc283 | Michael Basnight | 20 February 2018, 17:37:45 UTC | Handle 5.6.8 release Bump version constant Generate BWC zips | 20 February 2018, 17:37:45 UTC |
| 9edee5c | Deb Adair | 20 February 2018, 17:06:34 UTC | [DOCS] Bumped version for 5.6.8. | 20 February 2018, 17:06:34 UTC |
| 0d2410d | Jason Tedor | 20 February 2018, 15:29:26 UTC | Add 5.6.8 release notes to 5.6 release notes This commit adds the 5.6.8 to the 5.6 release notes page so that it is visible. | 20 February 2018, 15:29:26 UTC |
| 180944a | Jason Tedor | 20 February 2018, 15:24:13 UTC | Add release notes for 5.6.8 This commit adds the release notes for 5.6.8 to the 5.6 branch in preparation for the forthcoming 5.6.8 release. | 20 February 2018, 15:24:50 UTC |
| 92c243a | Tanguy Leroux | 20 February 2018, 13:54:53 UTC | [Tests] Fix RetryHttpInitializerWrapperTests.testIOExceptionRetry This commit gives more time to the IO exception handler to retry the request. | 20 February 2018, 14:13:53 UTC |
| 5aeae11 | Tanguy Leroux | 20 February 2018, 08:50:01 UTC | [Tests] Simplify GceDiscoverTests GceDiscoverTests can be simplified in a similar manner than #27945. It now uses a mocked GceInstancesService that exposes internal test cluster nodes as if they were real GCE nodes. It should also make the test more robust by not using a HTTP server anymore. closes #24313 | 20 February 2018, 10:04:01 UTC |
| 49fe012 | Ryan Ernst | 02 February 2018, 18:57:01 UTC | Build: Fix test task to explicitly depend on testClasses task (#28490) Gradle 4.5 now hides immutable task dependencies. We previously copied the existing dependencies from the builtin test task to the randomizedtesting task. This commit adds testClasses as an extra dependency of the randomizedtesting task, to ensure the classes are built. | 20 February 2018, 05:49:41 UTC |
| 0c7b6b8 | Alejandro Carstens Cattori | 19 February 2018, 09:33:11 UTC | [Docs] Correct typo in README.textile (#28716) | 19 February 2018, 09:35:47 UTC |
| bd79c39 | Clinton Gormley | 17 February 2018, 08:42:46 UTC | Added coming annotation and breaking changes link to release notes script Also fixed the "area" regex to only remove up to the first / so that it doesn't remove too much in :Distributed/Snapshot/Restore Finally, tidied | 17 February 2018, 08:46:01 UTC |
| 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 |
