IllegalStateException: Base role config group of type <rolename> not found in service <servicename>

0 votes
5 views
asked Aug 28, 2017 in Hadoop by admin (4,410 points)
SummaryThis exception can occur with any service if the Base Role Group is incorrectly deleted from the CM Database.
Last Published Date5/15/2017 12:05 PM
Symptoms

This exception can happen for any service.  As an example, an Impala role might fail to start due to this exception:

java.lang.IllegalStateException: Base role config group of type IMPALAD not found in service impala
Applies To

This exception can occur with any service if the Base Role Group is incorrectly deleted from the CM Database.

Cause

If a base <Role> Default Group is no longer available, likely caused by manually deleting the role group directly from the CM Database, the error will occur.

A possible scenario is that a new Role Group is created and renamed to match the name of the base Role Group.  The base Role Group is then renamed to something different.  After that, all the Roles are moved to the new Role Group.   This creates a situation where the empty base Role Group cannot be deleted despite having a name that looks like it is not the base Role Group.  Since a base Role Group cannot be deleted, an incorrect workaround may be used to delete the Role Group directly from the CM Database.  As a result, the base Role Group is now missing and causes the service to fail on startup.

Instructions

Restore the deleted base Role Group from a backup of the CM Database from prior to the deletion.

If the CM Admin would still like to delete the extra Role Group, use the following steps, otherwise it is ok to start up the service and leave the Role Groups as-is.

  1. Move the roles back to the base <Role> Default Group and rename it as such to prevent confusion.
  2. Delete the extra Role Group which now has no roles.

Please log in or register to answer this question.

...