Skip to content
This repository has been archived by the owner on Nov 16, 2021. It is now read-only.

Exchange Report Document #13

Closed
tempestb opened this issue Jan 18, 2017 · 3 comments
Closed

Exchange Report Document #13

tempestb opened this issue Jan 18, 2017 · 3 comments
Assignees

Comments

@tempestb
Copy link

Greetings Earthman,

Right now there are three developers, including myself, that are working on applications that communicate to the API outside of the existing Storj libraries. We use the CLI tool debug as reference.

Currently, there is a new feature added which involves Reports, specifically Exchange Reports. It appears these are called after every Shard transfer. (Both up and down.) The information that is being passed is unknown, so it would be helpful if there was a document which briefly explained where these values are coming from.

Specifically...

"dataHash": Assume Shard Hash?
"reporterId": ???
"farmerId": Assume Farmer Hash?
"clientId": ???
"exchangeStart": ??? Start of byte index? Or possibly this is a unix time stamp of some sort?
"exchangeEnd": ??? End of byte index? time stamp?
"exchangeResultCode": ??? Likely the Farmer response after transfer, but wasn't sure if I need to provide?
"exchangeResultMessage": ??? Same

This is not urgent, but I was told that mirrors rely on this feature, so we would obviously like to support mirroring of shards.

Thanks!

@braydonf
Copy link
Contributor

We also need to define how to turn exchange reports into an average bandwidth metric for each farmer. This is necessary for ideas discussed in SIP6.

@braydonf
Copy link
Contributor

I think this document should also describe the process to get consensus on network and bandwidth statistics.

@braydonf
Copy link
Contributor

braydonf commented Sep 14, 2017

Looks like we can finally get around to getting this documented in whole, and how the information will relate and be used. #37

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants