Revise mmapfs requirements #124091
Closed
Revise mmapfs requirements #124091
Conversation
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
…118454) (#118769) (#119292) Co-authored-by: Luigi Dell'Aquila <[email protected]>
…) (#119314) SmbTestContainer base image upgraded from Ubuntu 16.04 to 24.04 to avoid hanging Python module compilation when installing samba package. Installing SMB had to be moved from container building to starting because SYS_ADMIN capability is required. (cherry picked from commit a0f64d2) # Conflicts: # .buildkite/pipelines/pull-request/packaging-tests-unix.yml Co-authored-by: Mariusz Józala <[email protected]>
Co-authored-by: shainaraskas <[email protected]>
* Fix NPE by getting request once and defaulting to empty list * Fix error in OpenAIUpgrade test which used the wrong field name for certain versions * [CI] Auto commit changes from spotless --------- Co-authored-by: elasticsearchmachine <[email protected]>
This updates the gradle wrapper to 8.12 We addressed deprecation warnings due to the update that includes: - Fix change in TestOutputEvent api - Fix deprecation in groovy syntax - Use latest ospackage plugin containing our fix - Remove project usages at execution time - Fix deprecated project references in repository-old-versions (cherry picked from commit ba61f8c) # Conflicts: # build-tools-internal/src/main/java/org/elasticsearch/gradle/internal/distribution/DockerUbiElasticsearchDistributionType.java # build-tools-internal/src/main/java/org/elasticsearch/gradle/internal/test/Fixture.java # plugins/repository-hdfs/hadoop-client-api/build.gradle # qa/entitlements/build.gradle # server/src/main/java/org/elasticsearch/indices/IndicesFeatures.java # x-pack/plugin/migrate/build.gradle # x-pack/plugin/security/qa/security-basic/build.gradle
We add explicit support for running build with -Druntime.java=24 and -Druntime.java=24) By default it takes the build that was available at implementation time (b29 for 24 and b3 for 25) You can pass the build number also dynamically by running your build e.g. with ``` -Druntime.java=24 -Druntime.java.build=29 ``` which will resolve java ea24 build 29 fixes #118329 (cherry picked from commit f028340)
The STABLE_CONFIGURATION_CACHE feature flag enables the following:
- tasks using a shared build service without declaring the requirement via the Task.usesService method will emit a deprecation warning.
- when the configuration cache is not enabled but the feature flag is present, deprecations for the following configuration cache requirements are also enabled:
- Registering build listeners
- Using task extensions and conventions at execution time
#119469) Co-authored-by: Joe Gallo <[email protected]>
…o 2503e99 (#119414) Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
…19516) (#119527) * fix: do not let `_resolve/cluster` hang if remote is unresponsive Previously, `_resolve/cluster` would wait for a response from a remote as part of the connection strategy. If the remote were to be unresponsive, this API would wait until `netty` would terminate the connection with a handshake exception. The threshold for terminating the connection is `10s`. This means that the API would wait for `10s` before determining that the remote is unresponsive. This strategy is now replaced with a fail fast where a response is sent back to the user immediately rather than waiting for a connection termination. * Update docs/changelog/119516.yaml
…#123153) (#123738) This test was muted, got fixed, and then was muted again but the issue wasn't reopened (by accident it seems). Since that was 4 years ago, I'm going to unmute this test and if it's still an issue, the new test automation will open a new issue for it using the current muting mechanism. Relates #70595 (cherry picked from commit 4b31293)
* This is a copy from the original ticket #120171 * Update docs/reference/search/search-your-data/paginate-search-results.asciidoc Co-authored-by: Liam Thompson <[email protected]> --------- Co-authored-by: George Wallace <[email protected]> Co-authored-by: Liam Thompson <[email protected]>
The LuceneSourceOperator is supposed to terminate when it reaches the limit; unfortunately, we don't have a test to cover this. Due to this bug, we continue scanning all segments, even though we discard the results as the limit was reached. This can cause performance issues for simple queries like FROM .. | LIMIT 10, when Lucene indices are on the warm or cold tier. I will submit a follow-up PR to ensure we only collect up to the limit across multiple drivers.
) (#123922) updated flatten graph docs to include a real flattened graph
) (#123624) * [IDEA] Enable Gradle Configuration Cache for Gradle Runner This should speedup repetitives usages of the Gradle Runner for the majority of test executions We added a flag to disable it explicitly if it does not work for certain scenarios
#123972) Fixes misleading assertion configuration for test tasks from the command line. We support the following command line args: 1. `-Dtests.jvm.argline=-disableassertions` 2. `-Dtests.jvm.argline=-da` 3. `-Dtests.asserts=false`
…uginFuncTest supports linux aarch distributions #119868
…uginFuncTest bwc expanded distribution folder can be resolved as bwc project artifact #119869
bad link generation for github issue
In the 8.17 docs there is a statement that intends to say that nodes without roles are coordinating-only nodes. However, the wording was misleading because it referred to leaving the setting _unset_ rather than explictly setting it to _empty_.
* Move RPM/Debian note above for clarity. * Add info on checking the setting before changing it I've noticed on my machine by default it has been set to 1048576
|
Documentation preview: |
elasticsearchmachine
added
v8.17.4
external-contributor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
71 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.
gradle check?Description