Bug 856101
Summary: | Cache cannot shut down when disconnected | ||
---|---|---|---|
Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Radim Vansa <rvansa> |
Component: | Infinispan | Assignee: | Tristan Tarrant <ttarrant> |
Status: | CLOSED NOTABUG | QA Contact: | Martin Gencur <mgencur> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.0.1 | CC: | gsheldon, jdg-bugs, myarboro |
Target Milestone: | --- | ||
Target Release: | 6.1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
When the cache is disconnected from the network, it may become impossible to shut down. As a result, graceful node shutdown not possible. As a workaround, the process can be killed manually. The node may continue to run if it is not manually killed.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2012-09-13 14:31:05 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Radim Vansa
2012-09-11 08:22:49 UTC
Radim Vansa <rvansa> made a comment on jira ISPN-2283 I've found that this can occur not only when the node is disconnected but also when the whole cluster is shutting down and therefore the cache view is changed after the node has shut down. Radim Vansa <rvansa> made a comment on jira ISPN-2283 In fact the loop is not as infinite as I thought at first: DefaultCacheManager stops all caches and THEN stops the CacheViewManagerImpl. However, when stopping the cache, CacheViewManagerImpl.leave(cacheName) is called, which gets stuck in transport.invokeRemotely(request leave command), until a timeout in RSVP protocol which was set to 10 minutes. I'll check why the timeout is as high. Radim Vansa <rvansa> made a comment on jira ISPN-2283 In fact the loop is not as infinite as I thought at first: DefaultCacheManager stops all caches and THEN stops the CacheViewManagerImpl. However, when stopping the cache, CacheViewManagerImpl.leave(cacheName) is called, which gets stuck in transport.invokeRemotely(request leave command), until a transport.distributedSyncTimeout elapsed which was set to 10 minutes. I'll check why the timeout is as high. Radim Vansa <rvansa> made a comment on jira ISPN-2283 In fact the loop is not as infinite as I thought at first: DefaultCacheManager stops all caches and THEN stops the CacheViewManagerImpl. However, when stopping the cache, CacheViewManagerImpl.leave(cacheName) is called, which gets stuck in transport.invokeRemotely(request leave command), until a RSVP protocol timeout elapsed which was set to 10 minutes. Radim Vansa <rvansa> updated the status of jira ISPN-2283 to Resolved Radim Vansa <rvansa> made a comment on jira ISPN-2283 Not a bug - caused by improper configuration of RSVP protocol, was just waiting too long due to configuration. |