[infinispan-issues] [JBoss JIRA] Commented: (ISPN-186) Smart L1 cache invalidation

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577488#comment-12577488 ] 

Bela Ban commented on ISPN-186:
-------------------------------

Additional logic that may make this better:
- If the transport is multicast capable and we have more than N/3 (or whatever subset is picked) members to send the invalidation to --> use a multicast
- Else use several unicasts
- Note that daisychaining might be helpful in sending 'multicasts' in TCP stacks

> Smart L1 cache invalidation
> ---------------------------
>
>                 Key: ISPN-186
>                 URL: https://issues.jboss.org/browse/ISPN-186
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Distributed Cache
>            Reporter: Manik Surtani
>            Assignee: Pete Muir
>              Labels: l1
>             Fix For: 5.0.0.BETA1, 5.0.0.Final
>
>
> Need to build a mechanism in which L1 invalidation is NOT multicast, but instead is unicast _if necessary_ to specific nodes that may have cached a given entry.  This can be detected by maintaining a list of nodes who have requested a key via a remote get, but this would need to be relayed by all data owners.
> Benefits would be performance by removing unnecessary invalidation where this is not needed, and by reducing noise in network stacks of most nodes.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira