FAQ
I was viewing the Events in Cloudera Manager 4.6 and saw an entry marked
"IMPORTANT Corrupt executing impala profile". What does this mean? I have
included the stack trace below.

com.cloudera.cmon.ImpalaCorruptProfileException: Profile queryId is too
short: Query
at
com.cloudera.cmf.model.impala.ImpalaRuntimeProfileTree.getQueryId(ImpalaRuntimeProfileTree.java:124)
at
com.cloudera.cmon.ImpalaRuntimeProfileUtils.generateImpalaQueryFromProfile(ImpalaRuntimeProfileUtils.java:153)
at
com.cloudera.cmon.firehose.ImpalaRuntimeProfile.(ImpalaQueryManager.java:283)
at
com.cloudera.cmon.firehose.ImpalaQueryManager.updateQueries(ImpalaQueryManager.java:263)
at
com.cloudera.cmon.firehose.RoleStageReceiver.processImpalaUpdate(RoleStageReceiver.java:196)
at
com.cloudera.cmon.firehose.RoleStageReceiver.receiveItem(RoleStageReceiver.java:72)
at
com.cloudera.cmon.firehose.RoleStageReceiver.receiveItem(RoleStageReceiver.java:38)
at com.cloudera.cmon.pipeline.PipelineStage.driver(PipelineStage.java:273)
at com.cloudera.cmon.pipeline.PipelineStage$2.run(PipelineStage.java:149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)

Thanks,
Ben

Search Discussions

  • Kyle Vigen at Jun 12, 2013 at 11:28 pm
    Hi Ben,

    What version of Impala are you running? Prior to 1.0.1, certain Impala
    queries were missing profile information needed by CM which caused the
    service monitor to log a warning that the profile was corrupt (the
    stack trace you're seeing).

    If you're using CM for Impala query monitoring we recommend that you
    upgrade to Impala 1.0.1. Otherwise you can safely ignore the stack
    trace.

    - Kyle

    On Wed, Jun 12, 2013 at 3:31 PM, Benjamin Kim wrote:
    I was viewing the Events in Cloudera Manager 4.6 and saw an entry marked
    "IMPORTANT Corrupt executing impala profile". What does this mean? I have
    included the stack trace below.

    com.cloudera.cmon.ImpalaCorruptProfileException: Profile queryId is too
    short: Query
    at
    com.cloudera.cmf.model.impala.ImpalaRuntimeProfileTree.getQueryId(ImpalaRuntimeProfileTree.java:124)
    at
    com.cloudera.cmon.ImpalaRuntimeProfileUtils.generateImpalaQueryFromProfile(ImpalaRuntimeProfileUtils.java:153)
    at
    com.cloudera.cmon.firehose.ImpalaRuntimeProfile.<init>(ImpalaRuntimeProfile.java:85)
    at
    com.cloudera.cmon.firehose.ImpalaQueryManager.updateExecutingQueries(ImpalaQueryManager.java:283)
    at
    com.cloudera.cmon.firehose.ImpalaQueryManager.updateQueries(ImpalaQueryManager.java:263)
    at
    com.cloudera.cmon.firehose.RoleStageReceiver.processImpalaUpdate(RoleStageReceiver.java:196)
    at
    com.cloudera.cmon.firehose.RoleStageReceiver.receiveItem(RoleStageReceiver.java:72)
    at
    com.cloudera.cmon.firehose.RoleStageReceiver.receiveItem(RoleStageReceiver.java:38)
    at com.cloudera.cmon.pipeline.PipelineStage.driver(PipelineStage.java:273)
    at com.cloudera.cmon.pipeline.PipelineStage$2.run(PipelineStage.java:149)
    at
    java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)

    Thanks,
    Ben
  • Benjamin Kim at Jun 12, 2013 at 11:32 pm
    Hi Kyle,

    We are using Impala 1.0.1. So, this message can be safely ignored. Correct?

    Thanks,
    Ben
    On Wednesday, June 12, 2013 4:28:47 PM UTC-7, Kyle Vigen wrote:

    Hi Ben,

    What version of Impala are you running? Prior to 1.0.1, certain Impala
    queries were missing profile information needed by CM which caused the
    service monitor to log a warning that the profile was corrupt (the
    stack trace you're seeing).

    If you're using CM for Impala query monitoring we recommend that you
    upgrade to Impala 1.0.1. Otherwise you can safely ignore the stack
    trace.

    - Kyle

    On Wed, Jun 12, 2013 at 3:31 PM, Benjamin Kim wrote:
    I was viewing the Events in Cloudera Manager 4.6 and saw an entry marked
    "IMPORTANT Corrupt executing impala profile". What does this mean? I have
    included the stack trace below.

    com.cloudera.cmon.ImpalaCorruptProfileException: Profile queryId is too
    short: Query
    at
    com.cloudera.cmf.model.impala.ImpalaRuntimeProfileTree.getQueryId(ImpalaRuntimeProfileTree.java:124)
    at
    com.cloudera.cmon.ImpalaRuntimeProfileUtils.generateImpalaQueryFromProfile(ImpalaRuntimeProfileUtils.java:153)
    at
    com.cloudera.cmon.firehose.ImpalaRuntimeProfile.<init>(ImpalaRuntimeProfile.java:85)
    at
    com.cloudera.cmon.firehose.ImpalaQueryManager.updateExecutingQueries(ImpalaQueryManager.java:283)
    at
    com.cloudera.cmon.firehose.ImpalaQueryManager.updateQueries(ImpalaQueryManager.java:263)
    at
    com.cloudera.cmon.firehose.RoleStageReceiver.processImpalaUpdate(RoleStageReceiver.java:196)
    at
    com.cloudera.cmon.firehose.RoleStageReceiver.receiveItem(RoleStageReceiver.java:72)
    at
    com.cloudera.cmon.firehose.RoleStageReceiver.receiveItem(RoleStageReceiver.java:38)
    at
    com.cloudera.cmon.pipeline.PipelineStage.driver(PipelineStage.java:273)
    at
    com.cloudera.cmon.pipeline.PipelineStage$2.run(PipelineStage.java:149)
    at
    java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)

    Thanks,
    Ben
  • Kyle Vigen at Jun 12, 2013 at 11:55 pm
    Hi Ben,

    In Impala 1.0.1 that message should only show up in the logs if an
    invalid query is issued (ex. one with invalid syntax). If it's showing
    up after valid queries then it's a bug and we should investigate more.
    If it's only happening after invalid queries then you can safely
    ignore.

    Thanks,
    - Kyle
    On Wed, Jun 12, 2013 at 4:32 PM, Benjamin Kim wrote:
    Hi Kyle,

    We are using Impala 1.0.1. So, this message can be safely ignored. Correct?

    Thanks,
    Ben

    On Wednesday, June 12, 2013 4:28:47 PM UTC-7, Kyle Vigen wrote:

    Hi Ben,

    What version of Impala are you running? Prior to 1.0.1, certain Impala
    queries were missing profile information needed by CM which caused the
    service monitor to log a warning that the profile was corrupt (the
    stack trace you're seeing).

    If you're using CM for Impala query monitoring we recommend that you
    upgrade to Impala 1.0.1. Otherwise you can safely ignore the stack
    trace.

    - Kyle

    On Wed, Jun 12, 2013 at 3:31 PM, Benjamin Kim wrote:
    I was viewing the Events in Cloudera Manager 4.6 and saw an entry marked
    "IMPORTANT Corrupt executing impala profile". What does this mean? I
    have
    included the stack trace below.

    com.cloudera.cmon.ImpalaCorruptProfileException: Profile queryId is too
    short: Query
    at

    com.cloudera.cmf.model.impala.ImpalaRuntimeProfileTree.getQueryId(ImpalaRuntimeProfileTree.java:124)
    at

    com.cloudera.cmon.ImpalaRuntimeProfileUtils.generateImpalaQueryFromProfile(ImpalaRuntimeProfileUtils.java:153)
    at

    com.cloudera.cmon.firehose.ImpalaRuntimeProfile.<init>(ImpalaRuntimeProfile.java:85)
    at

    com.cloudera.cmon.firehose.ImpalaQueryManager.updateExecutingQueries(ImpalaQueryManager.java:283)
    at

    com.cloudera.cmon.firehose.ImpalaQueryManager.updateQueries(ImpalaQueryManager.java:263)
    at

    com.cloudera.cmon.firehose.RoleStageReceiver.processImpalaUpdate(RoleStageReceiver.java:196)
    at

    com.cloudera.cmon.firehose.RoleStageReceiver.receiveItem(RoleStageReceiver.java:72)
    at

    com.cloudera.cmon.firehose.RoleStageReceiver.receiveItem(RoleStageReceiver.java:38)
    at
    com.cloudera.cmon.pipeline.PipelineStage.driver(PipelineStage.java:273)
    at
    com.cloudera.cmon.pipeline.PipelineStage$2.run(PipelineStage.java:149)
    at

    java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at

    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)

    Thanks,
    Ben
  • Kyle Vigen at Jun 13, 2013 at 1:25 am
    Hi Ben,

    One thing I forgot to mention is that we do plan on improving our
    handling of this in the future. Even queries with syntax errors
    shouldn't generate that stack trace. We want to be able to monitor
    them like any other query.

    Thanks,
    - Kyle
    On Wed, Jun 12, 2013 at 4:55 PM, Kyle Vigen wrote:
    Hi Ben,

    In Impala 1.0.1 that message should only show up in the logs if an
    invalid query is issued (ex. one with invalid syntax). If it's showing
    up after valid queries then it's a bug and we should investigate more.
    If it's only happening after invalid queries then you can safely
    ignore.

    Thanks,
    - Kyle
    On Wed, Jun 12, 2013 at 4:32 PM, Benjamin Kim wrote:
    Hi Kyle,

    We are using Impala 1.0.1. So, this message can be safely ignored. Correct?

    Thanks,
    Ben

    On Wednesday, June 12, 2013 4:28:47 PM UTC-7, Kyle Vigen wrote:

    Hi Ben,

    What version of Impala are you running? Prior to 1.0.1, certain Impala
    queries were missing profile information needed by CM which caused the
    service monitor to log a warning that the profile was corrupt (the
    stack trace you're seeing).

    If you're using CM for Impala query monitoring we recommend that you
    upgrade to Impala 1.0.1. Otherwise you can safely ignore the stack
    trace.

    - Kyle

    On Wed, Jun 12, 2013 at 3:31 PM, Benjamin Kim wrote:
    I was viewing the Events in Cloudera Manager 4.6 and saw an entry marked
    "IMPORTANT Corrupt executing impala profile". What does this mean? I
    have
    included the stack trace below.

    com.cloudera.cmon.ImpalaCorruptProfileException: Profile queryId is too
    short: Query
    at

    com.cloudera.cmf.model.impala.ImpalaRuntimeProfileTree.getQueryId(ImpalaRuntimeProfileTree.java:124)
    at

    com.cloudera.cmon.ImpalaRuntimeProfileUtils.generateImpalaQueryFromProfile(ImpalaRuntimeProfileUtils.java:153)
    at

    com.cloudera.cmon.firehose.ImpalaRuntimeProfile.<init>(ImpalaRuntimeProfile.java:85)
    at

    com.cloudera.cmon.firehose.ImpalaQueryManager.updateExecutingQueries(ImpalaQueryManager.java:283)
    at

    com.cloudera.cmon.firehose.ImpalaQueryManager.updateQueries(ImpalaQueryManager.java:263)
    at

    com.cloudera.cmon.firehose.RoleStageReceiver.processImpalaUpdate(RoleStageReceiver.java:196)
    at

    com.cloudera.cmon.firehose.RoleStageReceiver.receiveItem(RoleStageReceiver.java:72)
    at

    com.cloudera.cmon.firehose.RoleStageReceiver.receiveItem(RoleStageReceiver.java:38)
    at
    com.cloudera.cmon.pipeline.PipelineStage.driver(PipelineStage.java:273)
    at
    com.cloudera.cmon.pipeline.PipelineStage$2.run(PipelineStage.java:149)
    at

    java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at

    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)

    Thanks,
    Ben
  • Benjamin Kim at Jun 13, 2013 at 5:03 pm
    Kyle,

    I just installed CM 4.6 and Impala 1.0.1 over the weekend onto our Dev
    cluster. The only statement that I can recall running was "show tables;".
    I'll still ignore it for now.

    Thanks,
    Ben
    On Wednesday, June 12, 2013 6:25:38 PM UTC-7, Kyle Vigen wrote:

    Hi Ben,

    One thing I forgot to mention is that we do plan on improving our
    handling of this in the future. Even queries with syntax errors
    shouldn't generate that stack trace. We want to be able to monitor
    them like any other query.

    Thanks,
    - Kyle
    On Wed, Jun 12, 2013 at 4:55 PM, Kyle Vigen wrote:
    Hi Ben,

    In Impala 1.0.1 that message should only show up in the logs if an
    invalid query is issued (ex. one with invalid syntax). If it's showing
    up after valid queries then it's a bug and we should investigate more.
    If it's only happening after invalid queries then you can safely
    ignore.

    Thanks,
    - Kyle
    On Wed, Jun 12, 2013 at 4:32 PM, Benjamin Kim wrote:
    Hi Kyle,

    We are using Impala 1.0.1. So, this message can be safely ignored.
    Correct?
    Thanks,
    Ben

    On Wednesday, June 12, 2013 4:28:47 PM UTC-7, Kyle Vigen wrote:

    Hi Ben,

    What version of Impala are you running? Prior to 1.0.1, certain Impala
    queries were missing profile information needed by CM which caused the
    service monitor to log a warning that the profile was corrupt (the
    stack trace you're seeing).

    If you're using CM for Impala query monitoring we recommend that you
    upgrade to Impala 1.0.1. Otherwise you can safely ignore the stack
    trace.

    - Kyle

    On Wed, Jun 12, 2013 at 3:31 PM, Benjamin Kim wrote:
    I was viewing the Events in Cloudera Manager 4.6 and saw an entry
    marked
    "IMPORTANT Corrupt executing impala profile". What does this mean? I
    have
    included the stack trace below.

    com.cloudera.cmon.ImpalaCorruptProfileException: Profile queryId is
    too
    short: Query
    at
    com.cloudera.cmf.model.impala.ImpalaRuntimeProfileTree.getQueryId(ImpalaRuntimeProfileTree.java:124)
    at
    com.cloudera.cmon.ImpalaRuntimeProfileUtils.generateImpalaQueryFromProfile(ImpalaRuntimeProfileUtils.java:153)
    at
    com.cloudera.cmon.firehose.ImpalaRuntimeProfile.<init>(ImpalaRuntimeProfile.java:85)
    at
    com.cloudera.cmon.firehose.ImpalaQueryManager.updateExecutingQueries(ImpalaQueryManager.java:283)
    at
    com.cloudera.cmon.firehose.ImpalaQueryManager.updateQueries(ImpalaQueryManager.java:263)
    at
    com.cloudera.cmon.firehose.RoleStageReceiver.processImpalaUpdate(RoleStageReceiver.java:196)
    at
    com.cloudera.cmon.firehose.RoleStageReceiver.receiveItem(RoleStageReceiver.java:72)
    at
    com.cloudera.cmon.firehose.RoleStageReceiver.receiveItem(RoleStageReceiver.java:38)
    at
    com.cloudera.cmon.pipeline.PipelineStage.driver(PipelineStage.java:273)
    at
    com.cloudera.cmon.pipeline.PipelineStage$2.run(PipelineStage.java:149)
    at
    java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)

    Thanks,
    Ben

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedJun 12, '13 at 10:31p
activeJun 13, '13 at 5:03p
posts6
users2
websitecloudera.com
irc#hadoop

2 users in discussion

Kyle Vigen: 3 posts Benjamin Kim: 3 posts

People

Translate

site design / logo © 2022 Grokbase