[jboss-jira] [JBoss JIRA] Commented: (JGRP-1147) TP: make logical_addr_cache's timeout configurable

[Bela Ban (JIRA)]

    [ https://jira.jboss.org/jira/browse/JGRP-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12523054#action_12523054 ] 

Bela Ban commented on JGRP-1147:
--------------------------------

OK, I've added 2 new properties to TP:

@Property(description="Max number of elements in the logical address cache before eviction starts")
    protected int logical_addr_cache_max_size=20;

@Property(description="Time (in ms) after which entries in the logical address cache marked as removable are removed")
   protected long logical_addr_cache_expiration=120000;


The latter starts a timer, which will go off every logical_addr_cache_expiration milliseconds and evict elements marked as removable which are older than logical_addr_cache_expiration ms.

You could now either leave logical_addr_cache_expiration at its default of 120000 and purge the cache manually, by calling TP.evictLogicalAddressCache(), or you could reduce the value of logical_addr_cache_expiration, so expired elements are remove faster

> TP: make logical_addr_cache's timeout configurable
> --------------------------------------------------
>
>                 Key: JGRP-1147
>                 URL: https://jira.jboss.org/jira/browse/JGRP-1147
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>            Priority: Minor
>             Fix For: 2.10
>
>
> [email Maher Al Kilani]
> I am using jgroups lib. I noticed that when one of the nodes is down, the
> lazyRemovalCache class tags it removable and all the nodes stay in
> logical_addr_cache (in TP.java). So when sending a message we are actually
> sending to all the removable and the alive ones. How can configure the
> lazyRemovalCache class to not tag as removable but rather remove the dead
> nodes?
> Bela: let's make the timeout and max size configurable. Plus, possibly add a getter, so we can hard-flush the caceh programmatically

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira