Skip to content

Remove deprecated trainer flag Trainer.distributed_backend in favor of Trainer.accelerator#9246

Closed
Tshimanga wants to merge 67 commits intoLightning-AI:masterfrom
Tshimanga:removal/1.5-distributed-backend-trainer-flag
Closed

Remove deprecated trainer flag Trainer.distributed_backend in favor of Trainer.accelerator#9246
Tshimanga wants to merge 67 commits intoLightning-AI:masterfrom
Tshimanga:removal/1.5-distributed-backend-trainer-flag

Conversation

@Tshimanga
Copy link
Copy Markdown
Contributor

What does this PR do?

Removes deprecated Trainer.distributed_backend flag as scheduled for 1.5

Before submitting

  • Was this discussed/approved via a GitHub issue? (not for typos and docs)
  • Did you read the contributor guideline, Pull Request section?
  • Did you make sure your PR does only one thing, instead of bundling different changes together?
  • Did you make sure to update the documentation with your changes? (if necessary)
  • Did you write any new necessary tests? (not for typos and docs)
  • Did you verify new and existing tests pass locally with your changes?
  • Did you list all the breaking changes introduced by this pull request?
  • Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review

Anyone in the community is welcome to review the PR.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

  • Is this pull request ready for review? (if not, please submit in draft mode)
  • Check that all items from Before submitting are resolved
  • Make sure the title is self-explanatory and the description concisely explains the PR
  • Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?

Make sure you had fun coding 🙃

Copy link
Copy Markdown
Contributor

@tchaton tchaton left a comment

Choose a reason for hiding this comment

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

LGTM ! @Tshimanga You are missing some and you have failing tests due to this :)

@mergify mergify bot added the has conflicts label Sep 1, 2021
Copy link
Copy Markdown
Contributor

@kaushikb11 kaushikb11 left a comment

Choose a reason for hiding this comment

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

Thanks @Tshimanga! But Failing tests. Also, at the moment accelerator flag supports Accelerators as well as Training Type plugins. We wish to decouple it, we would be taking a step back with the changes in this PR.

To read more about it, you could refer to #9053

@Tshimanga
Copy link
Copy Markdown
Contributor Author

@tchaton @kaushikb11 Reading over the conversation in #9053 it sounds like there's a lack of consensus for a pretty impactful redesign of accelerators and training type plugins. I can resolve the failures in this PR, but it feels like the refactor should come first to do this right. I think the deprecation of distribution_backend was perhaps premature and it's removal should be kicked back to 1.6.

Thoughts?

@tchaton
Copy link
Copy Markdown
Contributor

tchaton commented Sep 2, 2021

distribution_backend

Hey @Tshimanga,

Yes, we are still debating and the proposal from #9053 is definitely a big BC. If you have any suggestion, feel free to add to the conversation.

But let's pause this depreciation until resolution. Thanks for your hard work !

Best,
T.C

@mergify mergify bot added the has conflicts label Sep 2, 2021
@Tshimanga
Copy link
Copy Markdown
Contributor Author

@tchaton should I move the deprecation test to 1.6 in the meantime?

@tchaton
Copy link
Copy Markdown
Contributor

tchaton commented Sep 3, 2021

Hey @Tshimanga,

We still have a bit of time, let's see if we consensus is reached :)

Still 4-5 weeks left before 1.5.

Best,
T.C

@carmocca carmocca marked this pull request as draft September 4, 2021 02:28
@stale
Copy link
Copy Markdown

stale bot commented Sep 19, 2021

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you need further help see our docs: https://pytorch-lightning.readthedocs.io/en/latest/generated/CONTRIBUTING.html#pull-request or ask the assistance of a core contributor here or on Slack. Thank you for your contributions.

@stale stale bot added the won't fix This will not be worked on label Sep 19, 2021
@stale
Copy link
Copy Markdown

stale bot commented Sep 24, 2021

This pull request is going to be closed. Please feel free to reopen it create a new from the actual master.

@stale stale bot closed this Sep 24, 2021
@awaelchli awaelchli reopened this Sep 28, 2021
@stale stale bot removed the won't fix This will not be worked on label Sep 28, 2021
daniellepintz and others added 27 commits October 18, 2021 21:48
…StatsMonitor` (Lightning-AI#9924)

Co-authored-by: Carlos Mocholí <carlossmocholi@gmail.com>
Co-authored-by: Nicki Skafte Detlefsen <skaftenicki@gmail.com>
Co-authored-by: Rohit Gupta <rohitgr1998@gmail.com>
Co-authored-by: tchaton <thomas@grid.ai>
Co-authored-by: Adrian Wälchli <aedu.waelchli@gmail.com>
Co-authored-by: thomas chaton <thomas@grid.ai>
… `DeviceStatsMonitor` callback (Lightning-AI#9921)

Co-authored-by: Kaushik B <45285388+kaushikb11@users.noreply.github.com>
Co-authored-by: Rohit Gupta <rohitgr1998@gmail.com>
Co-authored-by: tchaton <thomas@grid.ai>
…rategies (Lightning-AI#9931)

Co-authored-by: Carlos Mocholí <carlossmocholi@gmail.com>
…AI#9963)


Co-authored-by: ronif <ronif@users.noreply.github.com>
Co-authored-by: Adrian Wälchli <aedu.waelchli@gmail.com>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: Carlos Mocholí <carlossmocholi@gmail.com>
Co-authored-by: thomas chaton <thomas@grid.ai>
Co-authored-by: edenlightning <66261195+edenlightning@users.noreply.github.com>
Co-authored-by: thomas chaton <thomas@grid.ai>
* fix

* update tests

* chlog

* skip windows
Co-authored-by: Carlos Mocholí <carlossmocholi@gmail.com>
@rohitgr7
Copy link
Copy Markdown
Contributor

I somewhere messed up the with git here.. closing this one .. will open another

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

Labels

deprecation Includes a deprecation design Includes a design discussion refactor

Projects

None yet

Development

Successfully merging this pull request may close these issues.