Mahesh Bhosle comments

Results 8 comments of


                                            Mahesh Bhosle

ServerErrorHandler: Poco::Exception. Code: 1000, e.code() = 107, e.displayText() = Net Exception: Socket is not connected, Stack trace (when copying this message, always include the lines below): clickhouse-1 |

@csvan I suspect that `clickhouse` is causing spikes in the CPU usage and the CPU usage for the server has not been stable

ServerErrorHandler: Poco::Exception. Code: 1000, e.code() = 107, e.displayText() = Net Exception: Socket is not connected, Stack trace (when copying this message, always include the lines below): clickhouse-1 |

Do you think having too many projects can cause CPU spikes? I have a total of 67 projects on the Sentry and 23 out of them are actively used for...

ServerErrorHandler: Poco::Exception. Code: 1000, e.code() = 107, e.displayText() = Net Exception: Socket is not connected, Stack trace (when copying this message, always include the lines below): clickhouse-1 |

@azaslavsky For now I have just rolled back to 24.1.0 and the clickhouse stopped throwing the error, but still seeing a lot of CPU spikes for the server.

ServerErrorHandler: Poco::Exception. Code: 1000, e.code() = 107, e.displayText() = Net Exception: Socket is not connected, Stack trace (when copying this message, always include the lines below): clickhouse-1 |

@aldy505 For now I have rolled-back to version 24.1.0 as it was production, Should I try [this](https://github.com/getsentry/snuba/issues/5707) on version 23.4.0 ?

ServerErrorHandler: Poco::Exception. Code: 1000, e.code() = 107, e.displayText() = Net Exception: Socket is not connected, Stack trace (when copying this message, always include the lines below): clickhouse-1 |

@aldy505 I have set up a new sentry server with version 23.4.0, I will try it and let know. I am a bit confused changing `consumer` will resolve the **clickhouse**...

ServerErrorHandler: Poco::Exception. Code: 1000, e.code() = 107, e.displayText() = Net Exception: Socket is not connected, Stack trace (when copying this message, always include the lines below): clickhouse-1 |

replacing rust-consumer with consumer in the `docker-compose.yml` file resolved the errors, now I no longer see the error in the `clickhouse` container. But am still not sure why the CPU...

ServerErrorHandler: Poco::Exception. Code: 1000, e.code() = 107, e.displayText() = Net Exception: Socket is not connected, Stack trace (when copying this message, always include the lines below): clickhouse-1 |

I understand @csvan, but right now I am using the `t3a.2xlarge` instance, which I feel is more than enough to run things smoothly. We had an old sentry server with...

Tempo often cannot query the traces

I am facing the same issue on Tempo version `2.8.1`, I am running Tempo in Single Binary Mode on a k8s cluster.