Why Rocks DB logging of edgeHub is written filesystem?
See original GitHub issueExpected Behavior
it is question. I am beginner so I may wrong this question.
I want to use tempfs /tmp/edgeHub because Rocks DB of edgeHub is very hard written at NAND disk (flash storage). So the disk lifespan was very short. (I know how to configuration of using tempfs at iothub.)
I think docker containers logging of defacto standard architecture is stdout. Why Rocks DB don’t use stdout & tempfs instead of rootfs? The product don’t wanted to inform log information to end user?
Current Behavior
I hope The edgeHub of Rocks DB logging to tempfs or stdout.
Steps to Reproduce
- Send to edgeHub about many msg/sec,
Context (Environment)
Raspi 2 microsd TLC 16GB
Device (Host) Operating System
Architecture
arm32
Container Operating System
Raspi
Runtime Versions
iotedged
iotedge 1.0.7
Edge Agent
EdgeAgent1.0.7
Edge Hub
iEdgeHub 1.0.7
Docker
moby-engine_3.0.5_armhf
Logs
Additional Information
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:15 (4 by maintainers)
Top Results From Across the Web
Prepare to deploy your IoT Edge solution in production
The IoT Edge hub and agent modules use local storage to maintain state and enable messaging between modules, devices, and the cloud. For...
Read more >Do Rocks DB or Level DB write log even when compaction?
Yes, data log is just for memtable. Leveldb only logs metadata of new sstables by using manifest file. Data log and manifest file...
Read more >building interactive distributed processing applications at a ...
The design of Ambry is inspired by log-structure file systems (LFS) [59,60]. These file systems are optimized for write throughput by sequentially writing...
Read more >Data Lake Insight
Log in to the DLI console, create a Flink SQL job, write SQL statements for the job, and configure running parameters. NO TE....
Read more >Simple index
... vipe idms-pairfinder-2 nameko-cloudant truncate-and-write-to-sql gen-msmask slimeda pygpg gitignore-parser idealist topsis-jagritikhanna log-helper-bit3 ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
No, the LSM tree persists directly to the filesystem. It doesn’t directly use stdout. The use of RocksDB is an internal implementation detail. It is not a public interface and isn’t expected to be interacted with directly by a user. The user interacts with it via the various Edge Hub APIs over mqtt/ampq/http etc.
Hello, Any news on the offline feature that @myagley was talking about? (Bound the message on RocksDB by size in addition to the time based limits that we have today)
When the limit is reached it would be useful to have a behavior similar to a circular buffer.
Has this functionality already been implemented?
Thanks for your support