Multilayer Gmetad Configuration

Experimental results show that multilayer Gmetad is independent of the ganglia version and can be multi-version compatible

Test Ⅰ as follows

Test preparation

* This test has a total of two levels of Gmetad, the ground level is the first stage Gmetad, the upper level is two level Gmetad, the two level Gmetad is 3.1.7 version, the first level Gmetad is 3.7.2 version

* In order to ensure that the information collected by level two Gemtad is indeed Gmetad, not gmond, this test only initiates a Gmond

*gmond node: hdp3

First-level Gmetad node: HDP2

Level two Gmetad node: HDP1

Gweb node: HDP1

Test process:

① configuration file

Hdp1

Cluster {

Name = "HDP3"

Owner = "Unspecified"

Latlong = "Unspecified"

url = "Unspecified"

}

/* The host section describes attributes of the host, like the location */

Host {

Location = "Unspecified"

}

/* Feel free to specify as many udp_send_channels as. Gmond

Used to only support have a single channel */

Udp_send_channel {

#bind_hostname = yes # highly recommended, soon to is default.

# This option tells Gmond to use a source address

# That's resolves to the machine ' s hostname. Without

# This, the metrics could appear to come from any

# interface and the DNS names associated with

# those IPs would be used to create the rrds.

#mcast_join = 239.2.11.71

Host = HDP3 (practice proves that this can only be, not localhost)

Port = 8649

TTL = 1

}

/* You can specify as many udp_recv_channels as. */

Udp_recv_channel {

#mcast_join = 239.2.11.71

Port = 8649

#bind = 239.2.11.71

#retry_bind = True

# Size of the UDP buffer. If You is handling lots of metrics you really

# should bump it up to e.g. 10MB or even higher.

# buffer = 10485760

}

/* You can specify as many tcp_accept_channels as a to share

An XML description of the state of the cluster * *

Tcp_accept_channel {

Port = 8655

# If you want to gzip XML output

Gzip_output = No

}

Hdp2

[Email protected] ganglia]# grep-v ^# gmetad.conf

Data_source "HDP3" hdp3:8655

RRAs "rra:average:0.5:1:244" "rra:average:0.5:24:244" "rra:average:0.5:168:244" "rra:average:0.5:672:244" \

Gridname "Hdp3-grid"

All_trusted on

Setuid_username Ganglia

Xml_port 8651

Interactive_port 8652

Case_sensitive_hostnames 0

Hdp1

[email protected] ganglia]# grep-v ^# gmetad.conf  

Data_source "Hdp3-grid" hdp2:8651

Gridname "Mygrid"

Case_sensitive_hostnames 1

② start

Hdp3:service Gmond Start

Hdp2:service Gmetad Start

Hdp1:service Gmetad Start

Service httpd Start

③ Results Validation

Realize the sub-grid display cluster, in the case of small number of clusters, this is not necessary, but if the cluster is many, all under the same grid cluster display, the page will be very long, very bad to see

But the problem with the grid is that if you want to see a grid under the total grid (that is, the remote grid), you need the grid to open the Gweb service, as

Test Ⅱ as follows

Test preparation

Same test Ⅰ, different points: first level Gmetad is 3.1.7 version, two level Gmetad version is 3.7.2

Testing process

① configuration file

Reference Test Ⅰ-①

② with Test Ⅰ-②

③ Validation Results

Same Test Ⅰ

Multilayer Gmetad Configuration