[jira] [Commented] (HBASE-17931) Rolling upgrade on branch-1 and master
[ https://issues.apache.org/jira/browse/HBASE-17931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972146#comment-15972146 ] stack commented on HBASE-17931: --- Thanks for raising the flag on this one [~yangzhe1991]. Agree its a blocker. Lets figure a receipe. Generally we'll upgrade Master first on rolling upgrade. Could bake into it the knowledge that it not assign hbase:meta to an old RS. Requiring users go to 1.4 first and then to 2.0 would be ok too if we had too... Thanks. > Rolling upgrade on branch-1 and master > -- > > Key: HBASE-17931 > URL: https://issues.apache.org/jira/browse/HBASE-17931 > Project: HBase > Issue Type: Bug > Components: scan >Affects Versions: 1.4.0 >Reporter: Phil Yang >Priority: Blocker > Fix For: 2.0.0 > > > In branch-1 and master we have some improvement and new features on scanning > which is not compatible. > A client of old version to a server of new version is compatible (must be a > bug if not, maybe need some test?). > A client of new version may not be able to read from a server of old version > correctly (because of scan limit, moreResults flag, etc), which is ok for > major/minor upgrade and we can tell users to upgrade server before upgrading > client. But RS also use scan to read meta. If meta table is in RS of old > version, all RSs of new version may have trouble while scanning meta table. > So we should make sure meta table always in servers of new version. Force > meta table in Master and upgrade Master first, or assign meta table in region > servers with latest version? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17931) Rolling upgrade on branch-1 and master
[ https://issues.apache.org/jira/browse/HBASE-17931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972073#comment-15972073 ] Phil Yang commented on HBASE-17931: --- Another option is keep compatibility between client 1.4 and server 1.3, and compatibility between client 2.0 and server 1.4. Then we can rolling upgrade from 1.3 to 1.4 and from 1.4 to 2.0. But we have to release 1.4.0 before 2.0.0. Which means we should return more results in 1.4 server and don't have to do this in 2.0 > Rolling upgrade on branch-1 and master > -- > > Key: HBASE-17931 > URL: https://issues.apache.org/jira/browse/HBASE-17931 > Project: HBase > Issue Type: Bug > Components: scan >Affects Versions: 1.4.0 >Reporter: Phil Yang >Priority: Blocker > Fix For: 2.0.0 > > > In branch-1 and master we have some improvement and new features on scanning > which is not compatible. > A client of old version to a server of new version is compatible (must be a > bug if not, maybe need some test?). > A client of new version may not be able to read from a server of old version > correctly (because of scan limit, moreResults flag, etc), which is ok for > major/minor upgrade and we can tell users to upgrade server before upgrading > client. But RS also use scan to read meta. If meta table is in RS of old > version, all RSs of new version may have trouble while scanning meta table. > So we should make sure meta table always in servers of new version. Force > meta table in Master and upgrade Master first, or assign meta table in region > servers with latest version? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17931) Rolling upgrade on branch-1 and master
[ https://issues.apache.org/jira/browse/HBASE-17931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15971963#comment-15971963 ] Duo Zhang commented on HBASE-17931: --- Most issues under HBASE-17143 have the potential to break the compatibility of old server and new client... And the most dangerous one is HBASE-17508. We will use this feature when scan meta. Maybe we could do something on the implementation. We could return more results then expected when scan, and the upper layer should just drop the needless results. For now I believe there will be a fatal error if server does not support limit as I added some asserts in the code... Thanks. > Rolling upgrade on branch-1 and master > -- > > Key: HBASE-17931 > URL: https://issues.apache.org/jira/browse/HBASE-17931 > Project: HBase > Issue Type: Bug > Components: scan >Affects Versions: 1.4.0 >Reporter: Phil Yang >Priority: Blocker > Fix For: 2.0.0 > > > In branch-1 and master we have some improvement and new features on scanning > which is not compatible. > A client of old version to a server of new version is compatible (must be a > bug if not, maybe need some test?). > A client of new version may not be able to read from a server of old version > correctly (because of scan limit, moreResults flag, etc), which is ok for > major/minor upgrade and we can tell users to upgrade server before upgrading > client. But RS also use scan to read meta. If meta table is in RS of old > version, all RSs of new version may have trouble while scanning meta table. > So we should make sure meta table always in servers of new version. Force > meta table in Master and upgrade Master first, or assign meta table in region > servers with latest version? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17931) Rolling upgrade on branch-1 and master
[ https://issues.apache.org/jira/browse/HBASE-17931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15971392#comment-15971392 ] Jerry He commented on HBASE-17931: -- Could we list the breaking changes or JIRAs? > Rolling upgrade on branch-1 and master > -- > > Key: HBASE-17931 > URL: https://issues.apache.org/jira/browse/HBASE-17931 > Project: HBase > Issue Type: Bug > Components: scan >Affects Versions: 1.4.0 >Reporter: Phil Yang >Priority: Blocker > Fix For: 2.0.0 > > > In branch-1 and master we have some improvement and new features on scanning > which is not compatible. > A client of old version to a server of new version is compatible (must be a > bug if not, maybe need some test?). > A client of new version may not be able to read from a server of old version > correctly (because of scan limit, moreResults flag, etc), which is ok for > major/minor upgrade and we can tell users to upgrade server before upgrading > client. But RS also use scan to read meta. If meta table is in RS of old > version, all RSs of new version may have trouble while scanning meta table. > So we should make sure meta table always in servers of new version. Force > meta table in Master and upgrade Master first, or assign meta table in region > servers with latest version? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17931) Rolling upgrade on branch-1 and master
[ https://issues.apache.org/jira/browse/HBASE-17931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970967#comment-15970967 ] Phil Yang commented on HBASE-17931: --- HDFS has similar command "dfsadmin -rollingUpgrade xxx". But it will make the process of rolling upgrade more complicated in the future HBase releases? > Rolling upgrade on branch-1 and master > -- > > Key: HBASE-17931 > URL: https://issues.apache.org/jira/browse/HBASE-17931 > Project: HBase > Issue Type: Bug > Components: scan >Affects Versions: 1.4.0 >Reporter: Phil Yang >Priority: Blocker > Fix For: 2.0.0 > > > In branch-1 and master we have some improvement and new features on scanning > which is not compatible. > A client of old version to a server of new version is compatible (must be a > bug if not, maybe need some test?). > A client of new version may not be able to read from a server of old version > correctly (because of scan limit, moreResults flag, etc), which is ok for > major/minor upgrade and we can tell users to upgrade server before upgrading > client. But RS also use scan to read meta. If meta table is in RS of old > version, all RSs of new version may have trouble while scanning meta table. > So we should make sure meta table always in servers of new version. Force > meta table in Master and upgrade Master first, or assign meta table in region > servers with latest version? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-17931) Rolling upgrade on branch-1 and master
[ https://issues.apache.org/jira/browse/HBASE-17931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15970956#comment-15970956 ] Duo Zhang commented on HBASE-17931: --- Or maybe we should introduce a Tool for doing rolling upgrading between minor and major releases? > Rolling upgrade on branch-1 and master > -- > > Key: HBASE-17931 > URL: https://issues.apache.org/jira/browse/HBASE-17931 > Project: HBase > Issue Type: Bug > Components: scan >Affects Versions: 1.4.0 >Reporter: Phil Yang >Priority: Blocker > Fix For: 2.0.0 > > > In branch-1 and master we have some improvement and new features on scanning > which is not compatible. > A client of old version to a server of new version is compatible (must be a > bug if not, maybe need some test?). > A client of new version may not be able to read from a server of old version > correctly (because of scan limit, moreResults flag, etc), which is ok for > major/minor upgrade and we can tell users to upgrade server before upgrading > client. But RS also use scan to read meta. If meta table is in RS of old > version, all RSs of new version may have trouble while scanning meta table. > So we should make sure meta table always in servers of new version. Force > meta table in Master and upgrade Master first, or assign meta table in region > servers with latest version? -- This message was sent by Atlassian JIRA (v6.3.15#6346)
