-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Increase Alpha trace logs. #3679
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bump up the number of logs per span to capture all the events from Server.Query.
Approved.
Sent from Pixel 2
…On Tue, Jul 16, 2019, 6:07 PM Daniel Mai ***@***.***> wrote:
This change bumps up the number of logs per span to capture all the events
from Server.Query instead of getting truncated logs in the trace data of up
to 64 of the latest annotations.
When I load the 21-million movie data set and run a query to get all the
movies directed by Steven Spielberg, Jaeger shows 232 logs for the query.
With this change, the logs would be truncated if there are more than 256
annotations in a single span, leaving us to the same problem of possibly
losing valuable info for a query trace.
{
director(func: ***@***.***, "steven spielberg")) {
***@***.***
director.film {
***@***.***
initial_release_date
country {
***@***.***
}
starring {
performance.actor {
***@***.***
}
performance.character {
***@***.***
}
}
genre {
***@***.***
}
}
}
}
[image: image]
<https://user-images.githubusercontent.com/2251820/61339794-4996f700-a7f4-11e9-8c55-46c809e328b1.png>
------------------------------
You can view, comment on, or merge this pull request online at:
#3679
Commit Summary
- Increase Alpha trace logs.
File Changes
- *M* dgraph/cmd/alpha/run.go
<https://github.com/dgraph-io/dgraph/pull/3679/files#diff-0> (2)
Patch Links:
- https://github.com/dgraph-io/dgraph/pull/3679.patch
- https://github.com/dgraph-io/dgraph/pull/3679.diff
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#3679?email_source=notifications&email_token=AJATO5XDAST7XMES25V6R5TP7ZWDVA5CNFSM4IEJJAMKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G7TNCXQ>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJATO5T44YQBJGOU62IBYALP7ZWDVANCNFSM4IEJJAMA>
.
|
gitlw
approved these changes
Jul 17, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: 0 of 1 files reviewed, all discussions resolved (waiting on @manishrjain)
Thanks @dgraph-bot 🤔 and @gitlw. |
dna2github
pushed a commit
to dna2fork/dgraph
that referenced
this pull request
Jul 19, 2019
Bump up the number of logs per span to capture all the events from Server.Query which can create a lot of logs.
danielmai
added a commit
that referenced
this pull request
Aug 13, 2019
Bump up the number of logs per span to capture all the events from Server.Query which can create a lot of logs.
danielmai
added a commit
that referenced
this pull request
Aug 14, 2019
* Increase max trace logs per span in Alpha. (#3679) Bump up the number of logs per span to capture all the events from Server.Query which can create a lot of logs. * Vendor in external dependencies necessary for OpenCensus. We did not strictly vendor everything when v1.0.13 was originally released. Now that we need to create a new patch release on top of Dgraph v1.0.13, we need to bring back old dependencies that are necessary to create a new Dgraph binary. We pick up versions for OpenCensus, Prometheus client, and gRPC that were released before March 10, 2019 (the v1.0.13 release date). * OpenCensus govendor fetch go.opencensus.io/...@v0.19.2 v0.19.2 was released on Mar 21, 2019. I tried vendoring in v1.19.1 (released Mar 4) but it won't succeed with this error. v0.19.2 should be ok to use. Error: repo remote not secure Failed to fetch package "git.apache.org/thrift.git/lib/go/thrift" * Prometheus client govendor fetch github.com/prometheus/client_golang/prometheus/...@v0.9.2 v0.9.2 was released on Dec 6, 2018. * gRPC govendor fetch google.golang.org/grpc/...@v1.13.0 v1.13.0 was released on Jun 19, 2018. We already version lock gRPC to v1.13.0 in the contrib/release.sh.
danielmai
added a commit
that referenced
this pull request
Aug 30, 2019
Bump up the number of logs per span to capture all the events from Server.Query which can create a lot of logs.
danielmai
added a commit
that referenced
this pull request
Aug 30, 2019
Cherry-picked from #3679. Bump up the number of logs per span to capture all the events from Server.Query which can create a lot of logs. * release/v1.0: Add comment to MaxAnnotationsEventsPerSpan.
danielmai
added a commit
that referenced
this pull request
Sep 4, 2019
* Increase max trace logs per span in Alpha. (#3679) Bump up the number of logs per span to capture all the events from Server.Query which can create a lot of logs. * Vendor in external dependencies necessary for OpenCensus. We did not strictly vendor everything when v1.0.13 was originally released. Now that we need to create a new patch release on top of Dgraph v1.0.13, we need to bring back old dependencies that are necessary to create a new Dgraph binary. We pick up versions for OpenCensus, Prometheus client, and gRPC that were released before March 10, 2019 (the v1.0.13 release date). * OpenCensus govendor fetch go.opencensus.io/...@v0.19.2 v0.19.2 was released on Mar 21, 2019. I tried vendoring in v1.19.1 (released Mar 4) but it won't succeed with this error. v0.19.2 should be ok to use. Error: repo remote not secure Failed to fetch package "git.apache.org/thrift.git/lib/go/thrift" * Prometheus client govendor fetch github.com/prometheus/client_golang/prometheus/...@v0.9.2 v0.9.2 was released on Dec 6, 2018. * gRPC govendor fetch google.golang.org/grpc/...@v1.13.0 v1.13.0 was released on Jun 19, 2018. We already version lock gRPC to v1.13.0 in the contrib/release.sh. (cherry picked from commit b196ca3)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change bumps up the number of logs per span to capture all the events from Server.Query instead of getting truncated logs in the trace data of up to 64 of the latest annotations.
When I load the 21-million movie data set and run a query to get all the movies directed by Steven Spielberg, Jaeger shows 232 logs for the query. With this change, the logs would be truncated if there are more than 256 annotations in a single span, leaving us to the same problem of possibly losing valuable info for a query trace.
This change is