You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Thomas Mueller (JIRA)" <ji...@apache.org> on 2015/05/06 14:11:59 UTC

[jira] [Created] (OAK-2843) Broadcasting cache

Thomas Mueller created OAK-2843:
-----------------------------------

             Summary: Broadcasting cache
                 Key: OAK-2843
                 URL: https://issues.apache.org/jira/browse/OAK-2843
             Project: Jackrabbit Oak
          Issue Type: Improvement
          Components: mongomk
            Reporter: Thomas Mueller
            Assignee: Thomas Mueller


In a cluster environment, we could speed up reading if the cache(s) broadcast data to other instances. This would avoid bottlenecks at the storage layer (MongoDB, RDBMs).

The configuration metadata (IP addresses and ports of where to send data to, a unique identifier of the repository and the cluster nodes, possibly encryption key) rarely changes and can be stored in the same place as we store cluster metadata (cluster info collection). That way, in many cases no manual configuration is needed. We could use TCP/IP and / or UDP.



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