Project

General

Profile

Actions

Bug #23816

closed

disable bluestore cache caused a rocksdb error

Added by Honggang Yang about 6 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Community (user)
Tags:
Backport:
luminous
Regression:
No
Severity:
1 - critical
Reviewed:
Affected Versions:
ceph-qa-suite:
rados
Component(RADOS):
BlueStore
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

I disabled bluestore/rocksdb cache to estimate ceph-osd's memory consumption
by set bluestore_cache_size_ssd/bluestore_cache_size_hdd/bluestore_cache_size to 0.

This caused a rocksdb error:

 2018-04-19 10:24:29.444 7f6926908240 -1 bluestore(/var/lib/ceph/osd/ceph-0/) _read_fsid unparsable uuid
  2018-04-19 10:24:29.468 7f6926908240 -1 rocksdb: Invalid argument: Enable cache_index_and_filter_blocks, , but block cache is disabled
  2018-04-19 10:24:29.468 7f6926908240 -1 bluestore(/var/lib/ceph/osd/ceph-0/) _open_db erroring opening db:
  2018-04-19 10:24:30.468 7f6926908240 -1 bluestore(/var/lib/ceph/osd/ceph-0/) mkfs failed, (5) Input/output error
  2018-04-19 10:24:30.468 7f6926908240 -1 OSD::mkfs: ObjectStore::mkfs failed with error (5) Input/output error
  2018-04-19 10:24:30.468 7f6926908240 -1  ** ERROR: error creating empty object store in /var/lib/ceph/osd/ceph-0/: (5) Input/output error 

So, if block cache is disabled, we should not set cache_index_and_filter_blocks.


Related issues 1 (0 open1 closed)

Copied to RADOS - Backport #23926: luminous: disable bluestore cache caused a rocksdb errorRejectedActions
Actions #2

Updated by Josh Durgin almost 6 years ago

  • Status changed from New to Fix Under Review
Actions #3

Updated by Sage Weil almost 6 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport set to luminous
Actions #4

Updated by Nathan Cutler almost 6 years ago

  • Copied to Backport #23926: luminous: disable bluestore cache caused a rocksdb error added
Actions #5

Updated by Nathan Cutler about 3 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions

Also available in: Atom PDF