[
https://issues.apache.org/jira/browse/OAK-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15013099#comment-15013099
]
Thomas Mueller commented on OAK-2843:
-------------------------------------
While testing, I found UDP did not work reliably on my machine. This was also
experienced by others (the unit test originally failed when using VPN; and for
Angela IPv6 doesn't seem to work). So I implemented a simple TCP broadcaster as
well, and tested this. I found out that the simple implementation slows down
startup quite a bit, because broadcasting is done synchronously right now. I
need to decouple broadcasting to another thread, and use a ring buffer, so that
if there are a lot of broadcasts, only as many are sent as there is actually
time to send, so that performance doesn't suffer.
> 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
> Fix For: 1.3.11
>
>
> 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)
