【问题标题】:Ktor needs 1 hour(forever) to boot upKtor 需要 1 小时(永远)才能启动
【发布时间】:2021-08-24 10:02:41
【问题描述】:

我有一个 ktor 应用程序。当我在开发模式下运行它时,我工作得很好。我通过复制 gradle 应用程序插件提供的内容将其打包到 docker 映像中。这在我的本地机器 8 核上也可以正常工作。但现在奇怪的部分。当我在租用的 V-Server 上做完全相同的事情时,也像我的本地系统一样运行 Ubuntu-20.04,ktor 的速度非常慢。

docker-compose logs server:
server           | 2021-08-24 08:00:23.337 [main] INFO  ktor.application - Autoreload is disabled because the development mode is off.
server           | 2021-08-24 08:25:35.048 [main] INFO  ktor.application - Autoreload is disabled because the development mode is off.
server           | 2021-08-24 09:18:48.246 [main] INFO  c.e.e.s.TemplateStore - Starting to parse Sentences
server           | 2021-08-24 09:18:48.345 [main] INFO  c.e.e.s.TemplateStore - Finished parsing sentences
server           | 2021-08-24 09:18:48.346 [main] INFO  ktor.application - Responding at http://0.0.0.0:8080
server           | 2021-08-24 09:18:48.347 [main] INFO  ktor.application - Application started in 3193.32 seconds.
 Application started in 3193.32 seconds

源代码可以在这里找到https://github.com/1-alex98/whatisthat。它有一个 docker-compose.yml 定义正在启动的整个 docker 容器。 本地系统 32 GB 内存 + 8 个核心。 V-Server 4 gb Ram + 2 个核心(htop 显示大量资源是免费的)。

我正在寻找有关世界上可能导致这种行为的想法。或者调试它的方法。

更新: 似乎永远读取一个文件:

"main" #1 prio=5 os_prio=0 cpu=652.14ms elapsed=173.92s tid=0x00007f01d4016000 nid=0xe runnable  [0x00007f01dace6000]
   java.lang.Thread.State: RUNNABLE
    at java.io.FileInputStream.readBytes(java.base@11.0.12/Native Method)
    at java.io.FileInputStream.read(java.base@11.0.12/FileInputStream.java:279)
    at java.io.FilterInputStream.read(java.base@11.0.12/FilterInputStream.java:133)
    at sun.security.provider.NativePRNG$RandomIO.readFully(java.base@11.0.12/NativePRNG.java:424)
    at sun.security.provider.NativePRNG$RandomIO.ensureBufferValid(java.base@11.0.12/NativePRNG.java:526)
    at sun.security.provider.NativePRNG$RandomIO.implNextBytes(java.base@11.0.12/NativePRNG.java:545)
    - locked <0x00000000c7571158> (a java.lang.Object)
    at sun.security.provider.NativePRNG$Blocking.engineNextBytes(java.base@11.0.12/NativePRNG.java:268)
    at java.security.SecureRandom.nextBytes(java.base@11.0.12/SecureRandom.java:751)
    at kotlin.random.AbstractPlatformRandom.nextBytes(PlatformRandom.kt:47)
    at kotlin.random.Random.nextBytes(Random.kt:260)
    at com.example.routes.websocket.WebsocketRoutingKt.<clinit>(WebsocketRouting.kt:40)
    at com.example.plugins.RoutingKt$routing$1.invoke(Routing.kt:13)
    at com.example.plugins.RoutingKt$routing$1.invoke(Routing.kt:11)
    at io.ktor.routing.Routing$Feature.install(Routing.kt:106)
    at io.ktor.routing.Routing$Feature.install(Routing.kt:88)
    at io.ktor.application.ApplicationFeatureKt.install(ApplicationFeature.kt:68)
    at io.ktor.routing.RoutingKt.routing(Routing.kt:129)
    at com.example.plugins.RoutingKt.routing(Routing.kt:11)
    at com.example.ApplicationKt$main$1.invoke(Application.kt:18)
    at com.example.ApplicationKt$main$1.invoke(Application.kt:14)
    at io.ktor.server.engine.internal.CallableUtilsKt.executeModuleFunction(CallableUtils.kt:50)
    at io.ktor.server.engine.ApplicationEngineEnvironmentReloading$launchModuleByName$1.invoke(ApplicationEngineEnvironmentReloading.kt:317)
    at io.ktor.server.engine.ApplicationEngineEnvironmentReloading$launchModuleByName$1.invoke(ApplicationEngineEnvironmentReloading.kt:316)
    at io.ktor.server.engine.ApplicationEngineEnvironmentReloading.avoidingDoubleStartupFor(ApplicationEngineEnvironmentReloading.kt:341)
    at io.ktor.server.engine.ApplicationEngineEnvironmentReloading.launchModuleByName(ApplicationEngineEnvironmentReloading.kt:316)
    at io.ktor.server.engine.ApplicationEngineEnvironmentReloading.access$launchModuleByName(ApplicationEngineEnvironmentReloading.kt:30)
    at io.ktor.server.engine.ApplicationEngineEnvironmentReloading$instantiateAndConfigureApplication$1.invoke(ApplicationEngineEnvironmentReloading.kt:304)
    at io.ktor.server.engine.ApplicationEngineEnvironmentReloading$instantiateAndConfigureApplication$1.invoke(ApplicationEngineEnvironmentReloading.kt:295)
    at io.ktor.server.engine.ApplicationEngineEnvironmentReloading.avoidingDoubleStartup(ApplicationEngineEnvironmentReloading.kt:323)
    at io.ktor.server.engine.ApplicationEngineEnvironmentReloading.instantiateAndConfigureApplication(ApplicationEngineEnvironmentReloading.kt:295)
    at io.ktor.server.engine.ApplicationEngineEnvironmentReloading.createApplication(ApplicationEngineEnvironmentReloading.kt:136)
    at io.ktor.server.engine.ApplicationEngineEnvironmentReloading.start(ApplicationEngineEnvironmentReloading.kt:268)
    at io.ktor.server.netty.NettyApplicationEngine.start(NettyApplicationEngine.kt:174)
    at com.example.ApplicationKt.main(Application.kt:21)
    at com.example.ApplicationKt.main(Application.kt)

这是一个新租的服务器,但我猜它有问题

【问题讨论】:

  • 你能否通过限制容器docs.docker.com/config/containers/resource_constraints的资源来重现它?
  • 以后再试试好像是个好主意...
  • 在 0.5 秒内开始 :D @AlekseiTirman
  • 所以我尝试了docker-compose exec server bash,但这比正常时间要长很多
  • 似乎/dev/random 的阅读由于某种原因被阻止了。我发现了一个类似的问题jira.atlassian.com/browse/BAM-18285。您可以尝试那里描述的解决方法。

标签: docker kotlin ktor


【解决方案1】:

docker-compose 很慢,我的程序没有启动似乎是由于对 /dev/urandom 的输入不足(不够好)。安装https://github.com/smuellerDD/jitterentropy-rngd 解决了这个问题。

【讨论】:

    猜你喜欢
    • 2023-03-11
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2021-06-14
    • 1970-01-01
    • 2013-11-15
    • 2014-02-23
    • 1970-01-01
    相关资源
    最近更新 更多