Activity for PhanTranQuocDat
-
PhanTranQuocDat created ticket #3363
ntf: introduce new configured variable for logger records timeout
-
ntf: crash when remove overdue notification
-
commit 7b80b26c5ac19135820854a6edc6d50a5dea82dc (HEAD -> develop, origin/develop, ticket-3350) Author: dat.tq.phan dat.tq.phan@dektech.com.au Date: Thu Apr 11 11:22:32 2024 +0700 ntf: check existed notification before retrieving [#3350] Related to ticket #3349, when ntf removes an overdue notification from logger buffer, it will try to retrieve next notification in queue. In case there's only a single notification in queue and it's overdue, after removing it, ntf will try to retrieve non-existed...
-
ntf: crash when remove overdue notification
-
ntf: check existed notification before retrieving [#3350]
-
ntf: check existed notification before retrieving [#3350]
-
ntf: crash when remove overdue notification
-
ntf: crash when remove overdue notification
-
ntf: crash when remove overdue notification
-
ntf: ntfd cannot handle notification when logd overload
-
commit ad744c90e242272fe78ba09694e41de5eb164455 (HEAD -> develop, origin/develop, ticket-3349) Author: dat.tq.phan dat.tq.phan@dektech.com.au Date: Mon Apr 1 17:13:53 2024 +0700 amf: move ntf job to the end of queue [#3349] When AMF sends job to NTF but NTF is busy with full buffer, AMF will be stuck and unable to process other jobs. Solution is to move the front NTF job to the end of queue when NTF is busy and continue to process other jobs. commit e58044b667bcc6c8b776d30fa04dbbbfdb49ebde Author:...
-
ntf: ntfd cannot handle notification when logd overload
-
ntf: ntfd cannot handle notification when logd overload
-
amf: move ntf job to the end of queue [#3349]
-
ntf: remove overdue notification from logger buffer [#3349]
-
ntf: ntfd cannot handle notification when logd overload [#3349]
-
ntf: ntfd cannot handle notification when logd overload [#3349]
-
ntf: ntfd cannot handle notification when logd overload
-
commit 7c5bcb15d96ca1ed042e0403f2971e9ffcbf5da2 (HEAD -> ticket-3337, origin/develop) Author: dat.tq.phan dat.tq.phan@dektech.com.au Date: Wed Apr 26 16:31:48 2023 +0700 mds: fix coredump when run mdstest using mds q_ownership [#3337] This fix will remove a wrong freeing when mds recevies message. Message buffer will only be freed by upper layer receiver.
-
mds: mdstest api coredump when when use MDS queue ownership
-
For more information, this ticket is related to ticket-3331, the commit: b65c0887f7d9f240573b7067110cdccb03e79397 Initially, the deallocation added to fix AMF Valgrind report, but deallocate memory in MDS lower layer is not right as it may delete messages before they are read by upper layers. So upper layers must deallocate memory after messages has been read (this point was full-filled from #3331, so remove the wrong memory deallocation in this case will not raise the issue from #3331).
-
imm: Valgrind reported errors
-
mds: mdstest api coredump when when use MDS queue ownership
-
For more information, this ticket is related to ticket-3331, the commit: b65c0887f7d9f240573b7067110cdccb03e79397 Initially, the deallocation added to fix AMF Valgrind report, but deallocate memory in MDS lower layer is not right as it may delete messages before they are read by upper layers. So upper layers must deallocate memory after messages has been read (this point was full-filled from #3331, so remove the wrong memory deallocation in this case will not raise the issue from #3331).
-
mds: mdstest api coredump when when use MDS queue ownership
-
mds: fix coredump when run mdstest using mds q_ownership [#3337]
-
mds: mdstest api coredump when when use MDS queue ownership
-
mds: mdstest api coredump when when use MDS queue ownership
-
rde: Valgrind reported errors
-
commit a1fcc05d5efc497c2aab3ec52ff697167c43c224 Author: dat.tq.phan dat.tq.phan@dektech.com.au Date: Tue Mar 28 10:22:14 2023 +0700 rde: fix errors reported by Valgrind [#3333] Fix memleak detected by Valgrind when receive rde message. Also fix the uninitialized value(s).
-
rde: Valgrind reported errors
-
rde: fix errors reported by Valgrind [#3333]
-
imm: Valgrind reported errors
-
imm: Fix errors reported by valgrind [#3335]
-
imm: Valgrind reported errors
-
rde: fix errors reported by Valgrind [#3333]
-
rde: Valgrind reported errors
-
amf: Fix errors reported by valgrind (cont-part 3) [#3331]
-
amf: Fix errors reported by valgrind (cont-part 3) [#3331]
-
Valgrind reports errors
-
commit df7e4e8e33363ddcac19538370c7d29e768f7d4f (origin/develop) Author: dat.tq.phan dat.tq.phan@dektech.com.au Date: Mon Mar 20 10:47:19 2023 +0700 amf: Fix errors reported by valgrind (cont) [#3331] This is the continous fix for valgrind report. The commit will fix memleak when trigger switch-over.
-
amf: Fix errors reported by valgrind (cont) [#3331]
-
Valgrind reports errors
-
Valgrind reports errors
-
commit b65c0887f7d9f240573b7067110cdccb03e79397 (HEAD -> develop, origin/develop) Author: dat.tq.phan dat.tq.phan@dektech.com.au Date: Wed Mar 1 09:53:44 2023 +0700 amf: Fix errors reported by valgrind [#3331] Valgrind reports errors while run amf tests. This ticket fixes errors from the report.
-
Valgrind reports errors
-
amf: Fix errors reported by valgrind [#3331]
-
Valgrind reports errors
-
amf: Fix errors reported by valgrind [#3331]
-
amf: Fix errors reported by valgrind [#3331]
-
Valgrind reports errors
-
Valgrind reports errors
-
amf: Fix errors reported by valgrind [#3331]
-
Valgrind reports errors
-
imm: immnd crashes due to NFS state unsynced
-
commit bb193b9154084ee57164e3783f7499fbc1443a9a (HEAD -> develop, origin/develop) Author: dat.tq.phan dat.tq.phan@dektech.com.au Date: Mon Feb 13 13:41:03 2023 +0700 imm: Make NFS state consistent among nodes [#3330] There is a case that the ccb apply not run on some nodes due to NFS unavailable. Then it causes the mismatch state in complete ack. Solution is to make NFS state consistent among nodes Also this commit combines three similar function into one.
-
imm: immnd crashes due to NFS state unsynced
-
imm: Make NFS state consistent among nodes [#3330]
-
imm: Make NFS state consistent among nodes [#3330]
-
imm: Wait for NFS available before processing ccb [#3330]
-
imm: immnd crashes due to NFS state unsynced
-
imm: Ccb state unsynced after split-brain
-
base: increase buffer size for users in group [#3316]
-
base: increase buffer size for users in group [#3316]
-
base: increase buffer size for users in group [#3316]
-
base: increase buffer size for users in group [#3316]
-
base: increase buffer size for users in group [#3316]
-
base: increase buffer for list of members in a group
-
Description has changed:
-
Description has changed: Diff: --- old +++ new @@ -1,6 +1 @@ When access imm, a user needs to be authenticated to be superuser or a member of authorized group. In case authorized group has too many users, the default system buffer is insufficient to contain leading to error: Numerical result out of range. -
-
base: increase buffer for list of members in a group
-
base: increase buffer for list of members in a group
-
base: increase buffer for list of members in a group
-
commit e456726385781f96dde2accb2f75f90414c4c8a5 (HEAD -> develop, origin/develop) Author: dat.tq.phan dat.tq.phan@dektech.com.au Date: Thu Dec 16 17:42:30 2021 +0700 amf: Correct HC period to make it effect immediately[#3298] Restart healthcheck timer after changing saAmfHctDefPeriod to make them take effect immediately.
-
amf: change saAmfHctDefPeriod not take effect immediately
-
amf: change saAmfHctDefPeriod/saAmfHctDefMaxDuration not take effect immediately
-
attach patch: Restart healthcheck timer after changing saAmfHctDefPeriod to make it take effect immediately
-
amf: change saAmfHctDefPeriod/saAmfHctDefMaxDuration not take effect immediately
-
amf: Restart healthcheck timer after changing saAmfHctDefPeriod/saAmfHctDefMaxDuration [#3298]
-
amf: change saAmfHctDefPeriod/saAmfHctDefMaxDuration not take effect immediately
1
