Git Product home page Git Product logo

Comments (5)

rahchuenmonroe avatar rahchuenmonroe commented on August 15, 2024

Another interesting thing we just noticed is that, when our redis instance went down for a few minutes and when the pods lost connection to it, all of our triton servers had this same segmentation fault at the same time and all restarted. Not sure if that is this pattern is the same reason we are seeing those core dumps intermittently, but either way, those segmentation faults seem like unexpected behavior.

from server.

statiraju avatar statiraju commented on August 15, 2024

@rahchuenmonroe we would appreciate if you could experiment and give us more concrete steps to reproduce the issue.

from server.

statiraju avatar statiraju commented on August 15, 2024

[6861] created for tracking

from server.

rmccorm4 avatar rmccorm4 commented on August 15, 2024

Our prior version was 2.44.0 and we never saw this issue before. We also started using redis caching for ensembles in this version.

In addition to @statiraju comment about providing reproduction steps, it would be great if you could also try simplifying the set of things that changed to help isolate the issue. For example, two experiments:

  1. 24.04 vs 24.05 both with no redis caching, see if 24.05 introduces failure
  2. 24.05 no redis caching vs. 24.05 with redis caching, see if redis caching introduces failure

from server.

rahchuenmonroe avatar rahchuenmonroe commented on August 15, 2024

To clarify, we were using 24.03 prior and now are using 24.05 because of ensemble caching.

So far:
24.05, caching enabled: pods restart after core dumps.
24.05, caching disabled: no restarts.
24.03, caching disabled: no restarts.
Can't test for 24.03 with caching enabled since ensemble caching is only in latest version.

The only way I have been able to somewhat accidentally reproduce this was when the redis instance went down for a few minutes during an update and then all pods core dumped. I'm not sure if that's something you folks can somewhat reproduce? Although it's hard to say that is what is happening intermittently also, it does seem a bit suspicious. And from my understanding, if the redis caching request fails, the request should be processed normally instead, so losing connection to redis should not restart the server.

Let me know if I can provide any more information on this, thanks for looking into this!

from server.

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.