-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Update redis to 5.0.3 #3066
Update redis to 5.0.3 #3066
Conversation
does rdb format changed between 3.2.4 to 5.0.3. can 5.0.3 reads the redis dump from 3.2.4. this might affect warm reboot since it dumps the redis databased before reboot and then load it after reboot. |
Signed-off-by: Jipan Yang <[email protected]>
@lguohan I don't have the right hardware setup for verifying system warm reboot. VS environment not working ( Actually never worked before even with same redis version) . It is appreciated if someone with hardware resource available may do a quick system warm-reboot test with the redis version change. Checking the log (from current redis to redis 5.03 warm upgrade), it looks data restore is good. <1> orchagent:
<2> neighsyncd
<3> syncd view comparison has issue, but probably not caused by redis version change.
<4> warm-reboot log
|
retest vs please |
|
@pavel-shirshov , we are not using redis rdb tools. |
@lguohan I understand that. The url I provided has answers on your questions:
Yes. It's changed.
Yes it can. Redis makes only backword compatible changes |
@jipanyang , can you save the redis database in a db file and then load the db file in 5.0.3 and see if the db has difference using redis-dump. |
retest vs please |
<1> save DB data with redis 3.2.4
<2> copy data out
<3> reboot into new sonic with redis 5.0.3
<4> copy db data to new image with redis 5.0.3
<5> stop redis db instance
<6> Let redis 5.0.3 pick up the back db data
<7> dump json from redis 5.0.3
<8> copy new json out and compare them with json generated with redis 3.2.4
|
Forgot to update the DB number in previous test (fixed to DB0.json, now DB$i.json).
|
retest vsimage please |
ok so comparison logic issue was caused by redis version change than? |
no, redis version change is fine. comparison logic issue is something else. |
So how come is passing now? |
…lly (#18969) #### Why I did it src/sonic-swss ``` * c36333c3 - (HEAD -> master, origin/master, origin/HEAD) New p4orch development changes (#3066) (6 hours ago) [mint570] * 26a5a1cb - Fix flex counter out-of-order issue by notifying counter operations using SelectableChannel (#3076) (10 hours ago) [Stephen Sun] * 2f8bd9cf - Add support for ECMP and LAG hash offset (#3138) (28 hours ago) [Kumaresh Perumal] ``` #### How I did it #### How to verify it #### Description for the changelog
Signed-off-by: Jipan Yang [email protected]
- What I did
redis version update with debian stretch:
- How I did it
unix default socket changed to /var/run/redis/redis.sock from
/var/run/redis/redis-server.sock to be consistent with current code implementation.
(The other choice is to change all the code to use new default path)
- How to verify it
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)