#support

Deleting Data from Clickhouse Directly

TLDR Shreyash is facing issues deleting data from Clickhouse directly due to lack of space. vishal-signoz confirms the issue is insufficient space.

9mo

Join the chat

Feb 24, 2023 (9 months ago)

Photo of md5-ca6495d5be926db80e09aabf066f4b8b

Shreyash

06:03 AM

Is there a way to delete the data from click house directly. The frontend is taking a lot of time.

06:06

Shreyash

06:06 AM

<pre>
    /src/exporter/clickhousetracesexporter/writer.go:130

    /src/exporter/clickhousetracesexporter/writer.go:109
2023-02-24T05:49:34.993Z    error    clickhousetracesexporter/writer.go:110    Could not write a batch of spans    {&quot;kind&quot;: &quot;exporter&quot;, &quot;data_type&quot;: &quot;traces&quot;, &quot;name&quot;: &quot;clickhousetraces&quot;, &quot;error&quot;: &quot;code: 243, message: Cannot reserve 1.00 MiB, not enough space&quot;}

    /src/exporter/clickhousetracesexporter/writer.go:110
2023-02-24T05:49:35.344Z    warn    [email protected]/batch_processor.go:178    Sender failed    {&quot;kind&quot;: &quot;processor&quot;, &quot;name&quot;: &quot;batch&quot;, &quot;pipeline&quot;: &quot;logs&quot;, &quot;error&quot;: &quot;sending_queue is full&quot;}
2023-02-24T05:49:36.345Z    warn    [email protected]/batch_processor.go:178    Sender failed    {&quot;kind&quot;: &quot;processor&quot;, &quot;name&quot;: &quot;batch&quot;, &quot;pipeline&quot;: &quot;logs&quot;, &quot;error&quot;: &quot;sending_queue is full&quot;}
2023-02-24T05:49:37.346Z    warn    [email protected]/batch_processor.go:178    Sender failed    {&quot;kind&quot;: &quot;processor&quot;, &quot;name&quot;: &quot;batch&quot;, &quot;pipeline&quot;: &quot;logs&quot;, &quot;error&quot;: &quot;sending_queue is full&quot;}
2023-02-24T05:49:38.347Z    warn    [email protected]/batch_processor.go:178    Sender failed    {&quot;kind&quot;: &quot;processor&quot;, &quot;name&quot;: &quot;batch&quot;, &quot;pipeline&quot;: &quot;logs&quot;, &quot;error&quot;: &quot;sending_queue is full&quot;}
2023-02-24T05:49:39.347Z    warn    [email protected]/batch_processor.go:178    Sender failed    {&quot;kind&quot;: &quot;processor&quot;, &quot;name&quot;: &quot;batch&quot;, &quot;pipeline&quot;: &quot;logs&quot;, &quot;error&quot;: &quot;sending_queue is full&quot;}
2023-02-24T05:49:40.347Z    error    exporterhelper/queued_retry.go:310    Dropping data because sending_queue is full. Try increasing queue_size.    {&quot;kind&quot;: &quot;exporter&quot;, &quot;data_type&quot;: &quot;logs&quot;, &quot;name&quot;: &quot;clickhouselogsexporter&quot;, &quot;dropped_items&quot;: 861}

    /go/pkg/mod/go.opentelemetry.io/[email protected]/exporter/exporterhelper/queued_retry.go:310

    /go/pkg/mod/go.opentelemetry.io/[email protected]/exporter/exporterhelper/logs.go:114

    /go/pkg/mod/go.opentelemetry.io/collector/[email protected]/logs.go:36

    /go/pkg/mod/go.opentelemetry.io/collector/processor/[email protected]/batch_processor.go:339

    /go/pkg/mod/go.opentelemetry.io/collector/processor/[email protected]/batch_processor.go:176

    /go/pkg/mod/go.opentelemetry.io/collector/processor/[email protected]/batch_processor.go:144
2023-02-24T05:49:40.348Z    warn    [email protected]/batch_processor.go:178    Sender failed    {&quot;kind&quot;: &quot;processor&quot;, &quot;name&quot;: &quot;batch&quot;, &quot;pipeline&quot;: &quot;logs&quot;, &quot;error&quot;: &quot;sending_queue is full&quot;}
</pre>

Getting above error

Photo of md5-f936d3e5743d23344d6c60813189716f

vishal-signoz

10:25 AM

Looks like there’s not enough space for clickhouse

SigNoz Community

Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI

Indexed 1023 threads (61% resolved)

Join Our Community

Similar Threads

Resolving Signoz Query Service Error

Einav encountered an error related to a missing table in the Signoz service which was preventing data visibility in the UI. Srikanth guided them to restart specific components and drop a database table, which resolved the issue.

3mo

Issue Accessing Pod Logs in SigNoz UI on AKS

prashant is facing an issue accessing pod logs of their application in SigNoz UI on AKS. nitya-signoz and Prashant provide suggestions related to log file paths and potential issues, but the problem remains unresolved.

6mo

Troubleshooting SigNoz Auto-Instrumentation Configuration

igor is having trouble configuring auto-instrumentation for Java applications using SigNoz, with traces not appearing in the SigNoz UI. Prashant advises to check logs of the otel sidecar, use service name for endpoint, verify supported libraries, and test with telemetrygen. However, the issue still persists.

8mo