Dell DX6012S DX Object Storage Application Guide - Page 44

Scsp Info

Page 44 highlights

Chapter 11. SCSP INFO The following topics in this chapter discuss details about SCSP INFO: • Section 11.1, "Introduction to INFO" • Section 11.2, "Unnamed Object INFO Details" • Section 11.4, "Error Responses to INFO" 11.1. Introduction to INFO This section discusses general information about SCSP INFO that applies to both named and unnamed objects. The INFO message is a request that is identical in semantics to the READ request, except that the content stream, if found, is not returned in the response. If the referenced content is found in the cluster, only the meta-information about that stream is returned in the form of response headers. The INFO request is formatted as a simple HTTP request using the HEAD method as shown in the following examples: • Named object HEAD /mybucket/samplefile.txt HTTP/1.1 Host: cluster.example.com User-Agent: DX Storage Client/0.1 • Unnamed object HEAD /06eec5e2c3f1aadcb41ef7fd52adc049 HTTP/1.1 Host: cluster.example.com User-Agent: DX Storage Client/0.1 11.1.1. Getting Replica Counts The query argument countreps=yes can be used to request that INFO return the number of replicas of a stream that are online in the cluster. This was previously the default behavior but was changed in the 4.0 release so that replicas are not counted unless specifically requested. Therefore, if you wish DX Storage to return the replica count of a stream, you should include the query argument as follows. HEAD /mybucket/samplefile.txt?countreps=yes HTTP/1.1 Host: cluster.example.com User-Agent: DX Storage Client/0.1 11.1.2. Getting Node Status and Cluster Capacity An INFO request submitted without a name or UUID returns 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 in the Admin Console. HEAD / HTTP/1.1 Host: cluster.example.com User-Agent: DX Storage Client/0.1 Copyright © 2010 Caringo, Inc. All rights reserved 39 Version 5.0 December 2010

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81

Copyright © 2010 Caringo, Inc.
All rights reserved
39
Version 5.0
December 2010
Chapter 11. SCSP INFO
The following topics in this chapter discuss details about SCSP INFO:
Section 11.1, “Introduction to INFO”
Section 11.2, “Unnamed Object INFO Details”
Section 11.4, “Error Responses to INFO”
11.1. Introduction to INFO
This section discusses general information about SCSP INFO that applies to both named and
unnamed objects.
The INFO message is a request that is identical in semantics to the READ request, except that the
content stream, if found, is not returned in the response. If the referenced content is found in the
cluster, only the meta-information about that stream is returned in the form of response headers.
The INFO request is formatted as a simple HTTP request using the HEAD method as shown in the
following examples:
Named object
HEAD /mybucket/samplefile.txt HTTP/1.1
Host: cluster.example.com
User-Agent: DX Storage Client/0.1
Unnamed object
HEAD /06eec5e2c3f1aadcb41ef7fd52adc049 HTTP/1.1
Host: cluster.example.com
User-Agent: DX Storage Client/0.1
11.1.1. Getting Replica Counts
The query argument
countreps=yes
can be used to request that INFO return the number of
replicas of a stream that are online in the cluster. This was previously the default behavior but
was changed in the 4.0 release so that replicas are not counted unless specifically requested.
Therefore, if you wish DX Storage to return the replica count of a stream, you should include the
query argument as follows.
HEAD /mybucket/samplefile.txt?countreps=yes HTTP/1.1
Host: cluster.example.com
User-Agent: DX Storage Client/0.1
11.1.2. Getting Node Status and Cluster Capacity
An INFO request submitted without a name or UUID returns 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 in the Admin Console.
HEAD / HTTP/1.1
Host: cluster.example.com
User-Agent: DX Storage Client/0.1