Developer
Searchโ€ฆ
๐Ÿ“ก
Metadata-Servers

๐Ÿ”ฆIntroduction

The metadata server is responsible for the formation, migration, maintenance and renewal of blockchain storage contracts. Storage contracts are synchronized with the gateway at first setup and thereafter when a contract has to be replaced or new contracts are required to upload more data. By default storage contracts are valid for 3 months. Storage contracts are grouped together into contract-sets of 20 contracts each. When data is uploaded it is uploaded to one specific contract set at a time. Every gateway includes a total 4x redundant contract-sets.
To guarantee availability in production and no Single point of failure (SPOF), a number of measures have been taken on both the gateway & metadata-server;
    Erasure coding. 5-of-20. Only 5 hosts are required to reconstruct the file.
    Redundant contract sets. As mentioned above each gateway has 4x redundant contract sets client-side in case one contract set becomes unavailable.
    Long contract validity. Having a long validity of contract allows the connection to be cut to the metadata-server for long periods of time without impacting availability.
    Gateway Isolation Mode (WIP). Isolation mode is the ultimate measure taken when the gateway is cut-off from StoreWise or a partner MDS. If this happens the gateway will cease to attempt sending metadata and switch to cache metadata and handle all storage operations client-side. When a new connection is achieved all metadata-will be re-synchronized with the metadata-server. With to the backup measures listed above, the gateway will be able to continue operation for the duration the blockchain storage contracts are valid.

๐Ÿ“ถ Available Metadata-servers (Post Alpha)

During nominal operation the gateway communicates with the gateway to exchange blockchain storage contracts and metafiles. To optimize for latency it is recommended to connect with a gateway geographically closest to the gateway.
The following metadata-servers will be available after the Alpha;
Location
Identifier
North America ๐Ÿ”œ
s3.na.storewise.tech:443
Europe ๐Ÿ”œ
s3.eu.storewise.tech:443
Asia Pacific ๐Ÿ”œ
s3.ap.storewsie.tech:443
Middle East ๐Ÿ”œ
s3.me.storewise.tech:443
Africa ๐Ÿ”œ
s3.af.storewise.tech:443
South America ๐Ÿ”œ
s3.sa.storewise.tech:443
For businesses it is possible to run your own private metadata-server cluster. Please contact StoreWise for further information.
Once you've selected the metadata-server closest to your gateway, it can be added to the startup command using --metadata-server .
Buckets and data stored in them while connected to one metadata-server is not cross-accessible with other metadata-servers.

Staging metadata-servers

For staging please use the following metadata-servers;
Location
Identifier
North America
s3.na.staging.storewise.tech:443
Europe
s3.eu.staging.storewise.tech:443
Asia Pacific
s3.ap.staging.storewsie.tech:443
Last modified 9mo ago