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

Posted to commits@oodt.apache.org by "Chris A. Mattmann (Updated) (JIRA)" <ji...@apache.org> on 2012/04/01 00:30:43 UTC

[jira] [Updated] (OODT-314) It is possible for 2 jobs submitted at very similar times to be assigned the same ID by the MemoryJobRepository

     [ https://issues.apache.org/jira/browse/OODT-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann updated OODT-314:
-----------------------------------

    Fix Version/s:     (was: 0.4)
                   0.5

- push to 0.5
                
> It is possible for 2 jobs submitted at very similar times to be assigned the same ID by the MemoryJobRepository
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: OODT-314
>                 URL: https://issues.apache.org/jira/browse/OODT-314
>             Project: OODT
>          Issue Type: Bug
>          Components: resource manager
>            Reporter: Gabe Resneck
>            Assignee: Gabe Resneck
>             Fix For: 0.5
>
>         Attachments: TestFifoMappedJobQueue.java
>
>
> Currently, when a job is added to a MemoryJobRepository, it helps to ensure no duplicates by assigning a new ID to that job based upon the current time.  However, it is still possible for jobs to be assigned the same ID if they are submitted at very similar times.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira