开发者社区> 问答> 正文

SchedulerX中我创建应用的时候报这个错,是什么原因呀?

SchedulerX中我创建应用的时候报这个错,是什么原因呀? {"requestUrl":"https://schedulerx-test.console.aliyun.com/app/registerApp.json","message":"com.aliyun.openservices.log.exception.LogException: project schedulerx-public, logstore count quota exceed","method":"post","params":{},"requestData":"appName=merach-sun-data-yearly-report&version=2&enableLog=true&groupId=merach-sun-data-yearly-report&metricsThresholdJson=eyJsb2FkNSI6IiIsImhlYXA1VXNhZ2UiOiIiLCJkaXNrVXNhZ2UiOiIifQ%3D%3D&alarmJson=eyJza2lwQnVzeVN3aXRjaCI6ZmFsc2V9&maxConcurrency=-1&appType=1&contact=%5B%7B%22userName%22%3A%22%E5%B9%B4%E5%BA%A6%E6%8A%A5%E5%91%8A%E6%9C%BA%E5%99%A8%E4%BA%BA%22%2C%22userPhone%22%3A%22%22%2C%22userMail%22%3A%22%22%2C%22ding%22%3A%22https%3A%2F%2Foapi.dingtalk.com%2Frobot%2Fsend%3Faccess_token%3D07e951feaf8555e8594dfe4d6e80bbb68e1cb5b9051a1cdfbcb2aeeff8b86d8c%22%2C%22wechat%22%3A%22%22%7D%5D&monitorConfig=%7B%22sendChannel%22%3A%22ding%22%2C%22alarmType%22%3A%22CustomContacts%22%7D&autoScale=false&regionId=cn-test","responseData":{},"traceId":"","requestId":"910442453313125406920096513815","code":1002,"headers":{"X-XSRF-TOKEN":"cb27a14c-d46f-402c-ad85-3fa1150eec48","schedulerx-namespace":"4437f616-7bb6-4e19-926f-67d21029ab39","schedulerx-namespace-source":"schedulerx","schedulerx-regionid":"cn-test"}}

展开
收起
fuxixi 2022-12-26 17:48:51 394 0
1 条回答
写回答
取消 提交回答
  • java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
    at org.apache.flink.runtime.scheduler.SchedulerNG.lambda$createApplication$4(SchedulerNG.java:661)
    at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:615)
    at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:609)
    at java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:1902)
    at org.apache.flink.runtime.scheduler.SchedulerNG.createApplication(SchedulerNG.java:659)
    at org.apache.flink.runtime.scheduler.SchedulerNG.lambda$schedule$0(SchedulerNG.java:275)
    at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:615)
    at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:609)
    at java.util.concurrent.CompletableFuture.thenApply(CompletableFuture.java:1902)
    at org.apache.flink.runtime.scheduler.SchedulerNG.schedule(SchedulerNG.java:272)
    at org.apache.flink.runtime.jobmaster.JobMaster.lambda$submit$0(JobMaster.java:434)
    at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:615)
    at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:609)
    at java.util.concurrent.CompletableFuture.thenAccept(CompletableFuture.java:1879)
    ...
    Caused by: java.lang.reflect.InvocationTargetException
    at java.lang.reflect.Method.invoke(Method.java:573)
    at org.apache.flink.runtime.scheduler.SchedulerNG.lambda$createApplication$4(SchedulerNG.java:661)
    ... 14 more
    Caused by: org.apache.flink.util.FlinkException: Could not instantiate application master service.
    at org.apache.flink.runtime.jobmaster.JobManagerRunner.startApplicationMasterService(JobManagerRunner.java:651)
    at org.apache.flink.runtime.jobmaster.JobManagerRunner.initialize(JobManagerRunner.java:253)
    ... 16 more
    Caused by: org.apache.flink.runtime.concurrent.ScheduledExecutorEStatusException: The scheduled task has been cancelled or timed out.
    at org.apache.flink.runtime.concurrent.ScheduledExecutorEStatusException.apply(ScheduledExecutorEStatusException.java:57)
    at org.apache.flink.runtime.concurrent.ScheduledExecutorEStatusException.apply(ScheduledExecutorEStatusException.java:28)
    at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:625)
    ... 19 more
    此错误表明在创建应用程序时,无法实例化应用程序主服务。应用程序主服务对于提交和执行作业至关重要。

    错误的根本原因是 org.apache.flink.runtime.concurrent.ScheduledExecutorEStatusException,这表明计划的任务已被取消或超时。这通常与 java.lang.reflect.InvocationTargetException 一起发生,这表明在调用反射方法时出现问题。

    导致此问题的可能原因包括:

    类路径问题:应用程序主服务类可能未包含在作业的类路径中。确保将应用程序主服务类及其依赖项打包到作业的 JAR 文件中。
    反射配置问题:Flink 无法反射实例化应用程序主服务类。检查应用程序主服务类的构造函数是否具有公共访问权限,并且没有抛出任何异常。
    并发问题:多个线程可能同时尝试创建应用程序主服务,导致竞争条件。检查应用程序提交逻辑以确保它线程安全。
    为了解决此问题,请尝试以下步骤:

    检查作业的类路径,确保应用程序主服务类及其依赖项已包含在其中。
    审查应用程序主服务类的构造函数,确保它具有公共访问权限,并且没有抛出任何异常。
    检查应用程序提交逻辑以确保它线程安全。
    如果问题仍然存在,请检查 Flink 和 YARN 日志以获取更多详细信息。

    2024-02-27 17:47:41
    赞同 展开评论 打赏
来源圈子
更多
收录在圈子:
问答排行榜
最热
最新

相关电子书

更多
低代码开发师(初级)实战教程 立即下载
冬季实战营第三期:MySQL数据库进阶实战 立即下载
阿里巴巴DevOps 最佳实践手册 立即下载