2.5.1 online update
admin
2,930 Posts
March 7, 2020, 4:15 pmQuote from admin on March 7, 2020, 4:15 pm2.5.1 is available as an online update. fixes bug with journal partition size while adding OSDs, it was caused after moving parameter to central config database. All 2.5.0 users are recommended to upgrade.
2.5.1 is available as an online update. fixes bug with journal partition size while adding OSDs, it was caused after moving parameter to central config database. All 2.5.0 users are recommended to upgrade.
Last edited on March 7, 2020, 4:28 pm by admin · #1
wailer
75 Posts
March 24, 2020, 12:18 amQuote from wailer on March 24, 2020, 12:18 amHi ,
We are planning to upgrade in short to from 2.4.0 to 2.5.1.
This bug affects any OSD created when in 2.5.0 version and not prior versions, correct?
Also , about backend networks, I see since 2.5.0 only uses 1 backend, what will happen when we upgrade to 2.5.1 , what network will remain?
At long term, is there a safe way to transition to the single backend architecture?
Thanks!
Hi ,
We are planning to upgrade in short to from 2.4.0 to 2.5.1.
This bug affects any OSD created when in 2.5.0 version and not prior versions, correct?
Also , about backend networks, I see since 2.5.0 only uses 1 backend, what will happen when we upgrade to 2.5.1 , what network will remain?
At long term, is there a safe way to transition to the single backend architecture?
Thanks!
Last edited on March 24, 2020, 12:30 am by wailer · #2
admin
2,930 Posts
March 24, 2020, 8:15 amQuote from admin on March 24, 2020, 8:15 amYes the journal config bug is in 2.5.0, introduced when we moved all config centrally.
Yes older clusters with 2 backends will continue to work. Internally the config file format /opt/petasan/config/cluster_info.json and /opt/petasan/config/node_info.json still have both backend 1 and backend 2, however we now support that backend 2 could be empty, in such case it will be the same values as backend 1. You should be able to manually put empty "" values to these values and reboot the cluster, but i suggest you try it in a test setup first just to be familiar.
Yes the journal config bug is in 2.5.0, introduced when we moved all config centrally.
Yes older clusters with 2 backends will continue to work. Internally the config file format /opt/petasan/config/cluster_info.json and /opt/petasan/config/node_info.json still have both backend 1 and backend 2, however we now support that backend 2 could be empty, in such case it will be the same values as backend 1. You should be able to manually put empty "" values to these values and reboot the cluster, but i suggest you try it in a test setup first just to be familiar.
2.5.1 online update
admin
2,930 Posts
Quote from admin on March 7, 2020, 4:15 pm2.5.1 is available as an online update. fixes bug with journal partition size while adding OSDs, it was caused after moving parameter to central config database. All 2.5.0 users are recommended to upgrade.
2.5.1 is available as an online update. fixes bug with journal partition size while adding OSDs, it was caused after moving parameter to central config database. All 2.5.0 users are recommended to upgrade.
wailer
75 Posts
Quote from wailer on March 24, 2020, 12:18 amHi ,
We are planning to upgrade in short to from 2.4.0 to 2.5.1.
This bug affects any OSD created when in 2.5.0 version and not prior versions, correct?
Also , about backend networks, I see since 2.5.0 only uses 1 backend, what will happen when we upgrade to 2.5.1 , what network will remain?
At long term, is there a safe way to transition to the single backend architecture?
Thanks!
Hi ,
We are planning to upgrade in short to from 2.4.0 to 2.5.1.
This bug affects any OSD created when in 2.5.0 version and not prior versions, correct?
Also , about backend networks, I see since 2.5.0 only uses 1 backend, what will happen when we upgrade to 2.5.1 , what network will remain?
At long term, is there a safe way to transition to the single backend architecture?
Thanks!
admin
2,930 Posts
Quote from admin on March 24, 2020, 8:15 amYes the journal config bug is in 2.5.0, introduced when we moved all config centrally.
Yes older clusters with 2 backends will continue to work. Internally the config file format /opt/petasan/config/cluster_info.json and /opt/petasan/config/node_info.json still have both backend 1 and backend 2, however we now support that backend 2 could be empty, in such case it will be the same values as backend 1. You should be able to manually put empty "" values to these values and reboot the cluster, but i suggest you try it in a test setup first just to be familiar.
Yes the journal config bug is in 2.5.0, introduced when we moved all config centrally.
Yes older clusters with 2 backends will continue to work. Internally the config file format /opt/petasan/config/cluster_info.json and /opt/petasan/config/node_info.json still have both backend 1 and backend 2, however we now support that backend 2 could be empty, in such case it will be the same values as backend 1. You should be able to manually put empty "" values to these values and reboot the cluster, but i suggest you try it in a test setup first just to be familiar.