Skip to content

[refactor] Return chunk of traces from remote storage api v2 #6830

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Mar 9, 2025

Conversation

mahadzaryab1
Copy link
Collaborator

Which problem is this PR solving?

Description of the changes

How was this change tested?

  • CI

Checklist

Signed-off-by: Mahad Zaryab <[email protected]>
Signed-off-by: Mahad Zaryab <[email protected]>
@mahadzaryab1 mahadzaryab1 changed the title Trace storage return [refactor] Return chunk of traces from remote storage api v2 Mar 9, 2025
@mahadzaryab1 mahadzaryab1 marked this pull request as ready for review March 9, 2025 20:16
@mahadzaryab1 mahadzaryab1 requested a review from a team as a code owner March 9, 2025 20:16
@mahadzaryab1 mahadzaryab1 requested a review from pavolloffay March 9, 2025 20:16
Copy link

codecov bot commented Mar 9, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.07%. Comparing base (1d516aa) to head (1d7bf53).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #6830      +/-   ##
==========================================
+ Coverage   96.05%   96.07%   +0.02%     
==========================================
  Files         365      366       +1     
  Lines       20720    20750      +30     
==========================================
+ Hits        19902    19935      +33     
+ Misses        624      622       -2     
+ Partials      194      193       -1     
Flag Coverage Δ
badger_v1 9.83% <ø> (-0.03%) ⬇️
badger_v2 1.98% <ø> (-0.01%) ⬇️
cassandra-4.x-v1-manual 14.83% <ø> (-0.05%) ⬇️
cassandra-4.x-v2-auto 1.97% <ø> (-0.01%) ⬇️
cassandra-4.x-v2-manual 1.97% <ø> (-0.01%) ⬇️
cassandra-5.x-v1-manual 14.83% <ø> (-0.05%) ⬇️
cassandra-5.x-v2-auto 1.97% <ø> (-0.01%) ⬇️
cassandra-5.x-v2-manual 1.97% <ø> (-0.01%) ⬇️
elasticsearch-6.x-v1 19.45% <ø> (+0.19%) ⬆️
elasticsearch-7.x-v1 19.53% <ø> (+0.19%) ⬆️
elasticsearch-8.x-v1 19.70% <ø> (+0.18%) ⬆️
elasticsearch-8.x-v2 1.98% <ø> (-0.01%) ⬇️
grpc_v1 10.87% <ø> (-0.04%) ⬇️
grpc_v2 7.92% <ø> (-0.03%) ⬇️
kafka-3.x-v1 10.12% <ø> (-0.04%) ⬇️
kafka-3.x-v2 1.98% <ø> (-0.01%) ⬇️
memory_v2 1.98% <ø> (-0.01%) ⬇️
opensearch-1.x-v1 19.58% <ø> (+0.19%) ⬆️
opensearch-2.x-v1 19.58% <ø> (+0.19%) ⬆️
opensearch-2.x-v2 1.98% <ø> (-0.01%) ⬇️
tailsampling-processor 0.48% <ø> (-0.01%) ⬇️
unittests 94.94% <ø> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@mahadzaryab1 mahadzaryab1 requested a review from yurishkuro March 9, 2025 20:24
@@ -129,6 +129,12 @@ message FindTraceIDsResponse {
repeated FoundTraceID trace_ids = 1;
}

// TracesChunk is a chunk of traces returned by the storage backend.
// Each TracesData object contains spans belonging to a single trace.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// Each TracesData object contains spans belonging to a single trace.
// All spans in a single TracesData object MUST belong to the same trace.
// Spans from a single large trace MAY be split across multiple chunks,
// but those chunks MUST be consecutive.

Signed-off-by: Mahad Zaryab <[email protected]>
@mahadzaryab1 mahadzaryab1 requested a review from yurishkuro March 9, 2025 20:44
Signed-off-by: Mahad Zaryab <[email protected]>
@@ -129,6 +129,14 @@ message FindTraceIDsResponse {
repeated FoundTraceID trace_ids = 1;
}

// Chunking requirements:
// - A single chunk MUST NOT contain spans from multiple traces.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the use of the word "chunk" is misleading here. Since the type is called xxChunk one might interpret that the whole chunk (multiple v1.TracesData entries) must be for the same trace, which is not the case.

Signed-off-by: Mahad Zaryab <[email protected]>
Signed-off-by: Mahad Zaryab <[email protected]>
@yurishkuro yurishkuro added this pull request to the merge queue Mar 9, 2025
Merged via the queue into jaegertracing:main with commit 935637d Mar 9, 2025
60 checks passed
@mahadzaryab1 mahadzaryab1 deleted the trace-storage-return branch April 2, 2025 17:13
amilbcahat pushed a commit to amilbcahat/jaeger that referenced this pull request May 4, 2025
…racing#6830)

## Which problem is this PR solving?
- Towards jaegertracing#6789

## Description of the changes
- This PR addresses
jaegertracing#6829 (comment)
and changes the remote storage api v2 to return a chunk of traces
instead of a single trace from `GetTraces` and `FindTraces`

## How was this change tested?
- CI

## Checklist
- [x] I have read
https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
- [x] I have signed all commits
- [x] I have added unit tests for the new functionality
- [x] I have run lint and test steps successfully
  - for `jaeger`: `make lint test`
  - for `jaeger-ui`: `npm run lint` and `npm run test`

---------

Signed-off-by: Mahad Zaryab <[email protected]>
amilbcahat pushed a commit to amilbcahat/jaeger that referenced this pull request May 4, 2025
…racing#6830)

## Which problem is this PR solving?
- Towards jaegertracing#6789

## Description of the changes
- This PR addresses
jaegertracing#6829 (comment)
and changes the remote storage api v2 to return a chunk of traces
instead of a single trace from `GetTraces` and `FindTraces`

## How was this change tested?
- CI

## Checklist
- [x] I have read
https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
- [x] I have signed all commits
- [x] I have added unit tests for the new functionality
- [x] I have run lint and test steps successfully
  - for `jaeger`: `make lint test`
  - for `jaeger-ui`: `npm run lint` and `npm run test`

---------

Signed-off-by: Mahad Zaryab <[email protected]>
Signed-off-by: amol-verma-allen <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/storage changelog:exprimental Change to an experimental part of the code v2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants