咖啡因:当AsyncLoader无法刷新时,请使用陈旧的值

我想将我的caffeine缓存配置为在加载程序无法刷新缓存时返回陈旧的结果。以下Kotlin代码演示了这种情况:

    @Test
    fun `completeble future`() = runBlocking {
        val cache = caffeine.newBuilder()
            .refreshAfterWrite(Duration.ofSeconds(1))
            .expireAfterWrite(Duration.ofSeconds(1))
            .buildAsync<String,String> { key: String,executor ->
                GlobalScope.future(executor.asCoroutineDispatcher()) {
                    throw Exception("== Error ==")
                }
            }

        cache.put("id",CompletableFuture.completedFuture("value"))

        delay(2000)

        assertEquals("value",cache.get("id").await())
    }

我希望该测试通过,但是却出现以下错误:

WARNING: Exception thrown during asynchronous load
java.lang.Exception: == Error ==
    at fsra.manager.TranslationmanagerImplTest$completeble future$1$cache$1$1.invokeSuspend(TranslationmanagerImplTest.kt:93)
    at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
    at kotlinx.coroutines.DispatchedTask.run(Dispatched.kt:241)
    at java.base/java.util.concurrent.ForkJoinTask$RunnableExecuteaction.exec(ForkJoinTask.java:1426)
    at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
    at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
    at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656)
    at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
    at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:177)




java.lang.Exception: == Error ==

    at fsra.manager.TranslationmanagerImplTest$completeble future$1$cache$1$1.invokeSuspend(TranslationmanagerImplTest.kt:93)
    at |b|b|b(Coroutine boundary.|b(|b)
    at fsra.manager.TranslationmanagerImplTest$completeble future$1.invokeSuspend(TranslationmanagerImplTest.kt:101)
Caused by: java.lang.Exception: == Error ==
    at fsra.manager.TranslationmanagerImplTest$completeble future$1$cache$1$1.invokeSuspend(TranslationmanagerImplTest.kt:93)
    at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
    at kotlinx.coroutines.DispatchedTask.run(Dispatched.kt:241)
    at java.base/java.util.concurrent.ForkJoinTask$RunnableExecuteaction.exec(ForkJoinTask.java:1426)
    at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
    at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
    at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656)
    at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
    at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:177)

我用Kotlin编写了代码,但我认为该问题与Kotlin协程无关。我想将caffeine配置为在刷新时不抛出,而是在缓存中返回之前的结果。

iCMS 回答:咖啡因:当AsyncLoader无法刷新时,请使用陈旧的值

高速缓存设置为在1秒后过期条目,并且测试等待2秒。然后,下一个调用将强制重新加载该新条目,因为该条目不可用,并且您引发了异常。

大于或等于到期时间时,刷新无效。小于时,该条目是陈旧但可用的,因此将其返回并异步重新加载。这是为了使流行项目(例如配置)可以保留在缓存中,而不会导致定期重新加载。不受欢迎的项目是在到期间隔内未访问的项目,可以将其逐出。如果刷新无法成功,则到期时间将开始,并且条目将被删除,因为到期时间设置为可以使用的最大时间。

更大的到期值(例如5秒)将通过您的测试。如果您的用例是定期盲目地重新加载所有缓存内容,则可以使用常规的MapScheduledExecutorService刷新它。

本文链接:https://www.f2er.com/2293490.html

大家都在问