FAQ
You can follow the instructions given at
http://www.cloudera.com/content/cloudera-content/cloudera-docs/CM5/latest/Cloudera-Manager-Administration-Guide/cm5ag_upgrading_cm.html
for
upgrading CM.

On Tue, May 13, 2014 at 11:27 AM, MrAkhe83 wrote:

Hi,

I can see 5.0.1-1 is now available.

What is the process for the upgrade?

Is it enough to only download the parcel, distribute it, activate it and
restart all services?

Thx

On Monday, May 12, 2014 1:55:13 PM UTC-5, Darren Lo wrote:

5.0.1 is coming very soon. Sorry I was a little over-zealous in my
previous timeframe.

On Mon, May 12, 2014 at 11:47 AM, MrAkhe83 wrote:

Hi,

has 5.1 already been released?

regards,
J

On Wednesday, May 7, 2014 3:06:56 PM UTC-5, Darren Lo wrote:

The root cause is a bug in our upgrade code where we didn't handle the
upgrade of certain commands correctly when migrating the commands schema to
add new capabilities. The bug isn't database-specific.

On Wed, May 7, 2014 at 1:03 PM, MrAkhe83 wrote:

Thanks Darren,

but what is the root cause of this problem? i am using mysql only for
hive..the rest is all postgres.

Thx

On Wednesday, May 7, 2014 1:50:15 PM UTC-5, Darren Lo wrote:

A fix for this bug will be released later this week. It's probably
easiest to just wait for that fix. Otherwise you can try running manual sql
to fix the problem, but that hasn't always been successful.

For a potentially helpful workaround via direct sql, see:
https://groups.google.com/a/cloudera.org/forum/#!searchin/sc
m-users/DbCommand%7Csort:date/scm-users/bmkOdHPJppg/8fFSxKlASTgJ

Your posgresql username / password is in /etc/cloudera-scm-server/db.
properties. Make sure you specify the port of 7432 when connecting
to your postgresql server.

Also be sure to back up your db before mucking around with anything.
Hopefully you also took a backup before your upgrade, and can revert to
that while you wait for the fix.

Thanks,
Darren

On Wed, May 7, 2014 at 11:12 AM, MrAkhe83 wrote:

After doing a yum upgrade 'cloudera-*' for CM5.0 upgrade i am seeing
the following in the logs:

2014-05-07 13:07:55,811 ERROR [MainThread:hibernate.Assertio
nFailure@43] HHH000099: an assertion failure occured (this may
indicate a bug in Hibernate, but is more likely due to unsafe use of the
session): org.hibernate.AssertionFailure: Unable to perform
un-delete for instance com.cloudera.cmf.model.DbCommand
2014-05-07 13:07:55,815 ERROR [MainThread:cmf.Main@201] Server
failed.
javax.persistence.RollbackException: Error while committing the
transaction
at org.hibernate.ejb.TransactionImpl.commit(TransactionImpl.jav
a:92)
at com.cloudera.enterprise.AbstractWrappedEntityManager.commit(
AbstractWrappedEntityManager.java:110)
at com.cloudera.cmf.persist.CmfEntityManager.commit(CmfEntityMa
nager.java:368)
at com.cloudera.server.cmf.Main.deleteDeprecatedCommands(Main.j
ava:709)
at com.cloudera.server.cmf.Main.<init>(Main.java:267)
at com.cloudera.server.cmf.Main.main(Main.java:196)
Caused by: org.hibernate.AssertionFailure: Unable to perform
un-delete for instance com.cloudera.cmf.model.DbCommand
at org.hibernate.engine.spi.ActionQueue.unScheduleDeletion(Acti
onQueue.java:527)
at org.hibernate.event.internal.DefaultPersistEventListener.onP
ersist(DefaultPersistEventListener.java:157)
at org.hibernate.internal.SessionImpl.firePersistOnFlush(Sessio
nImpl.java:879)
at org.hibernate.internal.SessionImpl.persistOnFlush(SessionImp
l.java:872)
at org.hibernate.engine.spi.CascadingAction$8.cascade(Cascading
Action.java:346)
at org.hibernate.engine.internal.Cascade.cascadeToOne(Cascade.j
ava:388)
at org.hibernate.engine.internal.Cascade.cascadeAssociation(Cas
cade.java:331)
at org.hibernate.engine.internal.Cascade.cascadeProperty(Cascad
e.java:209)
at org.hibernate.engine.internal.Cascade.cascade(Cascade.java:1
66)
at org.hibernate.event.internal.AbstractFlushingEventListener.c
ascadeOnFlush(AbstractFlushingEventListener.java:162)
at org.hibernate.event.internal.AbstractFlushingEventListener.p
repareEntityFlushes(AbstractFlushingEventListener.java:153)
at org.hibernate.event.internal.AbstractFlushingEventListener.f
lushEverythingToExecutions(AbstractFlushingEventListener.java:89)
at org.hibernate.event.internal.DefaultFlushEventListener.onFlu
sh(DefaultFlushEventListener.java:51)
at org.hibernate.internal.SessionImpl.flush(SessionImpl.java:12
34)
at org.hibernate.internal.SessionImpl.managedFlush(SessionImpl.
java:404)
at org.hibernate.engine.transaction.internal.jdbc.JdbcTransacti
on.beforeTransactionCommit(JdbcTransaction.java:101)
at org.hibernate.engine.transaction.spi.AbstractTransactionImpl.
commit(AbstractTransactionImpl.java:175)
at org.hibernate.ejb.TransactionImpl.commit(TransactionImpl.jav
a:75)
... 5 more

we are using postgresql and not mysql.

What is the workaround?

Thx

To unsubscribe from this group and stop receiving emails from it,
send an email to scm-users+...@cloudera.org.
To unsubscribe from this group and stop receiving emails from it,
send an email to scm-users+...@cloudera.org.
To unsubscribe from this group and stop receiving emails from it,
send an email to scm-users+...@cloudera.org.
To unsubscribe from this group and stop receiving emails from it, send
an email to scm-users+unsubscribe@cloudera.org.
To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 8 of 10 | next ›
Discussion Overview
groupscm-users @
categorieshadoop
postedMay 7, '14 at 6:12p
activeMay 13, '14 at 7:13p
posts10
users3
websitecloudera.com
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase