ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yakov Zhdanov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-75) Revisit node stop procedure and busy locking
Date Wed, 24 Dec 2014 13:06:13 GMT

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

Yakov Zhdanov updated IGNITE-75:
--------------------------------
    Description: 
# Have 64 or 128 threads preforming operations from public API (e.g. cache.put(..))
# Have 1 thread to stop current node. Stop will most likely hang due to busy lock on kernal
gateway (since it is busy locked by threads performing puts)

Comments:
# Why we have multiple busy locks instead of using one from KernalGateway?
# All ongoing user initiated operations should fail, no new allowed and then stop procedure
should proceed.
# One can use {{GridCacheStopSelfTest}} to debug this, but create a new test which should
involve 2 or more nodes.

  was:
# Have 64 or 128 threads preforming operations from public API (e.g. cache.put(..))
# Have 1 thread to stop current node. Stop will most likely hang due to busy lock on kernal
gateway (since it is busy locked by threads performing puts)

Comments:
# Why we have multiple busy locks instead of using one from KernalGateway?
# All ongoing user initiated operations should fail, no new allowed and then stop procedure
should proceed.


> Revisit node stop procedure and busy locking
> --------------------------------------------
>
>                 Key: IGNITE-75
>                 URL: https://issues.apache.org/jira/browse/IGNITE-75
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Yakov Zhdanov
>
> # Have 64 or 128 threads preforming operations from public API (e.g. cache.put(..))
> # Have 1 thread to stop current node. Stop will most likely hang due to busy lock on
kernal gateway (since it is busy locked by threads performing puts)
> Comments:
> # Why we have multiple busy locks instead of using one from KernalGateway?
> # All ongoing user initiated operations should fail, no new allowed and then stop procedure
should proceed.
> # One can use {{GridCacheStopSelfTest}} to debug this, but create a new test which should
involve 2 or more nodes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message