Use badger as storage backend for tracing #31

Merged

fyrchik merged 1 commit from dstepanov-yadro/frostfs-dev-env:feat/jeager-badger into master

2023-05-25 07:29:55 +00:00

dstepanov-yadro commented

2023-05-23 10:24:59 +00:00

Member

subj

dstepanov-yadro force-pushed feat/jeager-badger from 08bf01ffc4 to 26e290efcb

2023-05-23 10:25:46 +00:00

Compare

dstepanov-yadro requested review from storage-core-committers 2023-05-23 10:26:01 +00:00

dstepanov-yadro requested review from storage-core-developers 2023-05-23 10:26:01 +00:00

alexvanin approved these changes 2023-05-23 10:26:56 +00:00

alexvanin left a comment

Owner

By default jaeger stores tracing data in memory?
Maybe we want to store jaeger data in persistent volume for debugging?

By default jaeger stores tracing data in memory? Maybe we want to store jaeger data in persistent volume for debugging?

fyrchik approved these changes 2023-05-23 10:28:39 +00:00

acid-ant approved these changes 2023-05-23 11:10:05 +00:00

dstepanov-yadro commented

2023-05-24 06:50:32 +00:00

Author

Member

By default jaeger stores tracing data in memory?

Yes, all-in-one container uses memory as storage backend.

Maybe we want to store jaeger data in persistent volume for debugging?

Badger is DB engine (like Bolt), so it is persistent storage. Tracing data will be stored on Docker volume and will be available after container restart.

> By default jaeger stores tracing data in memory? Yes, all-in-one container uses memory as storage backend. > Maybe we want to store jaeger data in persistent volume for debugging? Badger is DB engine (like Bolt), so it is persistent storage. Tracing data will be stored on Docker volume and will be available after container restart.