Skip to main content
Database Administrators

Return to Answer

added 5 characters in body
Source Link
Erick Ramirez
Erick Ramirez
  • 4.2k
  • 1
  • 7
  • 27

The number of threads spawned by Cassandra isn't necessarily a problem and isn't necessarily the reason for Cassandra failing.

In my experience, the number of threads on a node increase as the amount of application requests grows -- that is normal behaviour for multi-threaded applications like Cassandra.

You need to review the errors and warning messages in the Cassandra logs for clues as to why it is crashing. You also need to review your monitoring to see if the application load/traffic has increased.

Typically if a Cassandra node is overloaded, one of the symptoms is that it can no longer spawn threads because it has run out of resources. In this examplescenario, a high number of threads is just a symptom of the problem and not the cause. Cheers!

The number of threads spawned by Cassandra isn't necessarily a problem and isn't necessarily the reason for Cassandra failing.

In my experience, the number of threads on a node increase as the amount of application requests grows -- that is normal behaviour for multi-threaded applications like Cassandra.

You need to review the errors and warning messages in the Cassandra logs for clues as to why it is crashing. You also need to review your monitoring to see if the application load/traffic has increased.

Typically if a Cassandra node is overloaded, one of the symptoms is that it can no longer spawn threads because it has run out of resources. In this example, a high number of threads is just a symptom of the problem and the cause. Cheers!

The number of threads spawned by Cassandra isn't necessarily a problem and isn't necessarily the reason for Cassandra failing.

In my experience, the number of threads on a node increase as the amount of application requests grows -- that is normal behaviour for multi-threaded applications like Cassandra.

You need to review the errors and warning messages in the Cassandra logs for clues as to why it is crashing. You also need to review your monitoring to see if the application load/traffic has increased.

Typically if a Cassandra node is overloaded, one of the symptoms is that it can no longer spawn threads because it has run out of resources. In this scenario, a high number of threads is just a symptom of the problem and not the cause. Cheers!

Source Link
Erick Ramirez
Erick Ramirez
  • 4.2k
  • 1
  • 7
  • 27

The number of threads spawned by Cassandra isn't necessarily a problem and isn't necessarily the reason for Cassandra failing.

In my experience, the number of threads on a node increase as the amount of application requests grows -- that is normal behaviour for multi-threaded applications like Cassandra.

You need to review the errors and warning messages in the Cassandra logs for clues as to why it is crashing. You also need to review your monitoring to see if the application load/traffic has increased.

Typically if a Cassandra node is overloaded, one of the symptoms is that it can no longer spawn threads because it has run out of resources. In this example, a high number of threads is just a symptom of the problem and the cause. Cheers!