Metaspace is unavailable for any requests till member_timeout is reached when a Leech or a Seeder has been stopped.

Metaspace is unavailable for any requests till member_timeout is reached when a Leech or a Seeder has been stopped.

book

Article ID: KB0093087

calendar_today

Updated On:

Products Versions
TIBCO ActiveSpaces -
Not Applicable -

Description

Description:
Metaspace is unavailable for any requests till member_timeout is reached when a Leech or a Seeder (as-agent) has been stopped.
Symptoms:
Metaspace is unavailable for member_timeout when Leech or Seeder has been stopped. 

Cause:
This behavior is by design. When a member drops, ActiveSpaces suspends the metaspace (cluster) due to membership changes until it is certain that the member is truly gone. This is to ensure transient network failures do not cause members to be evicted too early and allows ActiveSpaces to reconnect if possible. The tradeoff is that waiting to evict will affect the timeliness of operations to complete.

One way to avoid the pause is to have the client leave the metaspace gracefully via Metaspace.closeAll(). Leaving gracefully tells ActiveSpaces that the member is removing itself from the cluster.

Note: When stop as-agent (Ctrl-c) Memberspace.closeAll() is not handled today.

Issue/Introduction

Metaspace is unavailable for any requests till member_timeout is reached when a Leech or a Seeder has been stopped.

Resolution

To avoid the delay execute the following as-admin command to leave the member from metaspace before stopping the agent.

execute on member '<membername>' leave metaspace