Skip to content

fs: Mantle: A Programmable Metadata Load Balancer - #10887

Merged
jcsp merged 3 commits into
ceph:masterfrom
michaelsevilla:mantle
Oct 26, 2016
Merged

jcsp merged 3 commits into
ceph:masterfrom
michaelsevilla:mantle

Conversation

@michaelsevilla

Copy link
Copy Markdown
Contributor

@smithfarm smithfarm changed the title Mantle: A Programmable Metadata Load Balancer fs: Mantle: A Programmable Metadata Load Balancer Aug 28, 2016
@gregsfortytwo gregsfortytwo added cephfs Ceph File System needs-review labels Sep 6, 2016
Comment thread src/mds/MDBalancer.cc Outdated
#include "common/errno.h"

#define dout_subsys ceph_subsys_mds
#define dout_subsys ceph_subsys_mds_balancer

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure we want this: iirc the --debug-mds flag isn't a prefixish thing, so this change will silence all the balancer and migrator logs for people who currently set --debug-mds

@jcsp

jcsp commented Sep 9, 2016

Copy link
Copy Markdown
Contributor

This looks to be exactly what was discussed at the last CDM, so all of my comments are just detail things. At a high level: 👍

Does #7338 need poking along somehow?

@michaelsevilla

Copy link
Copy Markdown
Contributor Author

I already poked #7338 and @noahdesu is going to take care of it.

Dumb question: is it better to rebase (keep history clean but lose your comments) or just add more commits?

@jcsp

jcsp commented Sep 9, 2016

Copy link
Copy Markdown
Contributor

You can either add more commits (and rebase later before merge) or just do a straight history-squashing rebase.

Usually we leave comments on the "files changed" view (not individual commits) so that they survive a rebase, but I mistakenly put some on commits here -- my fault if they get lost in a rebase.

@gregsfortytwo

Copy link
Copy Markdown
Member

Luckily Github finally fixed that nonsense, at least as long as you navigate from the PR view into the commit (not sure if you just go straight to a commit). You can tell it's working because all the comments are on the diff, not on a commit. ;)

Personally I prefer commits prefixed with "SQUASH" that are intended to be rebase, as it makes life easier on the reviewer when there are follow-up comments, but that may just be me.

@gregsfortytwo

Copy link
Copy Markdown
Member

I see we did get some updated commits at some point that at least invalidated most comments. @jcsp, want to check this again? Be nice to get it in for @batrick's scaling tests.

@jcsp

jcsp commented Oct 24, 2016

Copy link
Copy Markdown
Contributor

This is good to go now from my point of view (apologies @michaelsevilla for delay). Please could you do a quick rebase as something else has touched CMakeLists.txt in the meantime

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants