Skip to content

[BUG]: increase max payload size of log service (Go) #4534

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 1 commit into from
May 13, 2025

Conversation

codetheweb
Copy link
Contributor

@codetheweb codetheweb commented May 12, 2025

Description of changes

The max gRPC payload/response sizes were updated for the Rust log client, but were never updated for the log service. So the PushLogs method was still failing when the request was > 4MB.

Test plan

How are these changes tested?

  • Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs section?

n/a

Copy link

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

  • Can you think of any use case in which the code does not behave as intended? Have they been tested?
  • Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
  • If appropriate, are there adequate property based tests?
  • If appropriate, are there adequate unit tests?
  • Should any logging, debugging, tracing information be added or removed?
  • Are error messages user-friendly?
  • Have all documentation changes needed been made?
  • Have all non-obvious changes been commented?

System Compatibility

  • Are there any potential impacts on other parts of the system or backward compatibility?
  • Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

  • Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

@codetheweb codetheweb marked this pull request as ready for review May 12, 2025 23:44
@codetheweb codetheweb requested a review from HammadB May 12, 2025 23:44
Copy link
Contributor

This PR fixes a bug where the log service was still limited to 4MB payload size, despite the Rust log client being updated to handle larger payloads. The change uses the shared gRPC utility with proper payload size configuration.

This summary was automatically generated by @propel-code-bot

@@ -158,7 +158,7 @@ func NewWithGrpcProvider(config Config, provider grpcutils.GrpcProvider) (*Serve
s.softDeleteCleaner.Start()

log.Info("Starting GRPC server")
s.grpcServer, err = provider.StartGrpcServer("coordinator", config.GrpcConfig, func(registrar grpc.ServiceRegistrar) {
s.grpcServer, err = provider.StartGrpcServer("sysdb-service", config.GrpcConfig, func(registrar grpc.ServiceRegistrar) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

why this change? does anything downstream for telemetry use it are we sure nothing depends on it?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

the coordinator value was not previously used because sysdb-service was hard coded in the common helper

@codetheweb codetheweb enabled auto-merge (squash) May 13, 2025 00:02
@codetheweb codetheweb merged commit 3028a39 into main May 13, 2025
71 checks passed
@codetheweb codetheweb deleted the bug-log-service-increase-max-payload-size branch May 13, 2025 17:29
var listener net.Listener
listener, err = net.Listen("tcp", ":"+config.PORT)

_, err = grpcutils.Default.StartGrpcServer("log-service", &grpcutils.GrpcConfig{
Copy link
Contributor

Choose a reason for hiding this comment

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

This line loses sharedOtel?

Copy link
Contributor

Choose a reason for hiding this comment

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

inside of the grpcutils package, it's using the shared otel package (, so I think this should be equivalent, but I might be missing something.

eculver added a commit that referenced this pull request May 14, 2025
eculver added a commit that referenced this pull request May 14, 2025
…#4540)

This reverts commit 3028a39.

After we deployed this commit, we lost metrics for log-service, so we
suspect it has something to do with it. I will re-enable the payload
size fix one way or the other, but want to get back to working
observability for the time being.
eculver added a commit that referenced this pull request May 14, 2025
## Description of changes

This restores the core functionality we were hoping to add in #4534
which is increasing the gRPC payload size. Instead of using the methods
from the `grpcutils` package, this just sets the option in the existing
setup so that we hopefully don't break whatever voodoo is keeping
metrics collection working.

- Improvements & Bug fixes
  - See #4534
- New functionality
  - See #4534

## Test plan

I ran `make test` locally, the build succeeds, but our local tests are
broken for some reason. Relying on CI so that I don't have to debug yet
another orthogonal issue.
itaismith pushed a commit that referenced this pull request May 23, 2025
The max gRPC payload/response sizes were updated for the Rust log
client, but were never updated for the log service. So the `PushLogs`
method was still failing when the request was > 4MB.

_How are these changes tested?_

- [x] Tests pass locally with `pytest` for python, `yarn test` for js,
`cargo test` for rust

_Are all docstrings for user-facing APIs updated if required? Do we need
to make documentation changes in the [docs
section](https://github.com/chroma-core/chroma/tree/main/docs/docs.trychroma.com)?_

n/a

checkpoint after adding default

checkpoint test passing
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants