Skip to content
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

Update jaeger all-in-one image to 1.14 #3128

Merged
merged 1 commit into from
Sep 10, 2019

Conversation

lukedirtwalker
Copy link
Collaborator

@lukedirtwalker lukedirtwalker commented Sep 10, 2019

Version 1.12 for me tried to allocate all the ram which would result in the machine no longer reacting.
With 1.14 I no longer saw this behavior.

Also use the new tmp volume (see jaegertracing/jaeger#1571)


This change is Reviewable

Version 1.12 for me tried to allocate all the ram which would result in the machine no longer reacting.
With 1.14 I no longer saw this behavior.

Also use the new tmp volume (see jaegertracing/jaeger#1571)
@lukedirtwalker lukedirtwalker added the feature New feature or request label Sep 10, 2019
Copy link
Contributor

@oncilla oncilla left a comment

Choose a reason for hiding this comment

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

:lgtm:

Reviewed 1 of 1 files at r1.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved

@lukedirtwalker lukedirtwalker merged commit 72c1d80 into scionproto:master Sep 10, 2019
@lukedirtwalker lukedirtwalker deleted the pubJaegerUpdate branch September 10, 2019 11:21
lukedirtwalker added a commit to lukedirtwalker/scion that referenced this pull request Sep 10, 2019
In scionproto#3128 we switched to temp storage, but that is deleted after calling down on the container.
That would mean on CI we can't access the traces, therefore switch back to the old storage approach.

Also update the version in scion.sh
lukedirtwalker added a commit that referenced this pull request Sep 10, 2019
In #3128 we switched to temp storage, but that is deleted after calling down on the container.
That would mean on CI we can't access the traces, therefore switch back to the old storage approach.

Also update the version in scion.sh
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants