Member since
10-27-2017
16
Posts
0
Kudos Received
0
Solutions
03-16-2018
08:12 AM
@Jay Kumar SenSharma Thanks for your response. It resolves the issue. I realised that once i specify the appId, i can not collect multiple metrics with one call. Is there any workaround wheeeby i can specify appId for some metrics and not others in same call. These metrics are all using same appId (hbase). If i dont specify appId, the call returns the metrics for ams-hbase. Thanks
... View more
03-15-2018
08:31 PM
Hello, i am trying to collect some metrics related to hbase but i keep getting metrics related to ams-hbase. i sent the following request: http://<server>:6188/ws/v1/timeline/metrics?metricNames=master.Server.numDeadRegionServers&appid=hbase and got the following response related to ams hbase: {
"metrics": [{
"timestamp": 1521145230000,
"metadata": {},
"metricname": "master.Server.numDeadRegionServers",
"appid": "ams-hbase",
"starttime": 1521145230000,
"metrics": {
"1521145230000": 0.0
}
}
]
} In the real sense, 2 region servers are down. how do i collect the intended metrics. Thanks
... View more
03-03-2018
12:24 AM
ok, i accepted an answer already. Thanks
... View more
03-02-2018
11:54 PM
Its ok. I am looking at a situation where i collect multiple metrics multiple metrics and extract them for storage in a database. Thanks anyways
... View more
03-02-2018
11:47 PM
@Jay Kumar SenSharma Okay thank you very much. I will to find a way of sorting them then. I appreciate
... View more
03-02-2018
11:21 PM
Hello @Jay Kumar SenSharma, Thanks for your continous help, it has been insightful. Anyways, i have noticed some behaviour while collecting metrics from the API. If for example i make an API call like so, http://*********/ws/v1/timeline/metrics?metricNames=dfs.FSNamesystem.BlockCapacity,dfs.FsVolume.FlushIoRateNumOps,jvm.file_descriptor_usage,Topologies,jvm.JvmMetrics.ThreadsTimedWaiting,jvm.threads.runnable.count,jvm.JvmMetrics.GcCount i get a response which is sorted in a strange manner like this below. Is there a special way API sorts the metrics in the response or is it just a random arrangement. Thanks {
"metrics": [{
"timestamp": 1520030910000,
"metadata": {},
"metricname": "jvm.JvmMetrics.ThreadsTimedWaiting",
"appid": "applicationhistoryserver",
"starttime": 1520030910000,
"metrics": {
"1520030910000": 29.0
}
}, {
"timestamp": 1520030910000,
"metadata": {},
"metricname": "Topologies",
"appid": "nimbus",
"starttime": 1520030910000,
"metrics": {
"1520030910000": 0.0
}
}, {
"timestamp": 1520030910000,
"metadata": {},
"metricname": "dfs.FSNamesystem.BlockCapacity",
"appid": "n
amenode",
"starttime": 1520030910000,
"metrics": {
"1520030910000": 2097152.0
}
}, {
"timestamp": 1520030910000,
"metadata": {},
"metricname": "dfs.FsVolume.FlushIoRateNumOps",
"appid": "datanode",
"starttime": 1520030910000,
"metrics": {
"1520030910000": 0.0
}
}, {
"timestamp": 1520030910000,
"metadata": {},
"metricname": "jvm.file_descriptor_usage",
"appid": "nifi",
"starttime": 1520030910000,
"metrics": {
"1520030910000": 0.04996
}
}, {
"timestamp": 1520030910000,
"metadata": {},
"metricname": "jvm.threads.runnable.count",
"appid": "ambari_server",
"starttime": 1520030910000,
"metrics": {
"1520030910000": 10.0
}
}
]
}
... View more
02-16-2018
10:09 AM
@Jay Kumar SenSharma Oh nice thats very good. Thanks I have also tried to use the wildcard (%) such that it can return all metrics per service but i always end up with an empty json response. Is it wrong to call for metrics as below; http://<ams-host>:6188/ws/v1/timeline/metrics?metricNames=regionServer.%
Thanks for your help
... View more
02-16-2018
04:46 AM
Hello @Jay Kumar SenSharma Thanks for your feedback. Please how do i review the AMS datastore. Using this, can i get all the metrics per service? Thanks
... View more
02-15-2018
07:50 PM
I will like to know if there is any way i can collect all the metrics from the metrics collector API using one request with the format below: http://<AMS_HOST>:6188/ws/v1/timeline/metrics?metricNames=<>&hostname=<>&appId=<>&startTime=<>&endTime=<>&precision=<> Thanks
... View more
Labels:
- Labels:
-
Apache Ambari
11-02-2017
02:08 PM
Thank you very much @Jay Kumar SenSharma I am able to resolve it now Umar
... View more
11-02-2017
12:16 PM
Hello @Jay Kumar SenSharma since these certificates were generated by someone else i will like to delete them and create a fresh set of certificates together with readding the NIFI component to HDP. Kindly help will the proper certificate clearing and creation process. Thanks
... View more
11-02-2017
11:48 AM
Hello @Jay Kumar SenSharma my jdk version is as below. openjdk version "1.8.0_131" When i ran the command to check the certificates, i got the message below before the certificate chain message. CONNECTED(00000003)
depth=1 OU = NIFI, CN = iot-node07.netvisor.local
verify error:num=19:self signed certificate in certificate chain
verify return:0
140187436160928:error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate:s3_pkt.c:1259:SS L alert number 42
140187436160928:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s23_lib.c:184:
--- Finally the permissions of the certificates were -rw------- Thanks
... View more
10-31-2017
03:01 PM
Thanks @Jay Kumar SenSharma i tried what you told me and the keystore password worked. But when i start the NIFI service, i still get the same error. So i tried to reinstall the nifi but i get the error below. 17/10/31 15:57:49 INFO properties.AESSensitivePropertyProvider: AES Sensitive Property Provider decrypted a sensitive value successfully
Attempt to contact NiFi Node https://iot-node07.netvisor.local:9091/nifi did not complete due to exception: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: Path does not chain with any of the trust anchors. Sleeping for 20 sec(s)
2017-10-31 15:58:10,335 - File['/var/lib/ambari-agent/cache/common-services/NIFI/1.0.0/package/files/nifi-toolkit-1.2.0.3.0.0.0-453/bin/node-manager.sh'] {'mode': 0755}
2017-10-31 15:58:13,004 - Will retry 14 time(s), caught exception: Error connecting to one or more nifi nodes: 17/10/31 15:58:11 INFO properties.NiFiPropertiesLoader: Loaded 124 properties from /usr/hdf/current/nifi/conf/nokedli/nifi.properties
17/10/31 15:58:12 INFO properties.ProtectedNiFiProperties: There are 4 protected properties of 5 sensitive properties (100%)
17/10/31 15:58:12 INFO properties.AESSensitivePropertyProvider: AES Sensitive Property Provider decrypted a sensitive value successfully
17/10/31 15:58:12 INFO properties.AESSensitivePropertyProvider: AES Sensitive Property Provider decrypted a sensitive value successfully
17/10/31 15:58:12 INFO properties.AESSensitivePropertyProvider: AES Sensitive Property Provider decrypted a sensitive value successfully
17/10/31 15:58:12 INFO properties.AESSensitivePropertyProvider: AES Sensitive Property Provider decrypted a sensitive value successfully
Attempt to contact NiFi Node https://iot-node07.netvisor.local:9091/nifi did not complete due to exception: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: Path does not chain with any of the trust anchors. Sleeping for 20 sec(s
... View more
10-27-2017
06:37 PM
Hello @Farhad Heybati, While installing NIFI on just one node in a 4-node HDP cluster, will it still be seen as stand-alone installation or it can still be installed in client-server mode. Also, NIFI Certificate authority is also deployed. Thanks
... View more
10-27-2017
05:24 PM
Thanks @Jay SenSharma. I will try this out. To paint a better scenario, its an HDP cluster of 4 nodes but nifi is running on just one of them. Also, NIFI Certificate Authority is also installed. I thought with CA, i wont need to make any changes to the keystore.
... View more
10-27-2017
02:58 PM
Hello guys please i need some help here. A former colleague of mine
installed some HDF services into an existing HDP cluster. The NIFI
service was running fine but the UI wasnt open because the ssl feature
was not completely configured. I followed the guide by configuring the
Initial Admin entity and Node identities but after saving it, NIFI
stopped working and till now i cannot start it. The error below comes up
whenever i start the NIFI service. org.apache.nifi.toolkit.tls.<wbr>service.client.<wbr>TlsCertificateAuthorityClient: Unable to open existing keystore, it can be reused by specifiying both configJson and useConfigJson
Service client error: Keystore was tampered with, or password was incorrect Kindly help me. Also can i use the Ambari to remove a service from the cluster? Thanks
... View more
Labels:
- Labels:
-
Apache Ambari
-
Apache NiFi