Code Monkey home page Code Monkey logo

Comments (1)

CMGS avatar CMGS commented on May 19, 2024

这个问题是这样的:

  1. 我们现有的机制只保证了 grpc 请求的可靠性,grpc 请求在,core 除非 kill -9, 否则正常退出是不会导致 leak
  2. lambda 在 background run 的时候 grpc 请求已经没得了
  3. 这时候 someone 更新 core,通过 core 保证 background workload recycle 和 expire recycle 失效
  4. 这个 lambda 容器就永久存在了

解决方案的话我能想到的是:

  1. 每个 core 在退出的时候通过 hostname 作为 path 记录一个状态到 store 里面
  2. 这个 host 上的 core 启动的时候自检,load 状态做对应处理,然后删除状态
  3. 每个请求进来的时候记录一个状态,请求结束的时候清理,同样也需要在 core 启动的时候进行自检

from core.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.