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

Use SpaceWeighted as the default scheduler #188

Closed
nkwangleiGIT opened this issue Apr 23, 2022 · 2 comments
Closed

Use SpaceWeighted as the default scheduler #188

nkwangleiGIT opened this issue Apr 23, 2022 · 2 comments
Assignees

Comments

@nkwangleiGIT
Copy link
Contributor

What steps did you take and what happened:
[A clear and concise description of what the bug is, and what commands you ran.]
As we introduced a new SpaceWeighted scheduler, and it can do better LVM volume binding, see the details in the PR below:
#178
But the default is still CapacityWeighted as we set the default value when initialize the params.

What did you expect to happen:
Use SpaceWeighted as the default scheduler.

The output of the following commands will help us better understand what's going on:
(Pasting long output into a GitHub gist or other Pastebin is fine.)

  • kubectl logs -f openebs-lvm-controller-0 -n kube-system -c openebs-lvm-plugin
  • kubectl logs -f openebs-lvm-node-[xxxx] -n kube-system -c openebs-lvm-plugin
  • kubectl get pods -n kube-system
  • kubectl get lvmvol -A -o yaml

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

  • LVM Driver version: v0.9.0
  • Kubernetes version (use kubectl version): K8S 1.20.x
  • Kubernetes installer & version:
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):
@dsharma-dc
Copy link
Contributor

@abhilashshetty04 This can perhaps be closed if the enhancement is already merged as seen from linked PR?

@abhilashshetty04
Copy link
Contributor

@dsharma-dc , Yes we are using spaceWeighted algorithm by default. Closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants