Forum Stats

  • 3,815,220 Users
  • 2,258,979 Discussions
  • 7,893,004 Comments

Discussions

Replicated cache data storage in proxy nodes.

1190653
1190653 Member Posts: 3
edited Aug 1, 2017 11:43PM in Coherence Support

We build a coherence cluster,has 2 distributed data nodes,2 replicated data nodes,2 proxy nodes,1 jmx node.

The client connects to the Proxy using the extend*client method.

After client put some data into replicated cache,we found replicated data both in replicated data nodes and proxy nodes .

We have 2 question:

1 When use replicated cache,how to avoid data storage in proxy nodes?

2 When use replicated cache,if data storage in proxy nodes,can data nodes not be configured?

Thanks.

Proxy config xml:

<?xml version="1.0"?>

<cache-config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xmlns="http://xmlns.oracle.com/coherence/coherence-cache-config"

xsi:schemaLocation="http://xmlns.oracle.com/coherence/coherence-cache-config coherence-cache-config.xsd">

<caching-scheme-mapping>

<cache-mapping>

<cache-name>repl-*</cache-name>

<scheme-name>bes-repl-scheme</scheme-name>

</cache-mapping>

</caching-scheme-mapping>

<caching-schemes>

<replicated-scheme>

<scheme-name>bes-repl-scheme</scheme-name>

<service-name>bes-replicated-service</service-name>

<backing-map-scheme>

<local-scheme>

<scheme-ref>unlimited-backing-map</scheme-ref>

</local-scheme>

</backing-map-scheme>

<autostart>true</autostart>

</replicated-scheme>

<proxy-scheme>

<service-name>bes-extend-service</service-name>

<thread-count>50</thread-count>

<acceptor-config>

<tcp-acceptor>

<local-address>

<address system-property="tangosol.coherence.extend.address">192.168.75.128</address>

<port system-property="tangosol.coherence.extend.port">12001</port>

</local-address>

</tcp-acceptor>

<outgoing-message-handler>

<heartbeat-interval>60s</heartbeat-interval>

<heartbeat-timeout>60s</heartbeat-timeout>

<request-timeout>5s</request-timeout>

</outgoing-message-handler>

</acceptor-config>

<proxy-config>

<cache-service-proxy>

<enabled>true</enabled>

<lock-enabled>true</lock-enabled>

</cache-service-proxy>

<invocation-service-proxy>

<enabled>true</enabled>

</invocation-service-proxy>

</proxy-config>

<autostart>true</autostart>

</proxy-scheme>

</caching-schemes>

</cache-config>

Answers

  • Tmiddlet-Oracle
    Tmiddlet-Oracle Member Posts: 125
    edited Aug 1, 2017 11:43PM

    Hi.

    A replicated scheme means exactly that, all data is replicated to all nodes, that includes nodes where proxy servers are running.

    What is your use case for replicated cache? Its recommended to use distributed cache with near cache nowadays.

    What version are you using?

    Thanks

    Tim

This discussion has been closed.