22-职责链(Chain of Resposibility)

本文深入探讨了职责链设计模式的定义、适用场景及其在软件工程中的应用。通过实例演示了如何利用职责链模式实现请求处理的解耦,增强系统的灵活性。

职责链(Chain of Resposibility)

1. 定义

使多个对象都有机会处理请求,从而避免请求的发送者和接收者之间的耦合关系。将这些对象连成一条链,并沿着这条链传递请求,直到有一个对象处理它为止。

2. 适用场景

  • 在软件构建过程中,一个请求可能被多个对象处理,但是每个请求在运行时只能有一个接受者,如果显式指定,将必不可少地带来请求发送者与接受者的紧耦合。
  • 如何使请求的发送者不需要指定具体的接受者?让请求的接受者自己在运行时决定来处理请求, 从而使两者解耦。

3. 要点总结

  • Chain of Resposibility 模式的应用场合在于“一个请求可能有多个接受者,但是最后真正的接受者只有一个”,这时候请求发送者与接受者的耦合可能出现“变化脆弱”的症状,职责链的目的就是将二者解耦,从而更好地应对变化
  • 应用了Chain of Resposibility模式后,对象的职责分派将更具灵活性。我们可以在运行时动态添加/修改请求者的处理职责。
  • 如果请求传递到职责链的末尾仍得不到处理,应该有一个合理的缺省机制。这也是每个接受对象的责任,而不是发出请求的对象的责任。

4. Demo

enum class RequestType
{
    REQ_HANDLER1,
    REQ_HANDLER2,
    REQ_HANDLER3
};

class Reqest
{
    string description;
    RequestType reqType;
public:
    Reqest(const string & desc, RequestType type) : description(desc), reqType(type) {}
    RequestType getReqType() const { return reqType; }
    const string& getDescription() const { return description; }
};

class ChainHandler{
    
    ChainHandler *nextChain;
    void sendReqestToNextHandler(const Reqest & req)
    {
        if (nextChain != nullptr)
            nextChain->handle(req);
    }
protected:
    virtual bool canHandleRequest(const Reqest & req) = 0;
    virtual void processRequest(const Reqest & req) = 0;
public:
    ChainHandler() { nextChain = nullptr; }
    void setNextChain(ChainHandler *next) { nextChain = next; }
    
   
    void handle(const Reqest & req)
    {
        if (canHandleRequest(req))
            processRequest(req);
        else
            sendReqestToNextHandler(req);
    }
};

class Handler1 : public ChainHandler{
protected:
    bool canHandleRequest(const Reqest & req) override
    {
        return req.getReqType() == RequestType::REQ_HANDLER1;
    }
    void processRequest(const Reqest & req) override
    {
        cout << "Handler1 is handle reqest: " << req.getDescription() << endl;
    }
};
        
class Handler2 : public ChainHandler{
protected:
    bool canHandleRequest(const Reqest & req) override
    {
        return req.getReqType() == RequestType::REQ_HANDLER2;
    }
    void processRequest(const Reqest & req) override
    {
        cout << "Handler2 is handle reqest: " << req.getDescription() << endl;
    }
};

class Handler3 : public ChainHandler{
protected:
    bool canHandleRequest(const Reqest & req) override
    {
        return req.getReqType() == RequestType::REQ_HANDLER3;
    }
    void processRequest(const Reqest & req) override
    {
        cout << "Handler3 is handle reqest: " << req.getDescription() << endl;
    }
};

int main(){
    Handler1 h1;
    Handler2 h2;
    Handler3 h3;
    h1.setNextChain(&h2);
    h2.setNextChain(&h3);
    
    Reqest req("process task ... ", RequestType::REQ_HANDLER3);
    h1.handle(req);
    return 0;
}

本专栏文章:

#!/bin/sh # Copyright Abandoned 1996 TCX DataKonsult AB & Monty Program KB & Detron HB # This file is public domain and comes with NO WARRANTY of any kind # MySQL daemon start/stop script. # Usually this is put in /etc/init.d (at least on machines SYSV R4 based # systems) and linked to /etc/rc3.d/S99mysql and /etc/rc0.d/K01mysql. # When this is done the mysql server will be started when the machine is # started and shut down when the systems goes down. # Comments to support chkconfig on RedHat Linux # chkconfig: 2345 64 36 # description: A very fast and reliable SQL database engine. # Comments to support LSB init script conventions ### BEGIN INIT INFO # Provides: mysql # Required-Start: $local_fs $network $remote_fs # Should-Start: ypbind nscd ldap ntpd xntpd # Required-Stop: $local_fs $network $remote_fs # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: start and stop MySQL # Description: MySQL is a very fast and reliable SQL database engine. ### END INIT INFO # If you install MySQL on some other places than /usr/local/mysql, then you # have to do one of the following things for this script to work: # # - Run this script from within the MySQL installation directory # - Create a /etc/my.cnf file with the following information: # [mysqld] # basedir=<path-to-mysql-installation-directory> # - Add the above to any other configuration file (for example ~/.my.ini) # and copy my_print_defaults to /usr/bin # - Add the path to the mysql-installation-directory to the basedir variable # below. # # If you want to affect other MySQL variables, you should make your changes # in the /etc/my.cnf, ~/.my.cnf or other MySQL configuration files. # If you change base dir, you must also change datadir. These may get # overwritten by settings in the MySQL configuration files. basedir= datadir= # Default value, in seconds, afterwhich the script should timeout waiting # for server start. # Value here is overriden by value in my.cnf. # 0 means don't wait at all # Negative numbers mean to wait indefinitely service_startup_timeout=900 # Lock directory for RedHat / SuSE. lockdir='/var/lock/subsys' lock_file_path="$lockdir/mysql" # The following variables are only set for letting mysql.server find things. # Set some defaults mysqld_pid_file_path= if test -z "$basedir" then basedir=/usr/local/mysql bindir=/usr/local/mysql/bin if test -z "$datadir" then datadir=/usr/local/mysql/data fi sbindir=/usr/local/mysql/bin libexecdir=/usr/local/mysql/bin else bindir="$basedir/bin" if test -z "$datadir" then datadir="$basedir/data" fi sbindir="$basedir/sbin" libexecdir="$basedir/libexec" fi # datadir_set is used to determine if datadir was set (and so should be # *not* set inside of the --basedir= handler.) datadir_set= # # Use LSB init script functions for printing messages, if possible # lsb_functions="/lib/lsb/init-functions" if test -f $lsb_functions ; then . $lsb_functions else log_success_msg() { echo " SUCCESS! $@" } log_failure_msg() { echo " ERROR! $@" } fi PATH="/sbin:/usr/sbin:/bin:/usr/bin:$basedir/bin" export PATH mode=$1 # start or stop [ $# -ge 1 ] && shift other_args="$*" # uncommon, but needed when called from an RPM upgrade action # Expected: "--skip-networking --skip-grant-tables" # They are not checked here, intentionally, as it is the resposibility # of the "spec" file author to give correct arguments only. case `echo "testing\c"`,`echo -n testing` in *c*,-n*) echo_n= echo_c= ;; *c*,*) echo_n=-n echo_c= ;; *) echo_n= echo_c='\c' ;; esac parse_server_arguments() { for arg do case "$arg" in --basedir=*) basedir=`echo "$arg" | sed -e 's/^[^=]*=//'` bindir="$basedir/bin" if test -z "$datadir_set"; then datadir="$basedir/data" fi sbindir="$basedir/sbin" libexecdir="$basedir/libexec" ;; --datadir=*) datadir=`echo "$arg" | sed -e 's/^[^=]*=//'` datadir_set=1 ;; --pid-file=*) mysqld_pid_file_path=`echo "$arg" | sed -e 's/^[^=]*=//'` ;; --service-startup-timeout=*) service_startup_timeout=`echo "$arg" | sed -e 's/^[^=]*=//'` ;; esac done } wait_for_pid () { verb="$1" # created | removed pid="$2" # process ID of the program operating on the pid-file pid_file_path="$3" # path to the PID file. i=0 avoid_race_condition="by checking again" while test $i -ne $service_startup_timeout ; do case "$verb" in 'created') # wait for a PID-file to pop into existence. test -s "$pid_file_path" && i='' && break ;; 'removed') # wait for this PID-file to disappear test ! -s "$pid_file_path" && i='' && break ;; *) echo "wait_for_pid () usage: wait_for_pid created|removed pid pid_file_path" exit 1 ;; esac # if server isn't running, then pid-file will never be updated if test -n "$pid"; then if kill -0 "$pid" 2>/dev/null; then : # the server still runs else # The server may have exited between the last pid-file check and now. if test -n "$avoid_race_condition"; then avoid_race_condition="" continue # Check again. fi # there's nothing that will affect the file. log_failure_msg "The server quit without updating PID file ($pid_file_path)." return 1 # not waiting any more. fi fi echo $echo_n ".$echo_c" i=`expr $i + 1` sleep 1 done if test -z "$i" ; then log_success_msg return 0 else log_failure_msg return 1 fi } # Get arguments from the my.cnf file, # the only group, which is read from now on is [mysqld] if test -x "$bindir/my_print_defaults"; then print_defaults="$bindir/my_print_defaults" else # Try to find basedir in /etc/my.cnf conf=/etc/my.cnf print_defaults= if test -r $conf then subpat='^[^=]*basedir[^=]*=\(.*\)$' dirs=`sed -e "/$subpat/!d" -e 's//\1/' $conf` for d in $dirs do d=`echo $d | sed -e 's/[ ]//g'` if test -x "$d/bin/my_print_defaults" then print_defaults="$d/bin/my_print_defaults" break fi done fi # Hope it's in the PATH ... but I doubt it test -z "$print_defaults" && print_defaults="my_print_defaults" fi # # Read defaults file from 'basedir'. If there is no defaults file there # check if it's in the old (depricated) place (datadir) and read it from there # extra_args="" if test -r "$basedir/my.cnf" then extra_args="-e $basedir/my.cnf" fi parse_server_arguments `$print_defaults $extra_args mysqld server mysql_server mysql.server` # # Set pid file if not given # if test -z "$mysqld_pid_file_path" then mysqld_pid_file_path=$datadir/`hostname`.pid else case "$mysqld_pid_file_path" in /* ) ;; * ) mysqld_pid_file_path="$datadir/$mysqld_pid_file_path" ;; esac fi case "$mode" in 'start') # Start daemon # Safeguard (relative paths, core dumps..) cd $basedir echo $echo_n "Starting MySQL" if test -x $bindir/mysqld_safe then # Give extra arguments to mysqld with the my.cnf file. This script # may be overwritten at next upgrade. $bindir/mysqld_safe --datadir="$datadir" --pid-file="$mysqld_pid_file_path" $other_args >/dev/null & wait_for_pid created "$!" "$mysqld_pid_file_path"; return_value=$? # Make lock for RedHat / SuSE if test -w "$lockdir" then touch "$lock_file_path" fi exit $return_value else log_failure_msg "Couldn't find MySQL server ($bindir/mysqld_safe)" fi ;; 'stop') # Stop daemon. We use a signal here to avoid having to know the # root password. if test -s "$mysqld_pid_file_path" then # signal mysqld_safe that it needs to stop touch "$mysqld_pid_file_path.shutdown" mysqld_pid=`cat "$mysqld_pid_file_path"` if (kill -0 $mysqld_pid 2>/dev/null) then echo $echo_n "Shutting down MySQL" kill $mysqld_pid # mysqld should remove the pid file when it exits, so wait for it. wait_for_pid removed "$mysqld_pid" "$mysqld_pid_file_path"; return_value=$? else log_failure_msg "MySQL server process #$mysqld_pid is not running!" rm "$mysqld_pid_file_path" fi # Delete lock for RedHat / SuSE if test -f "$lock_file_path" then rm -f "$lock_file_path" fi exit $return_value else log_failure_msg "MySQL server PID file could not be found!" fi ;; 'restart') # Stop the service and regardless of whether it was # running or not, start it again. if $0 stop $other_args; then $0 start $other_args else log_failure_msg "Failed to stop running server, so refusing to try to start." exit 1 fi ;; 'reload'|'force-reload') if test -s "$mysqld_pid_file_path" ; then read mysqld_pid < "$mysqld_pid_file_path" kill -HUP $mysqld_pid && log_success_msg "Reloading service MySQL" touch "$mysqld_pid_file_path" else log_failure_msg "MySQL PID file could not be found!" exit 1 fi ;; 'status') # First, check to see if pid file exists if test -s "$mysqld_pid_file_path" ; then read mysqld_pid < "$mysqld_pid_file_path" if kill -0 $mysqld_pid 2>/dev/null ; then log_success_msg "MySQL running ($mysqld_pid)" exit 0 else log_failure_msg "MySQL is not running, but PID file exists" exit 1 fi else # Try to find appropriate mysqld process mysqld_pid=`pidof $libexecdir/mysqld` # test if multiple pids exist pid_count=`echo $mysqld_pid | wc -w` if test $pid_count -gt 1 ; then log_failure_msg "Multiple MySQL running but PID file could not be found ($mysqld_pid)" exit 5 elif test -z $mysqld_pid ; then if test -f "$lock_file_path" ; then log_failure_msg "MySQL is not running, but lock file ($lock_file_path) exists" exit 2 fi log_failure_msg "MySQL is not running" exit 3 else log_failure_msg "MySQL is running but PID file could not be found" exit 4 fi fi ;; *) # usage basename=`basename "$0"` echo "Usage: $basename {start|stop|restart|reload|force-reload|status} [ MySQL server options ]" exit 1 ;; esac exit 0 帮忙分析下脚本
最新发布
09-06
<think> 嗯,用户想分析MySQL启动/停止脚本的功能和逻辑,而且特别提到脚本包含变量设置、参数解析、进程等待等操作。用户应该是个系统管理员或者开发运维人员,正在研究MySQL的服务管理机制。这类脚本通常隐藏在/etc/init.d目录里,但用户可能正在改造它或需要排错。 从用户提供的四个引用来看,线索比较零碎: 引用1和3都提到mysql.server这个关键启动脚本文件名,引用3还提到通过软接将脚本放入bin目录的操作。引用2提到的状态变量很有意思,但用户关注点显然在控制脚本而非服务器内部变量。引用4的zipkin脚本倒是个很好的对照案例,展示了标准的PID检查和进程停止逻辑。 脚本分析的核心应该是三个维度:启动流程(环境检查→参数解析→进程启动)、停止流程(信号发送→超时控制→强制终止)、状态管理(PID文件操作)。特别要注意的是MySQL可能需要处理my.cnf配置文件的优先级问题,以及mysqld_safe这个包装进程的处理——很多初学者会忽略这个细节。 用户没提供具体脚本内容,所以得聚焦通用实现模式。比如变量设置部分,常见的有BASEDIR、datadir、mysqld_pid_file_path等关键路径的定义;参数解析部分通常会处理--defaults-file这种覆盖配置文件的场景;进程等待最经典的是用for循环+sleep实现的超时检测逻辑。 需要提醒用户注意几个技术点:SIGTERM和SIGKILL的区别使用、mysqld_safe的监督作用可能导致双PID文件、以及初始化数据库时的临时密码过滤机制(如引用3所述)。这些在自定义脚本时都是高频踩坑点。 </think> 以下是对 MySQL 启动/停止脚本功能和逻辑的分析,基于常见的实现模式(如 `mysql.server` 或 `mysqld_safe` 脚本): --- ### 📜 **脚本核心功能** 1. **服务控制** - 接收命令参数(`start`/`stop`/`restart`/`status`) - 调用系统服务管理工具(如 `service` 或 `systemctl`)或直接操作进程 2. **环境初始化** - **设置关键路径**: ```bash basedir=/usr/local/mysql datadir=/var/lib/mysql ``` - **加载配置文件**: 解析 `my.cnf` 或通过 `--defaults-file` 指定配置: ```bash conf=/etc/my.cnf ``` 3. **进程管理** - **启动**:调用 `mysqld_safe`(守护进程)或直接启动 `mysqld` ```bash $basedir/bin/mysqld_safe --datadir="$datadir" >/dev/null & ``` - **停止**:向 `mysqld` 进程发送 `SIGTERM` 信号,超时后强制 `SIGKILL` ```bash kill -TERM $(cat "$pid_file") # 优雅终止 sleep 5 kill -KILL $(cat "$pid_file") 2>/dev/null # 强制终止 [^4] ``` 4. **状态检测** - **检查 PID 文件**:验证进程是否存活 ```bash if [ -f "$pid_file" ] && kill -0 $(cat "$pid_file") ; then echo "MySQL正在运行" fi ``` - **端口监听检测**:通过 `netstat` 或 `ss` 确认 `3306` 端口状态 --- ### ️ **关键逻辑流程** #### ▶️ **启动流程** ```mermaid graph TD A[解析参数] --> B{是否已运行?} B ----> C[报错并退出] B ----> D[设置环境变量] D --> E[调用 mysqld_safe] E --> F[等待PID文件生成] F --> G{进程是否存活?} G ----> H[启动成功] G ----> I[启动失败] ``` #### 🛑 **停止流程** ```mermaid graph TD A[解析参数] --> B{是否在运行?} B ----> C[报错并退出] B ----> D[发送SIGTERM] D --> E[等待5秒] E --> F{进程退出?} F ----> G[删除PID文件] F ----> H[发送SIGKILL] H --> G[删除PID文件] [^4] ``` --- ### 🔍 **高级机制分析** 1. **PID 文件管理** - **路径**:通常为 `$datadir/hostname.pid` - **作用**:记录主进程 ID,用于状态检查和停止操作 - **风险**:PID 文件未清理会导致误判进程状态 2. **超时控制** - 启动时等待 PID 文件生成的超时(通常 5-60 秒) - 停止时等待进程退出的超时(强制终止前等待 5-10 秒)[^4] 3. **用户权限控制** - 通过 `--user=mysql` 指定运行账户 - 关键目录权限检查(如 `datadir` 是否属于 mysql 用户) 4. **日志重定向** - 启动日志输出到 `$datadir/hostname.err` - 控制台输出抑制(`>/dev/null 2>&1`) --- ### ⚠️ **典型问题场景** 1. **启动失败** - PID 文件已存在但进程不存活 → 需手动删除 PID 文件 - 端口被占用 → 检查冲突进程 - 配置文件错误 → 验证 `my.cnf` 语法 [^2] 2. **停止失败** - 进程无响应 → 强制终止后需检查死锁或 I/O 阻塞 - 权限不足 → 需 root 执行脚本 3. **重启间隙故障** - 未等待进程完全退出即启动 → 导致数据损坏 - 未处理 `mysqld_safe` 的监控进程 → 产生僵尸进程 --- ### 💡 **引用说明** [^1]: 脚本支持 `service mysqld start/stop` 等标准操作 [^2]: 启动参数通过 `my.cnf` 或命令行传递,影响服务器变量 [^3]: 初始化时需设置环境变量和临时密码过滤 [^4]: 强制终止逻辑确保服务可控停止 --- ### ❓相关问题 1. MySQL 启动时如何加载自定义配置文件? 2. `mysqld_safe` 和 `mysqld` 在启动过程中的分工是什么? 3. PID 文件意外丢失会导致什么后果? 4. 如何修改脚本以支持 Graceful Shutdown(优雅关闭)?
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

逍遥俊子

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付:¥1
获取中
扫码支付

您的余额不足,请更换扫码支付或充值

打赏作者

实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值