Skip to Main Content

Integration

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

write-requeue-threshold / write-behind doesn't limit the number of requeued entries

Alessandro Affinito-OracleApr 20 2017 — edited May 22 2017

Hi

I've seen other questions about this topic are quite updated so I repost it:

What does this queue limit?

<write-requeue-threshold>      Specifies the maximum size of the write-behind queue for which failed cachestore write operations are requeued. The purpose of this setting is to prevent flooding of the write-behind queue with failed cachestore operations. This can happened in situations where a large number of successive write operations fail.

I've done a series of test, on the same cache server trying to store on a table that doesn't exist, like:

  • running two clients doing two different puts with different keys
  • running a single client with multiple puts on different keys
  • a mix of the above

The result is always the same: no failing request of the cache-store is discarded from the queue.

Even if my threshold is 1, 5 different storing transactions on 5 respective different keys are re-tried every minute.

Should we just open an SR?

This is my cache-config.xml

<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>ALEXCACHE_*</cache-name>

            <scheme-name>alexCache-distributed-dynamic</scheme-name>

            <init-params>

                <init-param>

                    <param-name>delegate-cache-name</param-name>

                    <param-value>ALEXCACHE_*</param-value>

                </init-param>

            </init-params>

        </cache-mapping>

    </caching-scheme-mapping>

   

    <caching-schemes>

        <near-scheme>

            <scheme-name>alexCache-distributed-dynamic</scheme-name>

           

            <front-scheme>

                <local-scheme>

                    <high-units>1000</high-units>

                </local-scheme>

            </front-scheme>

           

            <back-scheme>

                <distributed-scheme>

                    <scheme-ref>alexCache-distributed-back</scheme-ref>

                </distributed-scheme>

            </back-scheme>

           

            <invalidation-strategy>all</invalidation-strategy>

            <autostart>true</autostart>

        </near-scheme>

       

        <distributed-scheme>

            <scheme-name>alexCache-distributed-back</scheme-name>

            <service-name>DistributedCache</service-name>

            <backing-map-scheme>

                <read-write-backing-map-scheme>

                    <internal-cache-scheme>

                        <local-scheme/>

                    </internal-cache-scheme>

                    <cachestore-scheme>

                        <class-scheme>

                            <class-name>clients.Team_CS</class-name>

                            <init-params>

                                <init-param>

                                    <param-name>Java.lang.String</param-name>

                                    <param-value>{cache-name}</param-value>

                                </init-param>

                            </init-params>

                        </class-scheme>

                    </cachestore-scheme>

                   

                    <write-delay>10s</write-delay>

                    <write-requeue-threshold>1</write-requeue-threshold>                   

                </read-write-backing-map-scheme>

            </backing-map-scheme>

           

            <autostart>true</autostart>

        </distributed-scheme>

       

    </caching-schemes>

</cache-config>

This post has been answered by Shyam Radhakrishnan-Oracle on May 22 2017
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jun 19 2017
Added on Apr 20 2017
3 comments
698 views