ceph / ceph/python-crush

some mapping failed

Open
#5 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
22
Forks
8
PR merge metrics
No merged PRs in 30d

Description

Running Ceph 12.2.5, crush 1.0.35 (current PyPI version).

default ceph report does not have information about pg,so I using

```
ceph pg dump -f json > pg_dump.json
# edit crush/ceph/__init__.py,add line 72
report['pgmap'] = json.load(open('pg_dump.json'))
# replace crush_ruleset with crush_rule in line 115
ruleset = pool['crush_rule']
```

and then output is:

```
2018-07-16 16:35:04,999 42.7e map to [32, 320, 144] instead of [32, 320, 167]
2018-07-16 16:35:04,999 42.73 map to [134, 295, 144] instead of [134, 295, 196]
2018-07-16 16:35:05,000 43.57 map to [21, 416, 144] instead of [21, 416, 185]
2018-07-16 16:35:05,004 44.87 map to [41, 144, 314] instead of [41, 314]
2018-07-16 16:35:05,005 44.7d map to [144, 371, 34] instead of [227, 371, 34]
2018-07-16 16:35:05,006 45.f2 map to [144, 414, 48] instead of [237, 414, 48]
2018-07-16 16:35:05,007 45.46 map to [144, 336, 14] instead of [234, 336, 14]
2018-07-16 16:35:05,008 46.45 map to [361, 144, 47] instead of [361, 256, 47]
2018-07-16 16:35:05,008 46.65 map to [144, 377, 23] instead of [218, 377, 23]
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with crush/ceph/__init__.py around lines 72 and 115, then reproduce the report using Ceph 12.2.5 and the pg_dump.json data from `ceph pg dump -f json`. Compare the mappings reported by the issue with the expected mappings and determine what behavior should be corrected.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.