Database Reference
In-Depth Information
<arguments>… -classpath
…;C:\Ambari\metrics-sink-1.2.5.0.9.0.0-
60.jar;C:\Ambari\sqljdbc4.jar </arguments>
In other words, add both the metrics-sink and sqljdbc4 paths to the
classpath so that they are locatable by the service. You may have more
success putting them at the front of the class path rather than
appending them. One way to find the correct files for the addition of
these paths is to search for *.xml files within the
bin
folder. Each one of
these files needs to be updated. Also, pay attention to the metrics-sink
version number and change it as appropriate. You may have a newer
metrics-sink file version than in the Ambari documentation or listed
here in this chapter. Finally, if you have a multiple node cluster, don't
forget to do this on each node in the cluster.
3. Restart Hadoop. From a command prompt, run
stop_local_hdp_services.cmd
and then run
start_local_hdp_services.cmd.
If your cluster is more than one
node, be sure to also run
stop_remote_hdp_services.cmd
and
start_remote_hdp_services.cmd
.
If everything was successful, all your services will start back up as
expected.
4. To verify metrics collection, connect to the SQL Server where you
installed HadoopMetrics and run the following query:
SELECT * FROM HadoopMetrics.dbo.MetricRecord
If you are successfully collecting metrics, you will have a result set from this
query.
Installing and Configuring the Ambari SCOM Server
Now it is time to install and configure the Ambari SCOM Server within your
Hadoop cluster:
1. Determine which node in the cluster you will be running the Ambari
SCOM Server. In our single node cluster from Chapter 3, we'll install it
along with the other services. In an enterprise cluster, you will want to
install this on another node within the cluster.
