David Turner

Results 52 issues of David Turner

It's possible for a cluster state update task to emit deprecation warnings, but if the task is executed in a batch then these warnings will be exposed to the listener...

>bug
:Distributed/Cluster Coordination
Team:Distributed
v8.5.0

Today `TransportMasterNodeAction$AsyncSingleAction#doStart` captures a reference to the `clusterState` in a couple of listeners that might get used if it needs to use a `ClusterStateObserver` to retry the action. Yet, both...

>bug
:Distributed/Cluster Coordination
Team:Distributed

A couple of places in CCR request the metadata from the remote cluster, mostly in order to see if there are any change to the set of interesting indices: https://github.com/elastic/elasticsearch/blob/12ad399c488f0cc60e19b5e1b29c6d569cb4351a/x-pack/plugin/ccr/src/main/java/org/elasticsearch/xpack/ccr/action/AutoFollowCoordinator.java#L255-L268...

:Distributed/CCR
Team:Distributed
>tech debt

Today submitting an unbatched `ClusterStateUpdateTask` to the `MasterService` is deprecated, and devs are encouraged to write their own batching executor instead. In principle this makes it possible to combine updates...

:Distributed/Cluster Coordination
Team:Distributed
>tech debt

A highly available setup running with `proxy`-mode remote cluster connections needs to be able to handle a failure of the proxy. Today a `proxy`-mode remote cluster connection accepts only a...

>enhancement
:Distributed/Network
Team:Distributed

We encountered a case where a substantial fraction of the heap usage was due to per-segment-per-field `FieldInfo` objects, particularly `FieldInfo#name`. This commit adds a note to the sizing docs about...

>docs
:Distributed/Distributed
Team:Distributed
Team:Docs
v8.2.4
v8.3.4
v8.4.1
v8.5.0

Our recent discussions about supportability identified that exposing more node-by-node system performance metrics in APIs (emulating `vmstat`, `iostat`, `sar`, [`netstat`](https://github.com/elastic/elasticsearch/pull/84653), `mpstat`, and so on) would help a significant proportion of...

:Core/Infra/Core
Team:Core/Infra
Supportability

As noted at https://github.com/elastic/elasticsearch/issues/21471#issuecomment-1201029392, today we assume that anything in the cluster `Metadata` that we don't recognise must belong to a plugin that has since been uninstalled, and just leniently...

:Core/Infra/Plugins
Team:Core/Infra

What guarantees do we offer about the formatting of exception responses? Today the [docs give some examples](https://www.elastic.co/guide/en/elasticsearch/reference/current/common-options.html#common-options-error-options) but do not accurately describe the bits on which clients can rely, and...

:Core/Infra/REST API
Team:Core/Infra

### CI Link https://gradle-enterprise.elastic.co/s/yckwl5zjomfas ### Repro line ``` ./gradlew ':server:test' --tests "org.elasticsearch.cluster.coordination.CoordinatorTests.testSingleNodeDiscoveryStabilisesEvenWhenDisrupted" -Dtests.seed=949AB28501F8ED37:BBC20DD1A5D4EF81 ``` ### Does it reproduce? Yes ### Applicable branches main ### Failure history https://ci-stats.elastic.co/s/jenkins/goto/da1547f0-2ea6-11ed-8233-4bd40c8511bb - 3 similar-looking...

>test-failure
:Distributed/Cluster Coordination
Team:Distributed