[GitHub] ignite pull request #907: Ignite 3513

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #907: Ignite 3513

andrey-kuznetsov
GitHub user EdShangGG opened a pull request:

    https://github.com/apache/ignite/pull/907

    Ignite 3513

   

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-3513

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/907.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #907
   
----
commit 8ea4d6a9a489cdfaa276cd93d4e504b6cdb1bbfe
Author: EdShangGG <[hidden email]>
Date:   2016-07-25T11:45:16Z

    ignite-3513
   
    (cherry picked from commit f3261b50f17848339b141a900f8c97a61bdbc7ca)

commit 4642d79a9112c60b96f0f2e90cd66cd561334886
Author: EdShangGG <[hidden email]>
Date:   2016-07-25T18:18:16Z

    IGNITE-3513 Cleanup worker is placed in the Thread's waiting queue using Thread.sleep method
    -adding benchmark

commit 230f0ee1c779ddd2136f7cbbbc4f10f5a2614c1e
Author: EdShangGG <[hidden email]>
Date:   2016-07-27T09:34:31Z

    IGNITE-3513 Cleanup worker is placed in the Thread's waiting queue using Thread.sleep method
    -new benchmark
    -extracting wait strategy

commit beb7a3b55acb491f7b601c441a0c8f03aabfeba7
Author: EdShangGG <[hidden email]>
Date:   2016-07-28T13:49:23Z

    IGNITE-3513 Cleanup worker is placed in the Thread's waiting queue using Thread.sleep method
    -test

commit cfaca48c3f505e2d8e466937369df128b77e6244
Author: EdShangGG <[hidden email]>
Date:   2016-07-28T14:57:35Z

    IGNITE-3513 Cleanup worker is placed in the Thread's waiting queue using Thread.sleep method
    -ready for review version

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---