Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created on
07-08-2024
08:36 AM
- last edited on
04-20-2026
11:28 PM
by
GrazittiAPI
I've got an instance of hue server on my host configured to use infra-solr, and it's tell me that it's got stale configuration on solr_url because the server is changed.
If I restart the hue service for the first minute everything is good, but just some minute later it tells me again that's got stale configuration. The solr_url value isn't changed, there's the same url that was before i restart the service. Seems like it cannot update hue.ini config file
Any help?
Created 07-15-2024 07:11 AM
I don't know how, but I resolved the issue. For some reason i've to install Ranger RMS, but on the host where I've Ranger i don't have enough RAM to take both Ranger and Ranger RMS. So I've migrated Ranger to a new host with enough RAM to run both, and during the migration i've got an error because Postgre reached the maxinum active connection. Later that, the issue was fixed... So i think the cause was the DB
Created 07-08-2024 09:40 AM
@im_al3x Welcome to the Cloudera Community!
To help you get the best possible solution, I have tagged our Hue experts @nramanaiah @dturnau who may be able to assist you further.
Please keep us updated on your post, and we hope you find a satisfactory solution to your query.
Regards,
Diana Torres,Created 07-15-2024 07:11 AM
I don't know how, but I resolved the issue. For some reason i've to install Ranger RMS, but on the host where I've Ranger i don't have enough RAM to take both Ranger and Ranger RMS. So I've migrated Ranger to a new host with enough RAM to run both, and during the migration i've got an error because Postgre reached the maxinum active connection. Later that, the issue was fixed... So i think the cause was the DB