Skip to content
New issue

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

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

Already on GitHub? # to your account

To defend against possible OOME when selecting TransactionId that with a large volume of Span Data. #1397

Closed
koo-taejin opened this issue Jan 4, 2016 · 1 comment
Assignees
Milestone

Comments

@koo-taejin
Copy link
Member

To defend against possible OOME when selecting Transaction Id that with a large volume of Span Data.

@koo-taejin koo-taejin self-assigned this Jan 4, 2016
@emeroad
Copy link
Member

emeroad commented Jan 4, 2016

related issue : #1396

koo-taejin added a commit to koo-taejin/pinpoint that referenced this issue Jan 4, 2016
…a large volume of Span Data. pinpoint-apm#1397

To depend possibility of OOME when selecting TransactionId that with a large volume of Span Data.
@Xylus Xylus changed the title To depend possibility of OOME when selecting TransactionId that with a large volume of Span Data. To defend against possible OOME when selecting TransactionId that with a large volume of Span Data. Jan 4, 2016
@emeroad emeroad added this to the 1.5.2 milestone Jan 4, 2016
koo-taejin added a commit to koo-taejin/pinpoint that referenced this issue Jan 4, 2016
…a large volume of Span Data. pinpoint-apm#1397

To depend possibility of OOME when selecting TransactionId that with a large volume of Span Data.
koo-taejin added a commit to koo-taejin/pinpoint that referenced this issue Jan 4, 2016
…a large volume of Span Data. pinpoint-apm#1397

To depend possibility of OOME when selecting TransactionId that with a large volume of Span Data.
koo-taejin added a commit to koo-taejin/pinpoint that referenced this issue Jan 5, 2016
…a large volume of Span Data. pinpoint-apm#1397

To depend possibility of OOME when selecting TransactionId that with a large volume of Span Data.
koo-taejin added a commit that referenced this issue Jan 5, 2016
To defend against possible OOME when selecting Transaction Id that with a large volume of Span Data.
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

2 participants