Overview

After the last time I gave up halfway, I talked to my friends about this problem, so I improved it, althoughIn the end it failed.

nacos persist to database

A friend said that it may not be persisted to the database, resulting in too much local memory usage and crashing the system. I think it makes sense and changed it to persist to the database.
Action:

1. Find the sql file and put it in the database
   
   nacos-mysql.sql is required, just import the database
2. Modify the configuration file
   Enter application.properties
   
   Just modify these data, don't forget to delete the previous comments
3. Test
   Add in the upper right corner
   
   

Conclusion

It's definitely not the reason. First of all, I didn't find the statement that database persistence is added, but there is no local persistence; second, data is only added by manual configuration, and the service will not be started, so even if it is, it has no effect.; Third, one more database operation feels that it also increases the pressure on the server.

Continue to reduce jvm parameters and nacos parameters

java -jar -Xms32m -Xmx128m front-1.0-SNAPSHOT.jar

And change the parameters of nacos to 64, 64, 40
This can run two jar packages at the same time, so it is effective

It's still a server reason

But I suddenly found that the interfaces I have been testing all use redis for caching, so I tried many times

1. front.jar+gateway.jar can run common interface
2. See if redis works normally - yes
3. front.jar running the cache interface can run, the cache works normally
4. front.jar+gateway.jar runs the cache interface and crashes directly
5. Use redis first, then run front.jar, everything is normal, start gateway.jar, crash
   So I came to the conclusion that my previous operation was not a problem, simply started too many services, the server can't stand it!!!