Member since
11-27-2022
4
Posts
1
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1251 | 01-25-2023 01:05 AM |
03-06-2025
09:34 PM
Possible Causes & Solutions: 1. Token Expired The error message shows the token’s maxDate=2025-03-13T06:57:54.532Z, which means it is valid until March 13, 2025. However, if the token was already expired or incorrectly renewed, it would cause this failure. Solution: Check token validity using the klist command: klist -e If expired, renew the token manually: hdfs dfs -renewDelegationToken <token> 2. Incorrect or Missing Kerberos Credentials If the application is running on a Kerberized cluster, YARN must have a valid Kerberos ticket. Solution: Ensure the Kerberos ticket is valid: If the ticket is expired, re-authenticate: kinit -kt /etc/security/keytabs/yarn.service.keytab yarn/<hostname>@PLATFORMKRB.COM 3. Incorrect Token Renewer Principal The error message includes: renewer=yarn This means the token was issued for YARN to renew, but YARN may not have the required permissions. Solution: Ensure the renewer principal is correctly configured in core-site.xml: <property>
<name>hadoop.security.auth_to_local</name>
<value>RULE:[1:$1@$0](yarn@PLATFORMKRB.COM)s/.*/yarn/</value>
</property> Restart YARN after making changes. 4. Misconfigured Ozone Token in YARN If the Ozone token is not being properly renewed, you may need to refresh it. Solution: Try manually obtaining a new Ozone token: hdfs fetchdt -fs o3fs://<bucket>.<volume>/<host>:9862 <token-file> Pass the token explicitly when running the application. 5. OM (Ozone Manager) Certificate or Service ID Issues The error mentions omServiceId=<hostname> and omCertSerialId=6. If the OM certificate has expired or the service ID is incorrect, it can prevent token renewal. Solution: Check if the OM certificate is valid: ozone admin cert list If expired, renew the certificates and restart OM. 6. Mismatched Ozone and YARN Versions If the Ozone and YARN versions are incompatible, token renewal may fail. Solution: Check the Ozone and YARN versions: ozone version
yarn version Ensure they are compatible. Next Steps: a. Check if the Kerberos ticket is valid (klist). b. Try renewing the token manually (hdfs dfs -renewDelegationToken). c. Ensure the correct renewer principal is configured in YARN. d. Verify Ozone Manager certificates (ozone admin cert list). e. Restart YARN and OM after making changes.
... View more
01-25-2023
01:05 AM
Ok guys, I figured this out myself: curl -ikv --negotiate -u: https://dev-ran-7.dev-ran.root.hwx.site:8995/solr/ranger_audits/select -d ' q=*:*&wt=json&fl=access%2C%20agent%2C%20repo%2C%20resource%2C%20resType%2C%20event_count&fq=access%3Aread&fq=repo%3Acm_ozone&fq=-repoType%3A7&fq=resType%3Akey&fq=evtTime%3A%5B2023-01-23T18%3A30%3A00Z+TO+NOW%5D& json.facet={ resources:{ type : terms, field : resource, facet:{ read_access_count : "sum(event_count)" } } }'
... View more
01-25-2023
12:21 AM
Hello guys, Can someone please help me, how I can write a solr query where results to be grouped on one field (text type) and sum on another field. Here is my documents results: { "responseHeader": { "zkConnected": true, "status": 0, "QTime": 30, "params": { "q": "*:*", "doAs": "knoxui", "fl": "access, agent, repo, resource, resType, event_count", "fq": [ "access:read", "repo:cm_ozone", "resType:key", "action:read" ], "_forwardedCount": "1", "_": "1674633786010" } }, "response": { "numFound": 8, "start": 0, "docs": [ { "access": "read", "agent": "ozone", "repo": "cm_ozone", "resource": "volume1/fso-bucket/dir1/dir2/dir3", "resType": "key", "event_count": 1 }, { "access": "read", "agent": "ozone", "repo": "cm_ozone", "resource": "volume1/fso-bucket/dir1", "resType": "key", "event_count": 1 }, { "access": "read", "agent": "ozone", "repo": "cm_ozone", "resource": "volume1/fso-bucket/dir1/test3.txt", "resType": "key", "event_count": 1 }, { "access": "read", "agent": "ozone", "repo": "cm_ozone", "resource": "volume1/fso-bucket/dir1/dir2", "resType": "key", "event_count": 1 }, { "access": "read", "agent": "ozone", "repo": "cm_ozone", "resource": "volume1/fso-bucket/dir1/dir2/dir3", "resType": "key", "event_count": 1 }, { "access": "read", "agent": "ozone", "repo": "cm_ozone", "resource": "volume1/fso-bucket/dir1", "resType": "key", "event_count": 1 }, { "access": "read", "agent": "ozone", "repo": "cm_ozone", "resource": "volume1/fso-bucket/dir1/test3.txt", "resType": "key", "event_count": 1 }, { "access": "read", "agent": "ozone", "repo": "cm_ozone", "resource": "volume1/fso-bucket/dir1/dir2", "resType": "key", "event_count": 1 } ] } } Here I need something like equivalent to SQL: select resource, count(event_count) from <docs> group by resource;
... View more
Labels:
- Labels:
-
Apache Solr