liqinwyyx commented on PR #3792: URL: https://github.com/apache/ambari/pull/3792#issuecomment-2205347307
 Here is how I reproduce the problem: 1. Click Remote Cluster, Then click Add button to create a new cluster in Ambari. 2. Modify the remote cluster name from MyRemoteCluster to NewRemoteCluster. 3. After I updated the cluster name, I clicked the deregister remote cluster button and found no response on the page. 4. When I refreshed the page, the cluster I added was still there. So I conclude that this is a bug for remote clusters. 5. Here are my ideas for solving the problem: When I updated the name of the remote cluster, the database was updated. For some reason, the JPA cache was not updated, but the query interface directly looked up the database, so there was no problem. So when I delete the data in the cache and delete it in the database, I find that the data in the cache is inconsistent with the database, so the deletion fails. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
