[ https://issues.apache.org/jira/browse/OOZIE-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262517#comment-16262517 ]
Andras Piros commented on OOZIE-3132: ------------------------------------- [~gezapeti] there are some new {{TRACE}} level logging messages introduced by the patch when there are changes to {{SLACalculatorMemory#slaMap}}: * in case a new {{SLACalcStatus}} is added * in case an existing {{SLACalcStatus}} is updated * in case an existing {{SLACalcStatus}} is removed * in case no existing {{SLACalcStatus}} is found while trying to remove Apart from that, there are multiple places of {{INFO}} and {{TRACE}} levels. While debugging this class in a production system, best is to set its log level to {{TRACE}}. > Instrument SLACalculatorMemory > ------------------------------ > > Key: OOZIE-3132 > URL: https://issues.apache.org/jira/browse/OOZIE-3132 > Project: Oozie > Issue Type: Improvement > Components: core > Affects Versions: 4.3.0 > Reporter: Andras Piros > Assignee: Andras Piros > Fix For: 5.0.0b1 > > Attachments: OOZIE-3132.001.patch, OOZIE-3132.002.patch > > > When there are lots of {{WorkflowJobBean}} and {{CoordinatorJobBean}} > instances that have to be followed up on creating {{SLASummaryBean}} > instances, following can occur: > * we set {{oozie.sla.service.SLAService.capacity}} to a sane value like > {{10000}} to preserve heap consumption > * {{SLACalculatorMemory#addRegistration()}} and > {{SLACalculatorMemory#updateRegistration}} would: > ** either emit {{TRACE}} level logs like {{SLA Registration Event - Job:}} > showing the add / update of {{SLARegistrationBean}} was successful > ** or emit {{ERROR}} level logs like {{SLACalculator memory capacity reached. > Cannot add or update new SLA Registration entry for job}} showing the add / > update of {{SLARegistrationBean}} was not successful > Since sometimes stale or already processed {{SLAEvent}} entries from > {{SLACalculatorMemory#slaMap}} get removed, it's pretty hard to say what is > its the actual size - that is, whether the next add or update command will > succeed > We need an {{Instrumentation.Counter}} instance that gets incremented when > there is an {{SLACalculatorMemory#slaMap#put()}} with a new entry added, and > gets decremented when there happens a {{SLACalculatorMemory#slaMap#remove()}} > with an existing entry removed. This counter will be automatically present > within REST interface, and Oozie client. -- This message was sent by Atlassian JIRA (v6.4.14#64029)