当前位置: 首页 > news >正文

erlang学习:gen_server书上案例22.6练习题5

检查是否有懒惰的工人,也就是接受工作但不按时完成的进程。把任务请求函数修改为
返回{JobNumber, JobTime, F},其中JobTime是工人必须完成任务的秒数。如果工人在JobTime

  • 1时还未完成任务,服务器就应当向其发送一个hurry_up(快点儿)消息,而在JobTime + 1
    时应该用调用exit(Pid, youre_fired)(你被解雇了)来杀掉这个工人进程。

在上次添加工作的方法中记录了JobTime字段,如果执行超时的话就按照hurry_up催促逻辑进行催促输出

-module(gen_server_test).-export([start_link/0, add_job/3, work_wanted/0, job_done/1,hurry_up/1,statistics/0]).
-export([init/1, handle_call/3, handle_cast/2, handle_info/2,terminate/2, code_change/3]).
-export([test_job_centre/0]).
-define(SERVER, ?MODULE).%%创建一个记录,记录中包含了一个工作队列,与下一个工作任务编号
-record(state,
{jobs = queue:new(),next_job_number = 1,workers = gb_sets:new(),completed_jobs = gb_sets:new()
}).start_link() ->gen_server:start_link({local, ?SERVER}, ?MODULE, [], []).
add_job(Fun,WorkerPid,JobTime) ->gen_server:call(?SERVER, {add_job, Fun,WorkerPid,JobTime}).
work_wanted() ->gen_server:call(?SERVER, work_wanted).
job_done(JobNumber) ->gen_server:call(?SERVER, {job_done, JobNumber}).
hurry_up(WorkerPid) ->  %gen_server:call(?SERVER, {hurry_up, WorkerPid}).
statistics() ->gen_server:call(?SERVER, statistics).
%%---------------------------------------------------------------------------
init([]) ->{ok, #state{}}.handle_call({add_job, Fun,WorkerPid,JobTime}, _From, State) ->%%向队列中添加元素,队列的任务为执行Fun中的操作NewJobs = queue:in({State#state.next_job_number,JobTime,Fun}, State#state.jobs),%%执行任务函数Fun(),NewWorkers = gb_sets:add(WorkerPid, State#state.workers),% 建立与工人的连接link(WorkerPid),{reply, State#state.next_job_number,State#state{jobs = NewJobs,next_job_number = State#state.next_job_number + 1,workers = NewWorkers}};
handle_call(work_wanted, _From, State) ->IsEmpty = queue:is_empty(State#state.jobs),case IsEmpty oftrue ->{reply, no, State};false ->{{value, {JobNumber, JobTime,Fun}}, NewJobs} = queue:out(State#state.jobs),spawn_link(fun() -> track_job(JobTime, self(),State) end),{reply, {JobNumber, JobTime, Fun}, State#state{jobs = NewJobs}}end;
handle_call({job_done, JobNumber}, _From, State) ->NewCompletedJobs = gb_sets:add(JobNumber, State#state.completed_jobs),{reply, ok, State#state{completed_jobs = NewCompletedJobs}};
handle_call({hurry_up, WorkerPid}, _From, State) ->% 这里可以发送"hurry_up"消息给WorkerPidio:format("Worker ~p is being asked to hurry up~n", [WorkerPid]),{reply, ok, State};
handle_call(statistics, _From, State) ->{reply, #{waiting => queue:len(State#state.jobs),in_progress => gb_sets:size(State#state.workers),completed => gb_sets:size(State#state.completed_jobs)}, State};
handle_call(Request, _From, State) ->{reply, {error, {unknown_request, Request}}, State}.handle_cast(_Msg, State) ->{noreply, State}.
handle_info({exit, WorkerPid, _Reason}, State) ->%% 如果工人进程崩溃,则从workers集合中移除,并将任务重新添加到队列NewWorkers = gb_sets:delete(WorkerPid, State#state.workers),%% 查找并重新添加任务{ok, Fun} = find_task_for_worker(WorkerPid, State#state.jobs),NewJobs = queue:in({State#state.next_job_number - 1, Fun}, State#state.jobs),{noreply, State#state{workers = NewWorkers, jobs = NewJobs}};
handle_info(_Info, State) ->{noreply, State}.terminate(_Reason, _State) ->ok.code_change(_OldVsn, State, _Extra) ->{ok, State}.track_job(JobTime, WorkerPid,State) ->timer:sleep(JobTime - 1),case gb_sets:is_member(WorkerPid, State#state.workers) oftrue ->gen_server:call(?SERVER, {hurry_up, WorkerPid});false ->ok  % 工人已经完成了任务或被解雇end,timer:sleep(2),case gb_sets:is_member(WorkerPid, State#state.workers) oftrue ->exit(WorkerPid, youre_fired);false ->ok  % 工人已经完成了任务或被解雇end.
find_task_for_worker(WorkerPid, Jobs) ->case gb_sets:is_member(WorkerPid, gb_sets:from_list(Jobs)) oftrue ->%% 找到对应的任务{value, {_, Fun}} = queue:out(Jobs),{ok, Fun};false ->{error, not_found}end.
test_job_centre() ->%%创建两个任务Job1 = fun() ->io:format("Doing job 1~n")end,Job2 = fun() ->io:format("Doing job 2~n")end,%%将两个任务放入任务队列中JobNumber1 = add_job(Job1,self(),5),io:format("Job number 1 is ~p~n", [JobNumber1]),JobNumber2 = add_job(Job2,self(),10),io:format("Job number 2 is ~p~n", [JobNumber2]),%%工人领取任务队列任务{JobNumber1, JobTime1,Job1} = work_wanted(),io:format("Doing job ~p with time limit ~p~n", [{JobNumber1, Job1}, JobTime1]),{JobNumber2, JobTime2, Job2} = work_wanted(),io:format("Doing job ~p with time limit ~p~n", [{JobNumber2, Job2}, JobTime2]),%% 测试hurry_up方法hurry_up(self()),%% 模拟超时情况timer:sleep(6),  % 等待超过Job1的时间限制receive{hurry_up, _} ->io:format("Received hurry up message~n")after 1000 ->  % 超时时间io:format("No hurry up message received~n")end,job_done(JobNumber1),job_done(JobNumber2),case work_wanted() ofno ->io:format("No more jobs~n");{JobNumber, Job} ->io:format("Doing job ~p~n", [{JobNumber,Job}])end,exit(normal),ok.

代码执行结果,由于等待了6毫秒,导致工程一已经接近超时,因此发送了hurry_up请求,但是工程2还有4毫秒,因此并没有发送相应请求,因此一个输出了被请求的线程名称,一个输出没有接收到请求。
请添加图片描述


http://www.mrgr.cn/news/12851.html

相关文章:

  • Obsidian dataview 高级使用技巧 【文件筛选/排序/分组/限制】
  • CSS3中display显示属性
  • 前后端交互的过程
  • 【生活英语】3、支持和鼓励
  • 弗洛伊德(Floyd)算法(C/C++)
  • CMake构建学习笔记9-Eigen库的构建
  • Oracle Linux 7.9 安装minikube体验
  • C++中 inline 的含义是什么?
  • iptables笔记汇总
  • centos 部署 scrapy 爬虫详细教程
  • [论文笔记] LLM-ICL论文:AI模型对prompt格式分隔符的敏感性——结构化Prompt格式
  • 报表融合大屏,做不一样的财务分析!
  • 不可不知的DP协议过往史
  • vue el-tree主键id重复 添加自增id 以及原相同节点同步勾选 同步操作
  • 关于技术专项工作的梳理和总结
  • UDP是什么?UDP攻击为什么这么大?该如何防范?
  • vue使用vite配置跨域以及环境配置详解
  • Linux磁盘操作之du命令
  • 基于数据挖掘的心力衰竭疾病风险评估系统
  • WHAT - 通过 react-use 源码学习 React(Lifecycles 篇)