firebase / firebase/firebase-admin-java

9.0.0 to 9.3.0 sendMulticastAsync vs sendEachForMulticastAsync. Server crashes when sending too many pushes

未关闭
#1,001 4 条评论 0 个 reaction 已指派 1 人 已被 @Doris-Ge 认领 在 GitHub 查看
api: messaging
主要语言
Java
星标
620
派生
305
平均合并
3 小时 23 分钟
30 天内合并 PR
1

描述

### [REQUIRED] Step 2: Describe your environment

* Operating System version: debian / grails / groovy / java 11
* Firebase SDK version: 9.3.0
* Library version: _____
* Firebase Product: admin

### [REQUIRED] Step 3: Describe the problem
We switched out the firebase admin version from 9.0.0 to 9.3.0 yesterday. Sending out a few pushes works fine, but we sometimes send out a few millions in a "batch". There never were issues with the old sendMulticastAsync

ApiFuture apiFuture = FirebaseMessaging.getInstance().sendEachForMulticastAsync(multicastMessage)

apiFuture.addListener({
def batchResponse = apiFuture.get()
if (batchResponse != null && batchResponse.failureCount > 0) {
for (int i = 0; i < batchResponse.responses.size(); i++) {
def response = batchResponse.responses.get(i)
if (response != null && !response.successful && response.exception != null && (
(ErrorCode.NOT_FOUND == response.exception.errorCode && MessagingErrorCode.UNREGISTERED == response.exception.messagingErrorCode) ||
(ErrorCode.INVALID_ARGUMENT == response.exception.errorCode && MessagingErrorCode.INVALID_ARGUMENT == response.exception.messagingErrorCode))) {
UidRemovalJob.removalCandidates.add(new UidRemovalCandidate(phoneId: tokenList[i], os: 2))
}
}
}
}, executorServiceAndroidResponses)

Does this need to be switched to another implementation?

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。