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

Log results of each plugin in scheduler framework #83538

Closed
wants to merge 2 commits into from

Conversation

wgliang
Copy link
Contributor

@wgliang wgliang commented Oct 6, 2019

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #83401

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Log results of each plugin in scheduler framework

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

NONE

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Oct 6, 2019
@wgliang wgliang force-pushed the cleanup/log-each-plugins branch 2 times, most recently from 86b7400 to 174225a Compare October 7, 2019 03:47
@alculquicondor
Copy link
Member

/assign @liu-cong

pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
pkg/scheduler/framework/v1alpha1/framework_test.go Outdated Show resolved Hide resolved
@wgliang wgliang force-pushed the cleanup/log-each-plugins branch 3 times, most recently from 3932452 to 32cb44a Compare October 8, 2019 06:19
Copy link
Contributor

@liu-cong liu-cong left a comment

Choose a reason for hiding this comment

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

Can you mark resolved comments as "Resolved"? Thanks!

pkg/scheduler/framework/v1alpha1/framework_test.go Outdated Show resolved Hide resolved
@wgliang
Copy link
Contributor Author

wgliang commented Oct 9, 2019

/test pull-kubernetes-e2e-gce

pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
@wgliang wgliang force-pushed the cleanup/log-each-plugins branch 3 times, most recently from 7fb50d3 to 63fe2a5 Compare October 11, 2019 02:48
@liu-cong
Copy link
Contributor

/lgtm

Thanks Leon!

/assign ahg-g

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 11, 2019
@wgliang
Copy link
Contributor Author

wgliang commented Oct 12, 2019

/ping @ahg-g

@wgliang
Copy link
Contributor Author

wgliang commented Oct 14, 2019

/priority important-soon

@k8s-ci-robot k8s-ci-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Oct 14, 2019
@liu-cong
Copy link
Contributor

can you rebase

Copy link
Member

@ahg-g ahg-g left a comment

Choose a reason for hiding this comment

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

I put some 19 comments on this PR, I am very skeptical that this is going to be useful, logging for each pod for each node on each extension point is massive, even if it was enabled temporarily. I don' think this should be merged.

pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
pkg/scheduler/framework/v1alpha1/framework.go Outdated Show resolved Hide resolved
@ahg-g
Copy link
Member

ahg-g commented Oct 17, 2019

I put some 19 comments on this PR, I am very skeptical that this is going to be useful, logging for each pod for each node on each extension point is massive, even if it was enabled temporarily. I don' think this should be merged.

if we want more insights from logs, we can do that outside the framework: log a line after running all filters on all nodes for example.

@k8s-ci-robot
Copy link
Contributor

New changes are detected. LGTM label has been removed.

@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 21, 2019
@wgliang
Copy link
Contributor Author

wgliang commented Oct 21, 2019

I put some 19 comments on this PR, I am very skeptical that this is going to be useful, logging for each pod for each node on each extension point is massive, even if it was enabled temporarily. I don' think this should be merged.

if we want more insights from logs, we can do that outside the framework: log a line after running all filters on all nodes for example.

@ahg-g Thanks for your review. I've updated and rebased it.

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: wgliang
To complete the pull request process, please assign ahg-g
You can assign the PR to them by writing /assign @ahg-g in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@@ -586,7 +594,7 @@ func TestRecordingMetrics(t *testing.T) {
},
{
name: "Filter - Success",
action: func(f Framework) { f.RunFilterPlugins(context.Background(), nil, pod, nil) },
action: func(f Framework) { f.RunFilterPlugins(context.Background(), nil, pod, nodeInfo) },
Copy link
Contributor Author

@wgliang wgliang Oct 22, 2019

Choose a reason for hiding this comment

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

This is to solve the panic issue(L346).

errMsg := fmt.Sprintf("error while running %q filter plugin for pod %q: %v",
pl.Name(), pod.Name, status.Message())
errMsg := fmt.Sprintf("error while running %q filter plugin for pod %q on node %v: %v",
pl.Name(), pod.Name, nodeInfo.Node().Name, status.Message())
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Print nodeInfo.Node().Name

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Jan 20, 2020
@k8s-ci-robot
Copy link
Contributor

@wgliang: PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 19, 2020
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Log results of each plugin in scheduler framework
6 participants