[
https://issues.apache.org/jira/browse/PHOENIX-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16305780#comment-16305780
]
Pedro Boado commented on PHOENIX-4487:
--------------------------------------
I've done my testing and the fix is working fine. I had replicated the issue
before by following this same steps:
- Spin up a Cloudera CDH Quickstart VM for CDH 5.7
- Installed Cloudera Labs Apache Phoenix 4.7 from
http://archive.cloudera.com/cloudera-labs/phoenix/parcels/1.3/
- Created a couple of tables in Phoenix and checking that querying etc worked
fine.
- Stopped all services
- Upgraded Cloudera Manager to the latest version ( 5.13 ) .
- Uninstalled parcels for CDH 5.7
- Uninstalled parcels for Phoenix 4.7
- Upgraded to CDH 5.11.2
- Installed parcels from 5.13-cdh5.11.2 branch ( published in
http://phoenix.trenddevs.co.uk/parcels/4.13.2-cdh5.11.2/ )
- Started HBase, opened sqlline and checked that the tables and its information
are still queryable.
If the issue was still there phoenix wouldn't start after the parcel upgrade -
errors would be displayed in RS log - .
Thanks guys.
> Missing SYSTEM.MUTEX table upgrading from 4.7 to 4.13
> -----------------------------------------------------
>
> Key: PHOENIX-4487
> URL: https://issues.apache.org/jira/browse/PHOENIX-4487
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.14.0, 4.13.1, 4.13.2-cdh5.11.2
> Reporter: Flavio Pompermaier
> Assignee: James Taylor
> Fix For: 4.14.0, 4.13.2-cdh5.11.2
>
> Attachments: PHOENIX-4487.patch, PHOENIX-4487_v2.patch
>
>
> Upgrading from the official Cloudera Parcel equipped with Phoenix 4.7 to the
> last unofficial parcel (4.13 on CDH 5.11.2) I had the same error of
> https://issues.apache.org/jira/browse/PHOENIX-4293 (apart from the fact that
> the from version was 4.7...).
> The creation of system.mutex table fixed the problem.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
