Member since
02-04-2014
6
Posts
5
Kudos Received
2
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
4039 | 03-02-2016 12:41 PM | |
6464 | 02-04-2014 04:22 PM |
03-02-2016
11:24 PM
1 Kudo
What action triggered the stacktrace? The stacktrace is from deep within Spring and suggests system level issue, e.g. out of memory. A few things to check: - server log (/var/log/cloudera-scm-server/cloudera-scm-server.log) - management daemon logs (/var/log/cloudera-scm-firehose/*.log - check "Hosts"->"All Hosts" for memory pressure. The "Resources" tab of individual Host page may help as well
... View more
03-02-2016
12:41 PM
1 Kudo
The stacktrace indicates that there is an inconsistency with the Hibernate cache. Restarting CM server should fix the issue. Did you take any unconventional action prior to this issue, e.g. directly accessing the database?
... View more
09-21-2015
03:10 PM
2 Kudos
It looks like you have arrived in an inconsistent state of wanting the parcel to be activated, but it is not distributed, most likely because the distributed parcels were deleted outside of Cloudera Manager. To fix this, I presume that UI is stuck in "Activating" state, but there should be a "Cancel" button, that should reset your state so that you can distribute again. If there is no way to cancel, for whatever reason, you can force deactivate the parcel via API. http://cloudera.github.io/cm_api/apidocs/v6/path__clusters_-clusterName-_parcels_products_-product-_versions_-version-_commands_deactivate.html
... View more
02-04-2014
04:22 PM
Hi, We have confirmed that there is a bug in the configuration UI. It incorrectly attempts to update a Reports Manager configuration although it was not modified. For the time being, the recommended workaround is to update the configurations via API. Sorry for the inconvenience. Herman
... View more