How did the value in open files shown in SequoiaDB v2.8.4 come from?
This article mainly introduces "how does the value in open files shown in SequoiaDB v2.8.4 come from". In daily operation, I believe that many people have doubts about how to get the value in open files displayed in SequoiaDB v2.8.4. The editor consulted all kinds of data and sorted out a simple and useful method of operation. I hope it will be helpful to answer the question of "how does the value in open files shown in SequoiaDB v2.8.4 come from?" Next, please follow the editor to study!
[detailed description of the problem]
Where did the value in the open files shown in the node log in SequoiaDB v2.8.4 come from? The open files value displayed when the node was started on June 10 was the same as that set by ulimit.conf, which was 1048576, but on June 17, when the node was started this morning, the open files value was 4096.
[problem troubleshooting]
(take sdbadmin, the default user to which sequoiadb belongs as an example)
1. Confirm whether / proc/ [cm_pid] / limits is started with sdbadmin, and confirm the current value of / proc/ [cm_pid] / limits
From user: sdbcm open files of all hosts is 4096
2. If you execute the parameter. / bin/sdbstart plus-I, you will skip limits.conf and confirm the sequoiadb startup mode based on the ulimit-n in the current linux session.
From user: the customer executes the sdbstop command in the morning to show that the 11820 node (this node is the node of the above mentioned node log) fails to stop, and kill-9 the node that starts and stops using sdbadmin / sdbstart
3. Confirm whether the catalog node (such as 11820) is automatically pulled by CM, when the CM process is started, and if it is bin/sdbcmart-I, skip ulimit.conf.
From user: 11820 is pulled by cm, and the cm process is 2018-05-14. The last modification time of the cm file is 2017-12-04.
[solution]
Because the open files of the sdbcm node is 4096 and the 11820 node is dropped by kill and pulled by sdbcm; in addition, the setting of troubleshooting ulimit is also correct. There is no follow-up feedback log and more problem progress from the customer, and the cause of the problem is not found.
It is normal after the customer restarts sdbcm.
At this point, the study on "how to get the values in the open files shown in SequoiaDB v2.8.4" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!
