Skip to content

deb rpm: remove manual feature of zero-downtime-restart from uninstall phase - #758

Merged
daipom merged 1 commit into
fluent:feature-nodowntimefrom
Watson1978:remove-manual-feature-from-uninstall
Dec 9, 2024
Merged

deb rpm: remove manual feature of zero-downtime-restart from uninstall phase#758
daipom merged 1 commit into
fluent:feature-nodowntimefrom
Watson1978:remove-manual-feature-from-uninstall

Conversation

@Watson1978

@Watson1978 Watson1978 commented Dec 9, 2024

Copy link
Copy Markdown
Contributor

We were going to support two methods of downgrading with zero downtime.

  1. Running v6.x => Install v5.x package by overwriting
  2. Running v6.x => Replace FLUENT_PACKAGE_SERVICE_RESTART value to manual => uninstall v6.x => Install v5.x

The second method is to keep the Fluentd process running after uninstalling it.
We decided to remove 2. method because it may cause confusion for users.

Signed-off-by: Shizuo Fujita <fujita@clear-code.com>
@Watson1978 Watson1978 changed the title deb rpm: remove manual feature from uninstall phase deb rpm: remove manual feature of zero-downtime-restart from uninstall phase Dec 9, 2024
@daipom

daipom commented Dec 9, 2024

Copy link
Copy Markdown
Contributor

Thanks! Looks good!
Let's wait CI results.

@Watson1978
Watson1978 marked this pull request as ready for review December 9, 2024 04:44
@daipom
daipom merged commit 685ba07 into fluent:feature-nodowntime Dec 9, 2024
@daipom

daipom commented Dec 9, 2024

Copy link
Copy Markdown
Contributor

Thanks!

@Watson1978
Watson1978 deleted the remove-manual-feature-from-uninstall branch December 9, 2024 06:04
daipom pushed a commit to daipom/fluent-package-builder that referenced this pull request Dec 10, 2024
…l phase (fluent#758)

We were going to support two methods of downgrading with zero downtime.

1. Running v6.x => Install v5.x package by overwriting
2. Running v6.x => Replace `FLUENT_PACKAGE_SERVICE_RESTART` value to
`manual` => uninstall v6.x => Install v5.x

The second method is to keep the Fluentd process running after
uninstalling it.
We decided to remove `2.` method because it may cause confusion for
users.

Signed-off-by: Shizuo Fujita <fujita@clear-code.com>
daipom pushed a commit to daipom/fluent-package-builder that referenced this pull request Dec 10, 2024
…l phase (fluent#758)

We were going to support two methods of downgrading with zero downtime.

1. Running v6.x => Install v5.x package by overwriting
2. Running v6.x => Replace `FLUENT_PACKAGE_SERVICE_RESTART` value to
`manual` => uninstall v6.x => Install v5.x

The second method is to keep the Fluentd process running after
uninstalling it.
We decided to remove `2.` method because it may cause confusion for
users.

Signed-off-by: Shizuo Fujita <fujita@clear-code.com>
kenhys pushed a commit that referenced this pull request Dec 11, 2024
…l phase (#758)

We were going to support two methods of downgrading with zero downtime.

1. Running v6.x => Install v5.x package by overwriting
2. Running v6.x => Replace `FLUENT_PACKAGE_SERVICE_RESTART` value to
`manual` => uninstall v6.x => Install v5.x

The second method is to keep the Fluentd process running after
uninstalling it.
We decided to remove `2.` method because it may cause confusion for
users.

Signed-off-by: Shizuo Fujita <fujita@clear-code.com>
@kenhys kenhys added this to the 5.2.0 milestone Dec 12, 2024
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

Successfully merging this pull request may close these issues.

3 participants