gCubeSystem
/
storage-manager-trigger
16
0
Fork 0
Code Issues Releases Wiki Activity

Update 'README.md' 

add new image
This commit is contained in:
Roberto Cirillo 2023-07-07 17:39:31 +02:00
parent 179a53b206
commit 8fc3928ae6
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -13,7 +13,9 @@ Storage-manager-trigger is a jave tool used for reporting the storage usage reco
## Documentation
Storage-manager-trigger is a java library used for scraping and sending storage usage records to the accounting framework. It works on a MongoDB replicaset cluster and acts on a mongodb system collection named "oplog".It is used on D4Science Infrastructure for collecting and send all the records coming from MongoDB to the D4Science accounting framework. In D4Science, this library works in conjuction with the storage-manager gCube libraries, realizing a distribuited system of store and accounting data: the storage-manager libraries send the record in form of file and metadata to MongoDB, MongoDB collects them, the storageTrigger sniffs the new record from mongodb and send the related metadata informations to the accounting framework, in batch mode. In this way, the record is sent, stored and accounted in a distribuited mode. The storage-trigger library typically run on a delayed secondary member of a MongoDB cluster with no election priority avoiding, in this way, performace degradation on MongoDB primary node.
Storage-manager-trigger is a java library used for scraping and sending storage usage records to the accounting framework. It works on a MongoDB replicaset cluster and acts on a mongodb system collection named "oplog".It is used on D4Science Infrastructure for collecting and send all the records coming from MongoDB to the D4Science accounting framework. In D4Science, this library works in conjuction with the storage-manager gCube libraries, realizing a distribuited system of store and accounting data: the storage-manager libraries send the record in form of file and metadata to MongoDB, MongoDB collects them, the storageTrigger sniffs the new record from mongodb and send the related metadata informations to the accounting framework, in batch mode. In this way, the record is sent, stored and accounted in a distribuited mode. The storage-trigger library typically run on a delayed secondary member of a MongoDB cluster with no election priority avoiding, in this way, performace degradation on MongoDB primary node. \
[[images/MongoDB.png]]
## Change log