Timeout watchdog using a standby thread
http://codereview.stackexchange.com/questions/84697/timeout-watchdog-using-a-standby-thread
he simple but generic timeout class to be used watching for network connections, user input, filesystem events, and is intended to have a very simple interface specific to only our use cases (i.e. no satisfy-all attitude).
Intended steps to use:
- Construct
- Activate
- Potentially react to a timeout, deactivates itself
- Re-activate
- Destruct cleanly
After triggering the alarm the guard is expected to be inactive until explicitly activated. The code expected to be reasonably tested (that is one of the issues).
This posted code as a testable Visual Studio 2013 project lives on the GitHub.
Besides a general feedback on the code quality - or if, please, please, please, you see a bug, I would love to hear about these areas:
Destruction. Although I did my best to tell the guard thread to end, I am still concerned about having to
join()in the destructor. Generally I love my destructors short and sweet for emergency landings - is it possible here? Is there an STL way to brutally kill that thread?Tests. Existing ones test for intended simple scenarios. I am not sure this is enough to claim that the code works as intended. Is it? I did not find a better way to test timing edge cases. Also, as tests are time-dependant, they occasionally spuriously fail when run on slow VMs. Or are they? Is it sufficient for code like this to know that if tests run somewhere consistently? If I increase timeouts the spurious fails go away, but that lengthens the overall project test run.
Below are the current header, implementation, and tests files to save the GitHub trip.
Header:
#pragma once
namespace utility
{
/**
The `clock` alias is for easy switching to `steady_clock` once Microsoft fixes it
*/
typedef std::chrono::system_clock clock;
/**
The `TimeoutGuard` class triggers the `alarm` callback from the `guard_thread`
if `touch` was not called for at least the `timeout` duration.
Because of the way the `guard_thread` sleeps, the actual detection may happen
as late as after `timeout` + `naptime` duration. Hence it is possible that the alarm
will not be called if the `TimeoutGuard` instance is touched within the
'timeout` and `timeout` + `naptime` timeframe.
If not provided, by default the `naptime` is same as `timeout`.
The `TimeoutGuard` is not active after construction, whicn means, that the
`guard_thread` will block until it is activated by calling the `watch` method.
The `TimeoutGuard` class is not copyable and not moveable.
*/
class TimeoutGuard
{
public:
TimeoutGuard(
clock::duration timeout,
std::function<void( void )> alarm,
clock::duration naptime
);
TimeoutGuard(
clock::duration timeout,
std::function<void( void )> alarm
);
~TimeoutGuard();
TimeoutGuard( const TimeoutGuard & ) = delete;
TimeoutGuard & operator=(const TimeoutGuard & ) = delete;
TimeoutGuard( TimeoutGuard && ) = delete;
TimeoutGuard & operator=( TimeoutGuard && ) = delete;
void watch();
void touch();
private:
void guard();
clock::duration timeout;
clock::duration naptime;
std::function<void( void )> alarm;
std::atomic_bool idle;
std::atomic_bool live;
std::atomic<clock::time_point> touched;
std::thread guard_thread;
std::mutex guard_mutex;
std::condition_variable wakeup;
};
}
Here is the implementation:
#include "stdafx.h"
#include "TimeoutGuard.h"
namespace utility
{
TimeoutGuard::TimeoutGuard(
clock::duration timeout,
std::function<void( void )> alarm,
clock::duration naptime
)
: timeout( timeout )
, alarm( alarm )
, naptime( naptime )
{
idle.store( true );
live.store( true );
guard_thread = std::thread( std::bind( &TimeoutGuard::guard, this ) );
}
TimeoutGuard::TimeoutGuard(
clock::duration timeout,
std::function<void( void )> alarm
)
: TimeoutGuard( timeout, alarm, timeout )
{};
TimeoutGuard::~TimeoutGuard()
{
live.store( false );
wakeup.notify_all();
guard_thread.join();
}
void TimeoutGuard::guard()
{
while ( live.load() )
{
if ( idle.load() )
{
// Sleep indefinitely until either told to become active or destruct
std::unique_lock<std::mutex> live_lock( guard_mutex );
wakeup.wait( live_lock, [this]() { return ! this->idle.load() || ! this->live.load(); } );
};
// quit the loop if destructing
if ( ! live.load() ) break;
// the actual timeout checking
auto now = clock::now();
if ( ( now - touched.load() ) > timeout )
{
idle.store( true );
alarm();
continue; // skip waiting for next timeout
}
{
// sleep until next timeout check or destruction
std::unique_lock<std::mutex> live_lock( guard_mutex );
wakeup.wait_for( live_lock, naptime, [this](){ return ! this->live.load(); } );
}
};
}
void TimeoutGuard::watch()
{
touch();
idle.store( false );
wakeup.notify_all();
}
void TimeoutGuard::touch()
{
touched.store( clock::now() );
}
}
And, finally, existing tests:
#include "stdafx.h"
#include "CppUnitTest.h"
#include "TimeoutGuard.h"
using namespace Microsoft::VisualStudio::CppUnitTestFramework;
namespace utility
{
TEST_CLASS( TimeoutGuardTest )
{
public:
bool triggered = false;
void shoud_trigger()
{
triggered = true;
}
TEST_METHOD( TimeoutGuardExpiration )
{
TimeoutGuard tg{
std::chrono::milliseconds{ 5 },
std::bind( &TimeoutGuardTest::shoud_trigger, this )
};
triggered = false;
tg.watch();
std::this_thread::sleep_for( std::chrono::milliseconds{ 10 } );
Assert::IsTrue( triggered, L"Failed to call the timeout alarm on the first run", LINE_INFO() );
triggered = false;
tg.watch();
std::this_thread::sleep_for( std::chrono::milliseconds{ 10 } );
Assert::IsTrue( triggered, L"Failed to call the timeout alarm on the second run", LINE_INFO() );
}
TEST_METHOD( TimeoutGuardNoAlarm )
{
TimeoutGuard tg{
std::chrono::milliseconds{ 5 },
std::bind( &TimeoutGuardTest::shoud_trigger, this )
};
triggered = false;
tg.watch();
std::this_thread::sleep_for( std::chrono::milliseconds{ 1 } );
Assert::IsFalse( triggered, L"Wrongly called the timeout alarm on the first run", LINE_INFO() );
triggered = false;
tg.watch();
for (auto i = 0; i < 10; ++i)
{
std::this_thread::sleep_for( std::chrono::milliseconds{ 1 } );
tg.touch();
}
Assert::IsFalse( triggered, L"Wrongly called the timeout alarm on the second run", LINE_INFO() );
}
};
}
Timeout watchdog using a standby thread的更多相关文章
- Concurrent.Thread.js
(function(){ if ( !this.Data || (typeof this.Data != 'object' && typeof this.Data != 'functi ...
- 多线程爬坑之路-Thread和Runable源码解析
多线程:(百度百科借一波定义) 多线程(英语:multithreading),是指从软件或者硬件上实现多个线程并发执行的技术.具有多线程能力的计算机因有硬件支持而能够在同一时间执行多于一个线程,进而提 ...
- java中多线程中Runnable接口和Thread类介绍
java中的线程时通过调用操作系统底层的线程来实现线程的功能的. 先看如下代码,并写出输出结果. // 请问输出结果是什么? public static void main(String[] args ...
- Thread的run()与start()的区别
Java的线程是通过java.lang.Thread类来实现的.VM启动时会有一个由主方法所定义的线程.可以通过创建Thread的实例来创建新的线程.每个线程都是通过某个特定Thread对象所对应的方 ...
- Thread类源码剖析
目录 1.引子 2.JVM线程状态 3.Thread常用方法 4.拓展点 一.引子 说来也有些汗颜,搞了几年java,忽然发现竟然没拜读过java.lang.Thread类源码,这次特地拿出来晒一晒. ...
- 从源码解读线程(Thread)和线程池(ThreadPoolExecutor)的状态
线程是比进程更加轻量级的调度执行单位,理解线程是理解并发编程的不可或缺的一部分:而生产过程中不可能永远使用裸线程,需要线程池技术,线程池是管理和调度线程的资源池.因为前不久遇到了一个关于线程状态的问题 ...
- HttpClient throws TaskCanceledException on timeout
error msg: HttpClient throws TaskCanceledException on timeout HttpClient is throwing a TaskCanceledE ...
- java Thread 类的源码阅读(oracle jdk1.8)
java线程类的源码分析阅读技巧: 首先阅读thread类重点关注一下几个问题: 1.start() ,启动一个线程是如何实现的? 2.java线程状态机的变化过程以及如何实现的? 3. 1.star ...
- [Java多线程]-Thread和Runable源码解析
多线程:(百度百科借一波定义) 多线程(英语:multithreading),是指从软件或者硬件上实现多个线程并发执行的技术.具有多线程能力的计算机因有硬件支持而能够在同一时间执行多于一个线程,进而提 ...
随机推荐
- 连续小波变换CWT(2)
如果让你说说连续小波变换最大的特点是什么?多分辨分析肯定是标准答案.所谓多分辨分析即是指小波在不同频率段会有不同的分辨率.具体表现形式,我们回到前一篇文章的第一个图, 图一 对应的信号为 低频时(频率 ...
- day19 Dgango进阶 路由系统及 ORM 详解
完成一个完整的网页服务,需要有以下: 再次回顾一下Django 的完成开发流程: 一些值的获取: 对于性别,为互斥属性: 爱好则为多选: 需要使用新的方法 getlist 来获取多个爱好: 单选下拉框 ...
- hdu3374 String Problem 最小最大表示法 最小循环节出现次数
#include <iostream> #include <cstring> #include <cstdio> using namespace std; int ...
- gcc学习记录2——多输入文件
首先有两个.c文件:circle.c和circulararea.c. 分别对两个源文件生成目标文件,circle.o和circulararea.o. gcc -c circle.c circularr ...
- UVALive 5033 I'm Telling the Truth 二分图最大匹配(略有修改)
I - I'm Telling the Truth Time Limit:3000MS Memory Limit:0KB 64bit IO Format:%lld & %llu ...
- Vue2.0 - 生命周期
<!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8 ...
- docker (centOS 7) 使用笔记6 - skydns
skydns被用于kubenets作为DNS服务.本次测试是单独使用skydns作为DNS服务器,且作为loadbalance使用. 前提:需要先安装配置etcd服务 (在前面的文章里,已经安装部署了 ...
- Python 操作 Mysql 模块
一.Python 操作 Mysql 模块的安装 linux: yum install MySQL-python window: http://files.cnblogs.com/files/wupei ...
- python(5)-- 函数
python 函数 定义:函数是组织好的,可重复使用的,用来实现单一,或相关联功能的代码段. 使用好处:函数能提高应用的模块性,和代码的重复利用率. 分类:(1)python 内建函数:pytho ...
- OpenJudge 2727 仙岛求药
总时间限制: 1000ms 内存限制: 65536kB 描述 少年李逍遥的婶婶病了,王小虎介绍他去一趟仙灵岛,向仙女姐姐要仙丹救婶婶.叛逆但孝顺的李逍遥闯进了仙灵岛,克服了千险万难来到岛的中心,发 ...