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

redis: 3.2.9 -> 4.0.1 #29516

Merged
merged 1 commit into from Sep 18, 2017
Merged

redis: 3.2.9 -> 4.0.1 #29516

merged 1 commit into from Sep 18, 2017

Conversation

adisbladis
Copy link
Member

Motivation for this change

Redis 4.0 has been out for a while now and brings some nice additions:

  • Modules system
  • Better replication
  • Non blocking deletions
  • Compatibility with NAT setups

Sadly the NAT feature brings an incompatible change to the Redis Cluster protocol so an existing cluster has to be mass-rebooted.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • Linux
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

@rycee
Copy link
Member

rycee commented Sep 18, 2017

I like this but wonder if there should be a redis3 attribute for the 3.x version?

@adisbladis
Copy link
Member Author

The 4.x release doesn't break anything except that one change in the clustering protocol so I'm not sure that an attribute for redis3 is necessary.

I have already deployed some projects on Redis 4 without any hiccups or code changes.

@Mic92
Copy link
Member

Mic92 commented Sep 18, 2017

Redis will be restarted on update in NixOS anyway. So this seems fine to me.

@Mic92 Mic92 merged commit a40533f into NixOS:master Sep 18, 2017
@rycee
Copy link
Member

rycee commented Sep 27, 2017

Fair enough, but I think it would be prudent to put an entry in the release notes that this requires a cluster mass-restart since it'll be quite important for larger deploys (I'm not personally affected, though). Sorry about the long delay in coming back to this PR, btw!

globin added a commit that referenced this pull request Sep 27, 2017
@globin
Copy link
Member

globin commented Sep 27, 2017

Done in 34750bb

@rycee
Copy link
Member

rycee commented Sep 27, 2017

Thanks @globin! Much appreciated.

globin added a commit that referenced this pull request Sep 27, 2017
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.

None yet

4 participants