YottaDB / YDB

Mirrored from https://gitlab.com/YottaDB/DB/YDB
Other
76 stars 37 forks source link

Argumentless MUPIP RUNDOWN should record in syslog the orphaned jnlpool ipcs (semid/shmid) that it removes #266

Open nars1 opened 6 years ago

nars1 commented 6 years ago

Final Release Note

Description

MUPIP RUNDOWN with no arguments examines all ipcs in the system (semaphores and shared memory segments) and removes any if finds are created by YottaDB if they are orphaned (i.e. no processes have interest in them). Currently, the argumentless rundown records the ipcs that it removes corresponding to database files in the form of SEMREMOVED and SHMREMOVED messages to the syslog. But it does not do this for journal pool ipcs that it removes. It would be desirable to have this recorded (e.g. in case an ipc disappears mysteriously, seeing it in the syslog would help confirm it is an argumentless rundown that removed it).

Draft Release Note

MUPIP RUNDOWN with no arguments records (in the syslog) the ids of orphaned semaphore and shared memory segments (corresponding to the journal and receive pool) that it removes in the form of SEMREMOVED/SHMREMOVED messages. Previously it did this recording only for database file ipcs and not for journal/receive pool ipcs making it harder for one to know why a journal pool semid/shmid suddenly disappeared.