The `is_global_zero` check should be moved to the `logger.save()` implementation

[akashkw]

Proposed refactor

The is_global_zero check should be moved to the logger.save() implementation. https://github.com/PyTorchLightning/pytorch-lightning/blob/7e2f9fbad555242b0ceb2a24e5e4c004f0701bae/pytorch_lightning/loops/epoch/training_epoch_loop.py#L507-L510

Motivation

Same as #8608 and #8589

Pitch

Additional context

Originally posted by @ananthsub in #11920 (comment)

---

If you enjoy Lightning, check out our other projects! ⚡

• Metrics: Machine learning metrics for distributed, scalable PyTorch applications.

• Lite: enables pure PyTorch users to scale their existing code on any kind of device while retaining full control over their own loops and optimization logic.

• Flash: The fastest way to get a Lightning baseline! A collection of tasks for fast prototyping, baselining, fine-tuning, and solving problems with deep learning.

• Bolts: Pretrained SOTA Deep Learning models, callbacks, and more for research and production with PyTorch Lightning and PyTorch.

• Lightning Transformers: Flexible interface for high-performance research using SOTA Transformers leveraging Pytorch Lightning, Transformers, and Hydra.

cc @Borda @awaelchli @edward-io @ananthsub @rohitgr7 @kamil-kaczmarek @Raalsky @Blaizzy

[yamazakiji]

Hi! Can I get assigned to this issue?

[daniellepintz]

Actually I don't think this issue is needed, since we are planning to remove this method anyway in v1.7 along with the removal of flush_logs_every_n_steps, which is in just a few weeks.

https://github.com/PyTorchLightning/pytorch-lightning/blob/7e2f9fbad555242b0ceb2a24e5e4c004f0701bae/pytorch_lightning/loops/epoch/training_epoch_loop.py#L503-L510

[yamazakiji]

@daniellepintz so should I do it or you will close the issue?

[daniellepintz]

I will close it, sorry about that