repositoryanalyze

package
v9.0.0 Latest Latest
Warning

This package is not in the latest version of its module.

 Go to latest Published: Apr 17, 2025 License: Apache-2.0 Imports: 11 Imported by: 0

Documentation

Overview

Analyze a snapshot repository. Analyze the performance characteristics and any incorrect behaviour found in a repository.

The response exposes implementation details of the analysis which may change from version to version. The response body format is therefore not considered stable and may be different in newer versions.

There are a large number of third-party storage systems available, not all of which are suitable for use as a snapshot repository by Elasticsearch. Some storage systems behave incorrectly, or perform poorly, especially when accessed concurrently by multiple clients as the nodes of an Elasticsearch cluster do. This API performs a collection of read and write operations on your repository which are designed to detect incorrect behaviour and to measure the performance characteristics of your storage system.

The default values for the parameters are deliberately low to reduce the impact of running an analysis inadvertently and to provide a sensible starting point for your investigations. Run your first analysis with the default parameter values to check for simple problems. If successful, run a sequence of increasingly large analyses until you encounter a failure or you reach a `blob_count` of at least `2000`, a `max_blob_size` of at least `2gb`, a `max_total_data_size` of at least `1tb`, and a `register_operation_count` of at least `100`. Always specify a generous timeout, possibly `1h` or longer, to allow time for each analysis to run to completion. Perform the analyses using a multi-node cluster of a similar size to your production cluster so that it can detect any problems that only arise when the repository is accessed by many nodes at once.

If the analysis fails, Elasticsearch detected that your repository behaved unexpectedly. This usually means you are using a third-party storage system with an incorrect or incompatible implementation of the API it claims to support. If so, this storage system is not suitable for use as a snapshot repository. You will need to work with the supplier of your storage system to address the incompatibilities that Elasticsearch detects.

If the analysis is successful, the API returns details of the testing process, optionally including how long each operation took. You can use this information to determine the performance of your storage system. If any operation fails or returns an incorrect result, the API returns an error. If the API returns an error, it may not have removed all the data it wrote to the repository. The error will indicate the location of any leftover data and this path is also recorded in the Elasticsearch logs. You should verify that this location has been cleaned up correctly. If there is still leftover data at the specified location, you should manually remove it.

If the connection from your client to Elasticsearch is closed while the client is waiting for the result of the analysis, the test is cancelled. Some clients are configured to close their connection if no response is received within a certain timeout. An analysis takes a long time to complete so you might need to relax any such client-side timeouts. On cancellation the analysis attempts to clean up the data it was writing, but it may not be able to remove it all. The path to the leftover data is recorded in the Elasticsearch logs. You should verify that this location has been cleaned up correctly. If there is still leftover data at the specified location, you should manually remove it.

If the analysis is successful then it detected no incorrect behaviour, but this does not mean that correct behaviour is guaranteed. The analysis attempts to detect common bugs but it does not offer 100% coverage. Additionally, it does not test the following:

* Your repository must perform durable writes. Once a blob has been written it must remain in place until it is deleted, even after a power loss or similar disaster. * Your repository must not suffer from silent data corruption. Once a blob has been written, its contents must remain unchanged until it is deliberately modified or deleted. * Your repository must behave correctly even if connectivity from the cluster is disrupted. Reads and writes may fail in this case, but they must not return incorrect results.

IMPORTANT: An analysis writes a substantial amount of data to your repository and then reads it back again. This consumes bandwidth on the network between the cluster and the repository, and storage space and I/O bandwidth on the repository itself. You must ensure this load does not affect other users of these systems. Analyses respect the repository settings `max_snapshot_bytes_per_sec` and `max_restore_bytes_per_sec` if available and the cluster setting `indices.recovery.max_bytes_per_sec` which you can use to limit the bandwidth they consume.

NOTE: This API is intended for exploratory use by humans. You should expect the request parameters and the response format to vary in future versions.

NOTE: Different versions of Elasticsearch may perform different checks for repository compatibility, with newer versions typically being stricter than older ones. A storage system that passes repository analysis with one version of Elasticsearch may fail with a different version. This indicates it behaves incorrectly in ways that the former version did not detect. You must work with the supplier of your storage system to address the incompatibilities detected by the repository analysis API in any version of Elasticsearch.

NOTE: This API may not work correctly in a mixed-version cluster.

*Implementation details*

NOTE: This section of documentation describes how the repository analysis API works in this version of Elasticsearch, but you should expect the implementation to vary between versions. The request parameters and response format depend on details of the implementation so may also be different in newer versions.

The analysis comprises a number of blob-level tasks, as set by the `blob_count` parameter and a number of compare-and-exchange operations on linearizable registers, as set by the `register_operation_count` parameter. These tasks are distributed over the data and master-eligible nodes in the cluster for execution.

For most blob-level tasks, the executing node first writes a blob to the repository and then instructs some of the other nodes in the cluster to attempt to read the data it just wrote. The size of the blob is chosen randomly, according to the `max_blob_size` and `max_total_data_size` parameters. If any of these reads fails then the repository does not implement the necessary read-after-write semantics that Elasticsearch requires.

For some blob-level tasks, the executing node will instruct some of its peers to attempt to read the data before the writing process completes. These reads are permitted to fail, but must not return partial data. If any read returns partial data then the repository does not implement the necessary atomicity semantics that Elasticsearch requires.

For some blob-level tasks, the executing node will overwrite the blob while its peers are reading it. In this case the data read may come from either the original or the overwritten blob, but the read operation must not return partial data or a mix of data from the two blobs. If any of these reads returns partial data or a mix of the two blobs then the repository does not implement the necessary atomicity semantics that Elasticsearch requires for overwrites.

The executing node will use a variety of different methods to write the blob. For instance, where applicable, it will use both single-part and multi-part uploads. Similarly, the reading nodes will use a variety of different methods to read the data back again. For instance they may read the entire blob from start to end or may read only a subset of the data.

For some blob-level tasks, the executing node will cancel the write before it is complete. In this case, it still instructs some of the other nodes in the cluster to attempt to read the blob but all of these reads must fail to find the blob.

Linearizable registers are special blobs that Elasticsearch manipulates using an atomic compare-and-exchange operation. This operation ensures correct and strongly-consistent behavior even when the blob is accessed by multiple nodes at the same time. The detailed implementation of the compare-and-exchange operation on linearizable registers varies by repository type. Repository analysis verifies that that uncontended compare-and-exchange operations on a linearizable register blob always succeed. Repository analysis also verifies that contended operations either succeed or report the contention but do not return incorrect results. If an operation fails due to contention, Elasticsearch retries the operation until it succeeds. Most of the compare-and-exchange operations performed by repository analysis atomically increment a counter which is represented as an 8-byte blob. Some operations also verify the behavior on small blobs with sizes other than 8 bytes.

Index

Constants

This section is empty.

Variables

View Source 
var ErrBuildPath = errors.New("cannot build path, check for missing path parameters")

ErrBuildPath is returned in case of missing parameters within the build of the request.

Functions

This section is empty.

Types

type NewRepositoryAnalyze 

type NewRepositoryAnalyze func(repository string) *RepositoryAnalyze

NewRepositoryAnalyze type alias for index.

func NewRepositoryAnalyzeFunc 

func NewRepositoryAnalyzeFunc(tp elastictransport.Interface) NewRepositoryAnalyze

NewRepositoryAnalyzeFunc returns a new instance of RepositoryAnalyze with the provided transport. Used in the index of the library this allows to retrieve every apis in once place.

type RepositoryAnalyze 

type RepositoryAnalyze struct {
	// contains filtered or unexported fields
}

func New 

func New(tp elastictransport.Interface) *RepositoryAnalyze

Analyze a snapshot repository. Analyze the performance characteristics and any incorrect behaviour found in a repository.

The response exposes implementation details of the analysis which may change from version to version. The response body format is therefore not considered stable and may be different in newer versions.

There are a large number of third-party storage systems available, not all of which are suitable for use as a snapshot repository by Elasticsearch. Some storage systems behave incorrectly, or perform poorly, especially when accessed concurrently by multiple clients as the nodes of an Elasticsearch cluster do. This API performs a collection of read and write operations on your repository which are designed to detect incorrect behaviour and to measure the performance characteristics of your storage system.

The default values for the parameters are deliberately low to reduce the impact of running an analysis inadvertently and to provide a sensible starting point for your investigations. Run your first analysis with the default parameter values to check for simple problems. If successful, run a sequence of increasingly large analyses until you encounter a failure or you reach a `blob_count` of at least `2000`, a `max_blob_size` of at least `2gb`, a `max_total_data_size` of at least `1tb`, and a `register_operation_count` of at least `100`. Always specify a generous timeout, possibly `1h` or longer, to allow time for each analysis to run to completion. Perform the analyses using a multi-node cluster of a similar size to your production cluster so that it can detect any problems that only arise when the repository is accessed by many nodes at once.

If the analysis fails, Elasticsearch detected that your repository behaved unexpectedly. This usually means you are using a third-party storage system with an incorrect or incompatible implementation of the API it claims to support. If so, this storage system is not suitable for use as a snapshot repository. You will need to work with the supplier of your storage system to address the incompatibilities that Elasticsearch detects.

If the analysis is successful, the API returns details of the testing process, optionally including how long each operation took. You can use this information to determine the performance of your storage system. If any operation fails or returns an incorrect result, the API returns an error. If the API returns an error, it may not have removed all the data it wrote to the repository. The error will indicate the location of any leftover data and this path is also recorded in the Elasticsearch logs. You should verify that this location has been cleaned up correctly. If there is still leftover data at the specified location, you should manually remove it.

If the connection from your client to Elasticsearch is closed while the client is waiting for the result of the analysis, the test is cancelled. Some clients are configured to close their connection if no response is received within a certain timeout. An analysis takes a long time to complete so you might need to relax any such client-side timeouts. On cancellation the analysis attempts to clean up the data it was writing, but it may not be able to remove it all. The path to the leftover data is recorded in the Elasticsearch logs. You should verify that this location has been cleaned up correctly. If there is still leftover data at the specified location, you should manually remove it.

If the analysis is successful then it detected no incorrect behaviour, but this does not mean that correct behaviour is guaranteed. The analysis attempts to detect common bugs but it does not offer 100% coverage. Additionally, it does not test the following:

* Your repository must perform durable writes. Once a blob has been written it must remain in place until it is deleted, even after a power loss or similar disaster. * Your repository must not suffer from silent data corruption. Once a blob has been written, its contents must remain unchanged until it is deliberately modified or deleted. * Your repository must behave correctly even if connectivity from the cluster is disrupted. Reads and writes may fail in this case, but they must not return incorrect results.

IMPORTANT: An analysis writes a substantial amount of data to your repository and then reads it back again. This consumes bandwidth on the network between the cluster and the repository, and storage space and I/O bandwidth on the repository itself. You must ensure this load does not affect other users of these systems. Analyses respect the repository settings `max_snapshot_bytes_per_sec` and `max_restore_bytes_per_sec` if available and the cluster setting `indices.recovery.max_bytes_per_sec` which you can use to limit the bandwidth they consume.

NOTE: This API is intended for exploratory use by humans. You should expect the request parameters and the response format to vary in future versions.

NOTE: Different versions of Elasticsearch may perform different checks for repository compatibility, with newer versions typically being stricter than older ones. A storage system that passes repository analysis with one version of Elasticsearch may fail with a different version. This indicates it behaves incorrectly in ways that the former version did not detect. You must work with the supplier of your storage system to address the incompatibilities detected by the repository analysis API in any version of Elasticsearch.

NOTE: This API may not work correctly in a mixed-version cluster.

*Implementation details*

NOTE: This section of documentation describes how the repository analysis API works in this version of Elasticsearch, but you should expect the implementation to vary between versions. The request parameters and response format depend on details of the implementation so may also be different in newer versions.

The analysis comprises a number of blob-level tasks, as set by the `blob_count` parameter and a number of compare-and-exchange operations on linearizable registers, as set by the `register_operation_count` parameter. These tasks are distributed over the data and master-eligible nodes in the cluster for execution.

For most blob-level tasks, the executing node first writes a blob to the repository and then instructs some of the other nodes in the cluster to attempt to read the data it just wrote. The size of the blob is chosen randomly, according to the `max_blob_size` and `max_total_data_size` parameters. If any of these reads fails then the repository does not implement the necessary read-after-write semantics that Elasticsearch requires.

For some blob-level tasks, the executing node will instruct some of its peers to attempt to read the data before the writing process completes. These reads are permitted to fail, but must not return partial data. If any read returns partial data then the repository does not implement the necessary atomicity semantics that Elasticsearch requires.

For some blob-level tasks, the executing node will overwrite the blob while its peers are reading it. In this case the data read may come from either the original or the overwritten blob, but the read operation must not return partial data or a mix of data from the two blobs. If any of these reads returns partial data or a mix of the two blobs then the repository does not implement the necessary atomicity semantics that Elasticsearch requires for overwrites.

The executing node will use a variety of different methods to write the blob. For instance, where applicable, it will use both single-part and multi-part uploads. Similarly, the reading nodes will use a variety of different methods to read the data back again. For instance they may read the entire blob from start to end or may read only a subset of the data.

For some blob-level tasks, the executing node will cancel the write before it is complete. In this case, it still instructs some of the other nodes in the cluster to attempt to read the blob but all of these reads must fail to find the blob.

Linearizable registers are special blobs that Elasticsearch manipulates using an atomic compare-and-exchange operation. This operation ensures correct and strongly-consistent behavior even when the blob is accessed by multiple nodes at the same time. The detailed implementation of the compare-and-exchange operation on linearizable registers varies by repository type. Repository analysis verifies that that uncontended compare-and-exchange operations on a linearizable register blob always succeed. Repository analysis also verifies that contended operations either succeed or report the contention but do not return incorrect results. If an operation fails due to contention, Elasticsearch retries the operation until it succeeds. Most of the compare-and-exchange operations performed by repository analysis atomically increment a counter which is represented as an 8-byte blob. Some operations also verify the behavior on small blobs with sizes other than 8 bytes.

https://www.elastic.co/docs/api/doc/elasticsearch/v9/operation/operation-snapshot-repository-analyze

func (*RepositoryAnalyze) BlobCount 

func (r *RepositoryAnalyze) BlobCount(blobcount int) *RepositoryAnalyze

BlobCount The total number of blobs to write to the repository during the test. For realistic experiments, you should set it to at least `2000`. API name: blob_count

func (*RepositoryAnalyze) Concurrency 

func (r *RepositoryAnalyze) Concurrency(concurrency int) *RepositoryAnalyze

Concurrency The number of operations to run concurrently during the test. API name: concurrency

func (*RepositoryAnalyze) Detailed 

func (r *RepositoryAnalyze) Detailed(detailed bool) *RepositoryAnalyze

Detailed Indicates whether to return detailed results, including timing information for every operation performed during the analysis. If false, it returns only a summary of the analysis. API name: detailed

func (RepositoryAnalyze) Do 

func (r RepositoryAnalyze) Do(providedCtx context.Context) (*Response, error)

Do runs the request through the transport, handle the response and returns a repositoryanalyze.Response

func (*RepositoryAnalyze) EarlyReadNodeCount 

func (r *RepositoryAnalyze) EarlyReadNodeCount(earlyreadnodecount int) *RepositoryAnalyze

EarlyReadNodeCount The number of nodes on which to perform an early read operation while writing each blob. Early read operations are only rarely performed. API name: early_read_node_count

func (*RepositoryAnalyze) ErrorTrace 

func (r *RepositoryAnalyze) ErrorTrace(errortrace bool) *RepositoryAnalyze

ErrorTrace When set to `true` Elasticsearch will include the full stack trace of errors when they occur. API name: error_trace

func (*RepositoryAnalyze) FilterPath 

func (r *RepositoryAnalyze) FilterPath(filterpaths ...string) *RepositoryAnalyze

FilterPath Comma-separated list of filters in dot notation which reduce the response returned by Elasticsearch. API name: filter_path

func (*RepositoryAnalyze) Header 

func (r *RepositoryAnalyze) Header(key, value string) *RepositoryAnalyze

Header set a key, value pair in the RepositoryAnalyze headers map.

func (*RepositoryAnalyze) HttpRequest 

func (r *RepositoryAnalyze) HttpRequest(ctx context.Context) (*http.Request, error)

HttpRequest returns the http.Request object built from the given parameters.

func (*RepositoryAnalyze) Human 

func (r *RepositoryAnalyze) Human(human bool) *RepositoryAnalyze

Human When set to `true` will return statistics in a format suitable for humans. For example `"exists_time": "1h"` for humans and `"eixsts_time_in_millis": 3600000` for computers. When disabled the human readable values will be omitted. This makes sense for responses being consumed only by machines. API name: human

func (RepositoryAnalyze) IsSuccess 

func (r RepositoryAnalyze) IsSuccess(providedCtx context.Context) (bool, error)

IsSuccess allows to run a query with a context and retrieve the result as a boolean. This only exists for endpoints without a request payload and allows for quick control flow.

func (*RepositoryAnalyze) MaxBlobSize 

func (r *RepositoryAnalyze) MaxBlobSize(bytesize string) *RepositoryAnalyze

MaxBlobSize The maximum size of a blob to be written during the test. For realistic experiments, you should set it to at least `2gb`. API name: max_blob_size

func (*RepositoryAnalyze) MaxTotalDataSize 

func (r *RepositoryAnalyze) MaxTotalDataSize(bytesize string) *RepositoryAnalyze

MaxTotalDataSize An upper limit on the total size of all the blobs written during the test. For realistic experiments, you should set it to at least `1tb`. API name: max_total_data_size

func (RepositoryAnalyze) Perform 

func (r RepositoryAnalyze) Perform(providedCtx context.Context) (*http.Response, error)

Perform runs the http.Request through the provided transport and returns an http.Response.

func (*RepositoryAnalyze) Pretty 

func (r *RepositoryAnalyze) Pretty(pretty bool) *RepositoryAnalyze

Pretty If set to `true` the returned JSON will be "pretty-formatted". Only use this option for debugging only. API name: pretty

func (*RepositoryAnalyze) RareActionProbability 

func (r *RepositoryAnalyze) RareActionProbability(rareactionprobability string) *RepositoryAnalyze

RareActionProbability The probability of performing a rare action such as an early read, an overwrite, or an aborted write on each blob. API name: rare_action_probability

func (*RepositoryAnalyze) RarelyAbortWrites 

func (r *RepositoryAnalyze) RarelyAbortWrites(rarelyabortwrites bool) *RepositoryAnalyze

RarelyAbortWrites Indicates whether to rarely cancel writes before they complete. API name: rarely_abort_writes

func (*RepositoryAnalyze) ReadNodeCount 

func (r *RepositoryAnalyze) ReadNodeCount(readnodecount int) *RepositoryAnalyze

ReadNodeCount The number of nodes on which to read a blob after writing. API name: read_node_count

func (*RepositoryAnalyze) RegisterOperationCount 

func (r *RepositoryAnalyze) RegisterOperationCount(registeroperationcount int) *RepositoryAnalyze

RegisterOperationCount The minimum number of linearizable register operations to perform in total. For realistic experiments, you should set it to at least `100`. API name: register_operation_count

func (*RepositoryAnalyze) Seed 

func (r *RepositoryAnalyze) Seed(seed int) *RepositoryAnalyze

Seed The seed for the pseudo-random number generator used to generate the list of operations performed during the test. To repeat the same set of operations in multiple experiments, use the same seed in each experiment. Note that the operations are performed concurrently so might not always happen in the same order on each run. API name: seed

func (*RepositoryAnalyze) Timeout 

func (r *RepositoryAnalyze) Timeout(duration string) *RepositoryAnalyze

Timeout The period of time to wait for the test to complete. If no response is received before the timeout expires, the test is cancelled and returns an error. API name: timeout

type Response 

type Response struct {

	// BlobCount The number of blobs written to the repository during the test.
	BlobCount int `json:"blob_count"`
	// BlobPath The path in the repository under which all the blobs were written during the
	// test.
	BlobPath string `json:"blob_path"`
	// Concurrency The number of write operations performed concurrently during the test.
	Concurrency int `json:"concurrency"`
	// CoordinatingNode The node that coordinated the analysis and performed the final cleanup.
	CoordinatingNode types.SnapshotNodeInfo `json:"coordinating_node"`
	// DeleteElapsed The time it took to delete all the blobs in the container.
	DeleteElapsed types.Duration `json:"delete_elapsed"`
	// DeleteElapsedNanos The time it took to delete all the blobs in the container, in nanoseconds.
	DeleteElapsedNanos int64 `json:"delete_elapsed_nanos"`
	// Details A description of every read and write operation performed during the test.
	Details types.DetailsInfo `json:"details"`
	// EarlyReadNodeCount The limit on the number of nodes on which early read operations were
	// performed after writing each blob.
	EarlyReadNodeCount int `json:"early_read_node_count"`
	// IssuesDetected A list of correctness issues detected, which is empty if the API succeeded.
	// It is included to emphasize that a successful response does not guarantee
	// correct behaviour in future.
	IssuesDetected []string `json:"issues_detected"`
	// ListingElapsed The time it took to retrieve a list of all the blobs in the container.
	ListingElapsed types.Duration `json:"listing_elapsed"`
	// ListingElapsedNanos The time it took to retrieve a list of all the blobs in the container, in
	// nanoseconds.
	ListingElapsedNanos int64 `json:"listing_elapsed_nanos"`
	// MaxBlobSize The limit on the size of a blob written during the test.
	MaxBlobSize types.ByteSize `json:"max_blob_size"`
	// MaxBlobSizeBytes The limit, in bytes, on the size of a blob written during the test.
	MaxBlobSizeBytes int64 `json:"max_blob_size_bytes"`
	// MaxTotalDataSize The limit on the total size of all blob written during the test.
	MaxTotalDataSize types.ByteSize `json:"max_total_data_size"`
	// MaxTotalDataSizeBytes The limit, in bytes, on the total size of all blob written during the test.
	MaxTotalDataSizeBytes int64 `json:"max_total_data_size_bytes"`
	// RareActionProbability The probability of performing rare actions during the test.
	RareActionProbability types.Float64 `json:"rare_action_probability"`
	// ReadNodeCount The limit on the number of nodes on which read operations were performed
	// after writing each blob.
	ReadNodeCount int `json:"read_node_count"`
	// Repository The name of the repository that was the subject of the analysis.
	Repository string `json:"repository"`
	// Seed The seed for the pseudo-random number generator used to generate the
	// operations used during the test.
	Seed int64 `json:"seed"`
	// Summary A collection of statistics that summarize the results of the test.
	Summary types.SummaryInfo `json:"summary"`
}

Response holds the response body struct for the package repositoryanalyze

https://github.com/elastic/elasticsearch-specification/blob/52c473efb1fb5320a5bac12572d0b285882862fb/specification/snapshot/repository_analyze/SnapshotAnalyzeRepositoryResponse.ts#L24-L108

func NewResponse 

func NewResponse() *Response

NewResponse returns a Response

Source Files

View all Source files

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL
go.dev uses cookies from Google to deliver and enhance the quality of its services and to analyze traffic. Learn more.