Hi, just for completeness in case anyone has the same problem and gets here. I was using the command in the response from @Scharan but the error was because I was using the wrong version of Python 3.6, but this requires Python 3.8 or above. After upgrading to Py3.8, the comand worked as expected, only with a couple of warnings as shown bellow:   # ./build/env/bin/hue --cm-managed createsuperuser /opt/cloudera/parcels/CDH-7.1.9-1.cdh7.1.9.p6.51045883/lib/hue/build/env/lib/python3.8/site-packages/oauth2/grant.py:320: SyntaxWarning: "is" with a literal. Did you mean "=="? if isinstance(value, tuple) and len(value) is 2: Username (leave blank to use 'root'): prueba_permisos Email address: prueba_permisos@test.org Password: Password (again): Superuser created successfully.     ... View more

Hello @Amn_468  Yes CDH 6.3.3 Supports Oracle 19.  https://docs.cloudera.com/documentation/enterprise/6/release-notes/topics/rg_database_requirements.html Cheers! Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button. ... View more

apparently,  you have mismatch UUIDs for the 'master3.com'  peers { permanent_uuid: "8be74245ecaf4b5baf18b24dbc730922" member_type: VOTER last_known_addr { host: "master3.com" port: 7051 } }   as I can not see this UUID in consensus matrix  A = 865af50ae13e4cfagh5719b865d6716a B = c8d59ba15dbb4578900f597bb48bd9e0 C = 8be74245ecaf4b5baf18b24dbc7318ea   so what you can do now is to manually modify the consensus metadata on this 'B' host, so you need to stop this Kudu master role on 'B' host, then locate the directory - 'consensus-meta' on this  host (this folder could be either under the directory of 'fs_wal_dir' , or the first disk of 'fs_data_dirs'),  then you will use "kudu pbc dump 00000000000000000000000000000000" to check the all peers UUID, and I believe you will see the same wrong UUID - '8be74245ecaf4b5baf18b24dbc730922' in the output.   The actions you can take is to backup this 00000000000000000000000000000000 file, and use 'kudu pbc edit 00000000000000000000000000000000' to change the wrong UUID to '8be74245ecaf4b5baf18b24dbc7318ea' (the data displayed in "kudu pbc edit' is encoded UUID string, so you may want to check other 2 Master hosts to get the encoded UUID string.   after above, then you restart this master to see if this issue can be fixed.         ... View more