[ 
https://issues.apache.org/jira/browse/GOBBLIN-1901?focusedWorklogId=879593&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-879593
 ]

ASF GitHub Bot logged work on GOBBLIN-1901:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 09/Sep/23 00:19
            Start Date: 09/Sep/23 00:19
    Worklog Time Spent: 10m 
      Work Description: umustafi opened a new pull request, #3765:
URL: https://github.com/apache/gobblin/pull/3765

   Dear Gobblin maintainers,
   
   Please accept this PR. I understand that it will not be reviewed until I 
have checked off all the steps below!
   
   
   ### JIRA
   - [X] My PR addresses the following [Gobblin 
JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references 
them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
       - https://issues.apache.org/jira/browse/GOBBLIN-1901 
   
   
   ### Description
   - [X] Here are some details about my PR, including screenshots (if 
applicable):
   Creates MysqlMultiActiveLeaseAribterTestingDecorator class used to model 
scenarios where a lease owner fails to complete a lease successfully 
intermittently (representing a variety of slowness or failure cases that can 
result on the participant side, network connectivity, or database).
   It will fail on calls to {@link 
MysqlMultiActiveLeaseArbiter.recordLeaseSuccess()} where a deterministic 
function of the lease obtained timestamp matches a bitmask of the host. 
Ideally, each participant should fail on different calls (with limited overlap 
if we want to test that). See java doc for more details. 
   
   ### Tests
   - [X] My PR adds the following unit tests __OR__ does not need testing for 
this extremely good reason:
   WIP (will add in second iteration once methodology is agreed upon)
   
   ### Commits
   - [X] My commits all reference JIRA issues in their subject lines, and I 
have squashed multiple commits if they address the same issue. In addition, my 
commits follow the guidelines from "[How to write a good git commit 
message](http://chris.beams.io/posts/git-commit/)":
       1. Subject is separated from body by a blank line
       2. Subject is limited to 50 characters
       3. Subject does not end with a period
       4. Subject uses the imperative mood ("add", not "adding")
       5. Body wraps at 72 characters
       6. Body explains "what" and "why", not "how"
   
   




Issue Time Tracking
-------------------

            Worklog Id:     (was: 879593)
    Remaining Estimate: 0h
            Time Spent: 10m

> Define MultiActiveLeaseArbiter Decorator to Model Failed Lease Completion
> -------------------------------------------------------------------------
>
>                 Key: GOBBLIN-1901
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1901
>             Project: Apache Gobblin
>          Issue Type: New Feature
>          Components: gobblin-service
>            Reporter: Urmi Mustafi
>            Assignee: Abhishek Tiwari
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Creates MysqlMultiActiveLeaseAribterTestingDecorator class used to model 
> scenarios where a lease owner fails to complete a lease successfully 
> intermittently (representing a variety of slowness or failure cases that can 
> result on the participant side, network connectivity, or database).
> It will fail on calls to \{@link 
> MysqlMultiActiveLeaseArbiter.recordLeaseSuccess()} where a deterministic 
> function of the lease obtained timestamp matches a bitmask of the host. 
> Ideally, each participant should fail on different calls (with limited 
> overlap if we want to test that). See java doc for more details. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to