> I think that you clicked activate parcel, it prompted you to restart, and you thought that was an upgrade wizard > when in fact it was just a simple cluster restart.   agreed.    > We're making improvements to this specific experience as well.     Understood.   Thank you for the explanation.      ... View more

> Upgrading CDH will upgrade your Sqoop2 binaries since Sqoop2 is part of CDH.    OK   > Every time you upgrade Sqoop2 binaries you need to run the Sqoop2 upgrade command. > Click on your Sqoop2 service and look for the upgrade command in the actions dropdown menu on the right. > You have to stop the service first.    Then, I am a little puzzled/confused.  I understand your statements to imply that the Cloudera Manager upgrade wizard is broken and does not function properly with respect to Sqoop2.   > Every time you upgrade Sqoop2 binaries you need to run the Sqoop2 upgrade command.    So, the cloudera manager upgrade wizard does not run the Sqoop2 upgrade command ... even though this is a required step.    > You have to stop the service first.    The Cloudera Manager upgrade wizard stops & then starts all of the services in the cluster. The Sqoop2 service fails to start and the cluster is left in a bad state.    This is the behavior that I observed.    Q: Are you saying that this is a known problem with the Cloudera Manager upgrade wizard?      ... View more

> Normally you just run the Sqoop2 upgrade command whenever you upgrade Sqoop binaries.   I don't understand.    I did not explictly/exclusively upgrade the Sqoop binaries. Nor would I know how/where to "run the Sqoop2 upgrade command"   I upgraded the cluster from CDH 5.2.0 => CDH 5.2.1 through the Cloudera Manager web gui.  The upgrade process restarted the cluster the Sqoop2 service (and the Hue service which is dependent upon sqoop2) did not restart.    Please advise.    ... View more

I encountered the same issue when upgrading from CDH 5.2.0 => 5.2.1   I did not find this support thread until after removing the sqoop2 service and reinstalling it.    part of my logs: Caused by: org.apache.sqoop.common.SqoopException: CONN_0007:Connector registration failed Caused by: org.apache.sqoop.common.SqoopException: JDBCREPO_0026:Upgrade required but not allowed - Connector: generic-jdbc-connector The solution of using    Cloudera Manager -> Sqoop2 -> Configuration -> Sqoop 2 Server Default Group -> Advanced   -> Sqoop 2 Server Advanced Configuration Snippet (Safety Valve)     org.apache.sqoop.connector.autoupgrade=true     worked for me.    The Sqoop2 service was able to successfully start   Michael     ... View more

Thank you *very* much for the prompt response.   I'll go through it again and check it out.   > we changed this behavior to never recommend co-located worker and master nodes, except for single node clusters.   very good   ... View more

I figured out how to delete a role group. I am still interested in understanding why the install doesn't *require* one to treat their NameNode, JobTracker, etc. as "special" ... View more