Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cli: Add flag to choose pebble as storage engine #5915

Closed
jseldess opened this issue Nov 21, 2019 · 0 comments · Fixed by #6769
Closed

cli: Add flag to choose pebble as storage engine #5915

jseldess opened this issue Nov 21, 2019 · 0 comments · Fixed by #6769
Assignees
Milestone

Comments

@jseldess
Copy link
Contributor

PR: cockroachdb/cockroach#41453

From release notes:

The new --storage-engine flag for cockroach start, and equivalent COCKROACH_STORAGE_ENGINE environment variable, specify the type of storage engine a node should use. Options are rocksdb (default) and pebble. [#41453][#41453] {% comment %}doc{% endcomment %}

@jseldess jseldess modified the milestones: 19.2.x, 20.1 Nov 21, 2019
rmloveland added a commit that referenced this issue Mar 5, 2020
Fixes #5915.

Summary of changes:

- Add docs for `--storage-engine` flag on node start, which can
  be `pebble`, `rocksdb`, or `default`, which makes the
  `--storage-engine` flag sticky for future runs when no engine
  is specified
rmloveland added a commit that referenced this issue Mar 5, 2020
Fixes #5915.

Summary of changes:

- Add docs for `--storage-engine` flag on node start, which can
  be `pebble`, `rocksdb`, or `default`, which makes the
  `--storage-engine` flag sticky for future runs when no engine
  is specified
rmloveland added a commit that referenced this issue Mar 5, 2020
Fixes #5915.

Summary of changes:

- Add docs for `--storage-engine` flag on node start, which can
  be `pebble`, `rocksdb`, or `default`, which makes the
  `--storage-engine` flag sticky for future runs when no engine
  is specified
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants