[
https://issues.apache.org/jira/browse/UIMA-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor reassigned UIMA-838:
-----------------------------------
Assignee: Marshall Schor
> Incorrect support for process CAS error threshold count and threshold window
> -----------------------------------------------------------------------------
>
> Key: UIMA-838
> URL: https://issues.apache.org/jira/browse/UIMA-838
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Burn Lewis
> Assignee: Marshall Schor
> Fix For: 2.2.2S
>
> Attachments: UIMA-838-docs.patch, UIMA-838-docs2.patch,
> UIMA-838-fix2.patch, UIMA-838-test.patch, UIMA-838.patch
>
>
> The thresholdAction should be taken when the number of CAS errors reaches the
> thresholdCount value within the last thresholdWindow CASes. A
> thresholdWindow of 0 means an infinite window, so the action is taken when
> the total number of errors reaches the thresholdCount. A thresholdCount of 0
> means an infinite limit, errors are ignored. A thresholdCount of 1 means
> that the first error triggers the action, hence the action must be taken when
> the threshold is REACHED, not exceeded as stated in the current docs.
> (Although thresholds usually apply when exceeded, making the thresholdCount
> be the number permitted would require using a value such as -1 for no
> threshold, in contrast to our use of 0 to mean no timeout and no window)
> It should be an error to specify a (non-zero) thresholdWindow that is smaller
> than the thresholdCount ... an impossible situation.
> Note that if thresholdCount = 1 the thresholdWindow value is irrelevant, and
> if thresholdCount = thresholdWindow the action is taken when that many
> consecutive errors occur.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
