Scsp Read; Introduction To Read; Reading With Content Validation; Requestion Node Status And Cluster Capacity - Dell DX6000 Application Manual
Dx object storage application guide version 5.0
Hide thumbs
Also See for DX6000:
- Hardware owner's manual (198 pages) ,
- Getting started with your system (124 pages) ,
- Administration manual (74 pages)
Table of Contents
Advertisement
Chapter 5. SCSP READ
The following topics in this chapter discuss details about SCSP READ:
•
Section 5.1, "Introduction to READ"
•
Section 5.2, "Unnamed Object READ Details"
•
Section 5.3, "Normal Responses to READ"
•
Section 5.4, "Error Responses to READ"
5.1. Introduction to READ
This section discusses general information about SCSP READ that applies to both named and
unnamed objects.
The READ message is a request for a specific content stream to be returned from a DX Storage
cluster. It is formatted as a simple HTTP request using the GET method as shown in the following
examples.
• Named object:
GET /mybucket/samplefile.txt HTTP/1.1
Host: cluster.example.com
User-Agent: DX Storage Client/0.1
• Unnamed object:
GET /12BFEA648C2697A56FD5618CAE15D5CA HTTP/1.1
Host: cluster.example.com
User-Agent: DX Storage Client/0.1
DX Storage makes no assumptions about User-Agent (except that it is an HTTP/1.1 client). The
Host header is mandatory and must conform to the requirements of
specification.
5.1.1. Reading With Content Validation
To validate the stream content as it is being read, you must add the query argument ?
validate=yes to the URI. The content digest is then be computed and compared at the end. A
hash mismatch will cause the socket connection to be dropped before the final bytes are sent.
GET /name-or-uuid?validate=yes HTTP/1.1
Host: cluster.example.com
User-Agent: DX Storage Client/0.1
5.1.2. Requestion Node Status and Cluster Capacity
A READ request can be submitted without a name or UUID as follows to return counts for high-level
node operations (read, write, delete, and so on), as well as cluster-wide Space Available and Total
Capacity values. This information is also available on the Node Status page shown when navigating
to a node's IP address with the designated SCSP port (for example, http://192.168.99.100:80).
GET / HTTP/1.1
Host: cluster.example.com
Copyright © 2010 Caringo, Inc.
All rights reserved
Section 14.23
22
of the HTTP/1.1
Version 5.0
December 2010
Advertisement
Table of Contents
