[23289] Handle maximum deadline misses case (backport #6016)#6097
Merged
juanlofer-eprosima merged 1 commit into2.14.xfrom Oct 16, 2025
Merged
[23289] Handle maximum deadline misses case (backport #6016)#6097juanlofer-eprosima merged 1 commit into2.14.xfrom
juanlofer-eprosima merged 1 commit into2.14.xfrom
Conversation
Contributor
Author
|
Cherry-pick of 3230d1d has failed: To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
12 tasks
Contributor
|
@zesk1999 please solve conflicts here |
juanlofer-eprosima
requested changes
Oct 14, 2025
juanlofer-eprosima
requested changes
Oct 14, 2025
973535e to
ccfb5d5
Compare
ccfb5d5 to
3d5bccd
Compare
Contributor
Author
juanlofer-eprosima
requested changes
Oct 15, 2025
3d5bccd to
dbd3e05
Compare
2f72993 to
5c2753d
Compare
* Refs #23289. Handle maximum deadline misses case. Data writer implementation. Signed-off-by: zesk1999 <zesk1999@gmail.com> * Refs #23289. Handle maximum deadline misses case. Data reader implementation. Signed-off-by: zesk1999 <zesk1999@gmail.com> * Refs #23289. Handle maximum deadline misses case. Tests. Signed-off-by: zesk1999 <zesk1999@gmail.com> --------- Signed-off-by: zesk1999 <zesk1999@gmail.com> (cherry picked from commit 3230d1d) Signed-off-by: zesk1999 <zesk1999@gmail.com> # Conflicts: # src/cpp/fastdds/publisher/DataWriterImpl.cpp # src/cpp/fastdds/publisher/DataWriterImpl.hpp # src/cpp/fastdds/subscriber/DataReaderImpl.cpp # test/blackbox/CMakeLists.txt # test/blackbox/common/BlackboxTestsDeadlineQos.cpp
5c2753d to
7fd176c
Compare
Barry-Xu-2018
pushed a commit
to Barry-Xu-2018/Fast-DDS
that referenced
this pull request
Oct 17, 2025
* Refs #23289. Handle maximum deadline misses case. Data writer implementation. Signed-off-by: zesk1999 <zesk1999@gmail.com> * Refs #23289. Handle maximum deadline misses case. Data reader implementation. Signed-off-by: zesk1999 <zesk1999@gmail.com> * Refs #23289. Handle maximum deadline misses case. Tests. Signed-off-by: zesk1999 <zesk1999@gmail.com> --------- Signed-off-by: zesk1999 <zesk1999@gmail.com> (cherry picked from commit 3230d1d) Signed-off-by: zesk1999 <zesk1999@gmail.com> Co-authored-by: Zeljko Jovanovic <128973134+zesk1999@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR fixes an issue where a DataWriter with a deadline period of 0ms would cause a high CPU load due to an infinite loop of deadline_missed callbacks.
The DataWriterImpl has been modified to handle a 0 as a special case. When this condition is detected:
This ensures that the DataWriter remains stable and responsive, and allows the deadline timer to be properly re-armed if the QoS is later changed to a valid value.
Also, reaching the maximal number of deadline missed messages cancels the timer.
Fixes #23289
@Mergifyio backport 3.3.x 3.2.x 2.14.x
Contributor Checklist
Commit messages follow the project guidelines.
The code follows the style guidelines of this project.
Tests that thoroughly check the new feature have been added/Regression tests checking the bug and its fix have been added; the added tests pass locally
[N/A] Any new/modified methods have been properly documented using Doxygen.
[N/A] Any new configuration API has an equivalent XML API (with the corresponding XSD extension)
Changes are backport compatible: they do NOT break ABI nor change library core behavior.
Changes are API compatible.
[N/A] New feature has been added to the
versions.mdfile (if applicable).[N/A] New feature has been documented/Current behavior is correctly described in the documentation.
Applicable backports have been included in the description.
Reviewer Checklist
This is an automatic backport of pull request #6016 done by [Mergify](https://mergify.com).