You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@aurora.apache.org by "Bill Farner (JIRA)" <ji...@apache.org> on 2015/06/24 18:20:05 UTC

[jira] [Commented] (AURORA-1369) Scheduler warns about unoptimized Operation SAVE_JOB_INSTANCE_UPDATE_EVENT

    [ https://issues.apache.org/jira/browse/AURORA-1369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14599668#comment-14599668 ] 

Bill Farner commented on AURORA-1369:
-------------------------------------

Thanks for filing!  I think it would be reasonable to kill the log statement, or add a no-op case for that operation type.

> Scheduler warns about unoptimized Operation SAVE_JOB_INSTANCE_UPDATE_EVENT
> --------------------------------------------------------------------------
>
>                 Key: AURORA-1369
>                 URL: https://issues.apache.org/jira/browse/AURORA-1369
>             Project: Aurora
>          Issue Type: Story
>          Components: Scheduler
>    Affects Versions: 0.8.0
>            Reporter: Stephan Erb
>            Priority: Minor
>
> The aurora scheduler warns about a storage operation which is not coalesced. We are seeing hundreds of messages in the form:
> {code}
> W0622 15:28:32.962 THREAD3134 org.apache.aurora.scheduler.storage.log.StreamManagerImpl$StreamTransactionImpl.coalesce: Unoptimized op: SAVE_JOB_INSTANCE_UPDATE_EVENT
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)