redis主要存储图片的base64值。 业务是循环发送群（群，文字等）。图片存储redis读取redis。 public function hander(){ try { $redis = new \EasySwoole\Redis\RedisCluster(new \EasySwoole\Redis\Config\RedisClusterConfig([ ['172.16.0.36', 6379], ['172.16.0.36', 6380], ['172.16.0.36', 6381], ['172.16.0.37', 6379], ['172.16.0.37', 6380], ['172.16.0.37', 6381], ['172.16.0.38', 6379], ['172.16.0.38', 6380], ['172.16.0.38', 6381], ], [ 'auth' => '', 'serialize' => $this->serialize ? \EasySwoole\Redis\Config\RedisConfig::SERIALIZE_JSON : \EasySwoole\Redis\Config\RedisConfig::SERIALIZE_NONE, 'timeout'=>1 ])); }catch (\Throwable $e) { $extra = [ 'code' => $e->getCode(), 'msg' => $e->getMessage(), 'line' => $e->getLine(), 'file' => $e->getFile() ]; echo "Exception:".json_encode($extra)."\n"; return false; } return $redis; }

直接在发送的时候获取redis hander，get ，循环的时候有时候卡住了，有时候正常，一般前两个正常，第三个就卡住。

什么情况？设置redis的超时时间了。

EasySwoole版本为：3.3.4 1、在EasySwooleEvent设置redis pool的最小和最大连接数 $redis_pool_config->setMinObjectNum(5); $redis_pool_config->setMaxObjectNum(20);

2、EasySwoole启动情况如下： root 10189 0.0 0.0 614168 7484 ? Ssl 05:28 0:00 EasySwoole root 10190 0.0 0.1 321360 9004 ? S 05:28 0:00 EasySwoole root 10196 0.2 0.1 330552 10052 ? Sl 05:28 0:04 EasySwoole.Worker.0 root 10197 0.2 0.1 330552 10052 ? Sl 05:28 0:04 EasySwoole.Worker.1 root 10198 0.2 0.1 330552 10052 ? Sl 05:28 0:04 EasySwoole.Worker.2 root 10199 0.3 0.2 636516 19312 ? Sl 05:28 0:07 EasySwoole.Worker.3 root 10201 0.2 0.2 634404 16388 ? Sl 05:28 0:04 EasySwoole.Worker.4 root 10203 0.2 0.2 634136 16120 ? Sl 05:28 0:04 EasySwoole.Worker.5 root 10204 0.2 0.2 634200 16116 ? Sl 05:28 0:04 EasySwoole.Worker.6 root 10206 0.2 0.1 330552 10052 ? Sl 05:28 0:04 EasySwoole.Worker.7 root 10208 0.2 0.1 333660 10576 ? Sl 05:28 0:04 EasySwoole.TaskWorker.0 root 10210 0.2 0.1 333660 10572 ? Sl 05:28 0:04 EasySwoole.TaskWorker.1 root 10211 0.2 0.1 333660 10588 ? Sl 05:28 0:04 EasySwoole.TaskWorker.2 root 10213 0.2 0.1 333660 10580 ? Sl 05:28 0:04 EasySwoole.TaskWorker.3

3、通过redis cli查看redis的连接情况，如下： # Clients connected_clients:434 client_recent_max_input_buffer:4 client_recent_max_output_buffer:0 blocked_clients:0

4、通过netstat监控redis端口，发现将近400个连接，都是由一个EasySwoole进程连接的，进程id为：10199，具体如下： tcp 0 0 127.0.0.1:32940 127.0.0.1:6379 ESTABLISHED 10199/EasySwoole.Worker tcp 0 0 127.0.0.1:33280 127.0.0.1:6379 ESTABLISHED 10199/EasySwoole.Worker ............

5、日志记录的redis连接池使用情况： [2020-02-28 14:20:44][DEBUG][INFO] : [Redis Pool: ``{"created":5,"inuse":0,"max":20,"min":5}] [2020-02-28 14:20:44][DEBUG][INFO] : [Redis Pool: {"created":5,"inuse":0,"max":20,"min":5}] [2020-02-28 14:20:49][DEBUG][INFO] : [Redis Pool: {"created":5,"inuse":0,"max":20,"min":5}] [2020-02-28 14:20:49][DEBUG][INFO] : [Redis Pool: {"created":5,"inuse":0,"max":20,"min":5}] [2020-02-28 14:20:49][DEBUG][INFO] : [Redis Pool: {"created":5,"inuse":0,"max":20,"min":5}] [2020-02-28 14:20:49][DEBUG][INFO] : [Redis Pool: {"created":5,"inuse":0,"max":20,"min":5}]

问题： (1) 按第一步配置情况应该是一个worker最多开20个连接，8个worker也就是160个连接，但实际却是一个worker就开了将近400个连接，其它worker几乎没有创建redis连接，想请教下为什么是这样的？ (2) 第五步获取的redis连接池使用情况为什么跟实际不一样？实际有400个连接

swoole for win版本：https://www.swoole.com/static/swoole-4.2.1.zip es版本：1.1.1

问题：在直接运行php和使用swoole运行pdo均正常。但是在es中使用出现了502错误(无法访问此网站)。同样的es代码在linux可以正常运行，但在win版本无法运行。

<?php
//php-cli Version（正常）
$dbhost = '127.0.0.1:3306';  // mysql服务器主机地址
$dbuser = 'admin';            // mysql用户名
$dbpass = 'admin';          // mysql用户名密码
$conn = new PDO('mysql:host=127.0.0.1;dbname=yiban;port=3306', $dbuser, $dbpass );
$query = $conn->query('select * from yiban_college_data');
$data =[];
print_r( $query->fetchAll() );

<?php
//php-swoole Version（正常）
$http = new swoole_http_server("127.0.0.1", 9501);
$http->on('request', function ($request, $response) {
	$dbhost = '127.0.0.1:3306';  // mysql服务器主机地址
	$dbuser = 'admin';            // mysql用户名
	$dbpass = 'admin';          // mysql用户名密码
	$conn = new PDO('mysql:host=127.0.0.1;dbname=yiban;port=3306', $dbuser, $dbpass );
	$query = $conn->query('select * from yiban_college_data');
	$data =[];
	print_r( $query->fetchAll() );
    $response->end("<h1>Hello Swoole. #".rand(1000, 9999)."</h1>");
});
$http->start();

<?php
//ES Version(win异常，linux正常)
    function test(){
        $dbhost = '127.0.0.1:3306';  // mysql服务器主机地址
        $dbuser = 'admin';            // mysql用户名
        $dbpass = 'admin';          // mysql用户名密码
        $conn = new \PDO('mysql:host=127.0.0.1;dbname=yiban;port=3306', $dbuser, $dbpass );
        $query = $conn->query('select * from yiban_college_data');
        $data =[];
        print_r( $query->fetchAll() );
    }

https://www.easyswoole.com/BaseUsage/crontab.html 完整使用示例代码 在 EasySwoole 中使用 第2点

最后一行 $crontab->attachToServer(ServerManager::getInstance()->getSwooleServer());

如果添加这一行 任务到时间后会重复运行 但是用指令执行正常

代码直接取示例的代码即可验证

#533 之前按照这个任务改了 \EasySwoole\Crontab\Crontab 类 替换为 \EasySwoole\EasySwoole\Crontab\Crontab 类 这个问题才显现出来

目前有一个参数，我需要在一次请求的完整周期内（包括由当前请求内创建的异步任务）使用一个变量

在创建Saas项目时，通常会有一些数据库字段用于表示客户来源，比如client id，现在问题是我想在用户登录后，每次请求都会通过权限控制获取到这个client id，然后这个client id 在整个请求周期内，不管是控制器内，还是模型，服务，异步任务等地方，都能获取到这个client id，我尝试看过文档里关于全局变量的描述，全局变量在框架内是不可用的，而且框架也不依赖session，所以通过session也不能，就算是让这个数据缓存在客户端，每次通过请求发送到后端，这任然之后控制器内能获取，而不能在其他类/变量里面拿到这个变量

使用： easyswoole-3.4.4和elasticsearch 7.10.1，单条和批量插入时，提示错误如下： [2021-06-02 09:11:35][debug][notice]:[Specifying types in urls has been deprecated at file:/easyswoole/vendor/easyswoole/elasticsearch/src/Endpoints/Bulk.php line:22]。

部分源代码： $config = new \EasySwoole\ElasticSearch\Config([ 'host' => 'es01', 'port' => 9200, 'username' => 'elastic', 'password' => '*********', 'scheme' => 'https' ]);

    $elasticsearch = new \EasySwoole\ElasticSearch\ElasticSearch($config);

    go(function () use ($elasticsearch, $body) {
        $bean = new \EasySwoole\ElasticSearch\RequestBean\Bulk();
        $bean->setIndex('log_web');
        $bean->setType('tms_lbs_receive');
        /*     $body = [];
             for ($i = 1; $i <= 5; $i++) {
                 $body[] = [
                     'create' => [
                         '_index' => 'my-index',
                         '_type' => 'my-type',
                         '_id' => $i * 1000
                     ]
                 ];
                 $body[] = [
                     'test-field' => 'test-data',
                 ];
             }*/
        $bean->setBody($body);
        $response = $elasticsearch->client()->bulk($bean)->getBody();
        $response = json_decode($response, true);
        var_dump($response);

可能原因： es6时，官方就提到了es7会删除type，并且es6时已经规定每一个index只能有一个type。在es7中使用默认的_doc作为type，官方说在8.x版本会彻底移除type。

Hi everyone, a question can Easyswoole handle user sessions through multiple servers (front end ) connected to one database server ?

I am thinking of that Laravel can handle it since one can store sessions in the database, is this possible to do the same with Easyswoole ?

If not, is ther any other way to share the user sessions in multiple servers ?

Regards

按照文档: 启动框架 中途没有报错的话，执行：

启动框架

php easyswoole server start 此时可以访问 http://localhost:9501 就看到框架的欢迎页面，表示框架已经安装成功

实际: yun@kube-slave1:/data/www/dev/easyswoole-3.x$ php easyswoole server start

| | / | | | | | __ _ ___ _ _ | ( __ __ ___ ___ | | ___ | | / ` | / | | | | | _ \ \ \ /\ / / / _ \ / _ \ | | / _
| | | (| | _ \ | || | __) | \ V V / | () | | () | | | | / || _,| |/ __, | |/ _/_/ _/ ___/ || ___| / | |_/ Operation: php easyswoole start [arg1] [arg2] Intro: to start current easyswoole server Arg: daemonize run in daemonize produce load produce.php

文档能否写的仔细点, 如此这般, 怎么敢用于生产环境

目前在registerErrorHandler里面，当出现不可捕获的异常时，会导致客户端无法得到响应（控制台有输出），最终504错误，因此要放到EventRegister::onRequest的闭包函数里面

swoole文档：https://wiki.swoole.com/#/getting_started/notice?id=%e6%8d%95%e8%8e%b7server%e8%bf%90%e8%a1%8c%e6%9c%9f%e8%87%b4%e5%91%bd%e9%94%99%e8%af%af

版本信息
sw:4.2.11 es:3.1.14

分发器 public function decode($raw, $client): ?Caller { $caller = new Caller; public function decode($raw, $client): ?Caller { $caller = new Caller; $caller->setControllerClass("\App\WebSocket\Controller\Index"); $caller->setAction('heartbeat'); return $caller; }

注册事件 // 注册WS事件回调 $conf = new \EasySwoole\Socket\Config(); $conf->setType($conf::WEB_SOCKET); $conf->setParser(new WebSocketParser); $dispatch = new Dispatcher($conf); // 收到客户端消息时的处理 $register->set(EventRegister::onMessage, function (\swoole_server $server, \swoole_websocket_frame $frame) use ($dispatch) { $dispatch->dispatch($server, $frame->data, $frame); });

报错信息 PHP Fatal error: Uncaught EasySwoole\Socket\Exception\ControllerPoolEmpty: controller pool empty for \App\WebSocket\Controller\Index in /usr/share/nginx/html/chengzi/vendor/easyswoole/socket/src/Dispatcher.php:89 Stack trace: #0 /usr/share/nginx/html/chengzi/EasySwooleEvent.php(49): EasySwoole\Socket\Dispatcher->dispatch(Object(Swoole\WebSocket\Server), 'PING', Object(Swoole\WebSocket\Frame)) #1 [internal function]: EasySwoole\EasySwoole\EasySwooleEvent::EasySwoole\EasySwoole{closure}(Object(Swoole\WebSocket\Server), Object(Swoole\WebSocket\Frame)) #2 /usr/share/nginx/html/chengzi/vendor/easyswoole/easyswoole/src/ServerManager.php(99): call_user_func(Object(Closure), Object(Swoole\WebSocket\Server), Object(Swoole\WebSocket\Frame)) #3 {main} thrown in /usr/share/nginx/html/chengzi/vendor/easyswoole/socket/src/Dispatcher.php on line 89

Fatal error: Uncaught EasySwoole\Socket\Exception\ControllerPoolEmpty: controller pool empty for \App\WebSocket\Controller\Index in /usr/share/nginx/html/chengzi/vendor/easyswoole/socket/src/Dispatcher.php:89 Stack trace: #0 /usr/share/nginx/html/chengzi/EasySwooleEvent.php(49): EasySwoole\Socket\Dispatcher->dispatch(Object(Swoole\WebSocket\Server), 'PING', Object(Swoole\WebSocket\Frame)) #1 [internal function]: EasySwoole\EasySwoole\EasySwooleEvent::EasySwoole\EasySwoole{closure}(Object(Swoole\WebSocket\Server), Object(Swoole\WebSocket\Frame)) #2 /usr/share/nginx/html/chengzi/vendor/easyswoole/easyswoole/src/ServerManager.php(99): call_user_func(Object(Closure), Object(Swoole\WebSocket\Server), Object(Swoole\WebSocket\Frame)) #3 {main} thrown in /usr/share/nginx/html/chengzi/vendor/easyswoole/socket/src/Dispatcher.php on line 89

Hello, i'm trying to understand how easyswoole can help me upgrading my distributed datascraper achitecture which i built on top of zeromq (majordomo pattern + optional titanic queue persistence on redis), msgpack for network packet compression and mongodb for schema-less storage.

With zeromq i can setup a main majordomo broker that maintain a list of available workers identified by names and distributed across multiple machines, creating a pool of each worker type. Using a vent-sink pattern i push the tasks that need to be performed and these are distributed across the workers as they become available (these are single thread workers, so while working they don't respond to heartbeat and from the broker point of view they become unavailable, and return available after the task is done and the heartbeat is restored). The tasks distribution is not following the round robin approach, since the workers internal zmq queue is limited to 1 task and the broker recieve a "task done" aknowledge , so the fastest workers got more tasks todo.

What i love of this approach is that is resilent and consistent, broker down ? no problem, it restart (as it is supervisor monitored) and process the "eventually" persisted titanic queue. Need more processing power? No problem, spin-up a new node with 100 workers and they immediatly starts working.

What i hate is the memory consumption, each worker requires between 15 to 30 mb, and also the relevant quantity of php code distributed on each worker (the majordomo pattern, titanic and majordomo worker code is written in php, same as the redis queue and few other stuff).

I'd like to hear your opinion about the benefits rewriting this kind of architecture using easyswoole/swoole. Some examples will be very appreciated.

Beg my pardon for my bad english, hope can help me better understand. thank you!

//需要开启协程数、判断需要处理的图片数与协程数,取较小值 $loopSize = $size < ($imageLength-$start) ? $size : ($imageLength-$start); for ($j = 0; $j < $loopSize; $j++){ //保存图片 $wg->add(); go (function () use($wg, $redis, $j, $start, $imageLocalPath, $channel, $imageUrl, $imagePath, $exportId){ $imageIndex = $j + $start; $image_url = $imageUrl[$imageIndex]; if (empty($image_url) || $image_url == "") { $imageData = [$imageIndex=>""]; $channel->push($imageData); }else { $client = new HttpClient(); $endWith = pathinfo($image_url); $endType = "jpg"; if (isset($endWith['extension'])) { $endType = $endWith['extension']; } $client->setUrl($image_url); $client->setTimeout(15); $filename = "{$imagePath}/{$imageIndex}.{$endType}"; $imageLocalFullPath = "{$imageLocalPath}/{$imageIndex}.{$endType}"; $imageData = [$imageIndex=>$imageLocalFullPath]; $channel->push($imageData); try { $res = $client->download($filename, 0, HttpClient::METHOD_GET, $client->get()->getBody()); Manager::getInstance()->get("ssc_capture")->invoke(function (Redis $redis) use ($exportId) { $redis->hIncrBy($this->taskId, "handle_num", 1); }); $client->getClient()->close(); } catch (\Exception $e) { echo CLASS."".FUNCTION.""."下载图片异常_".$e->getMessage().PHP_EOL; } } $wg->done(); }); } $wg->wait(); }

[2022-08-18 15:22:17][trigger][warning]:[Swoole\Table::set(): failed to set('9205'), unable to allocate memory at file:/home/share/v3.api.easyswole/vendor/easyswoole/easyswoole/src/Core.php line:302]

在redis 的队列了经常会出现

message":"SQLSTATE[HY000] [2002] Connection reset by peer or Transport endpoint is not connected [show full columns from out_order_bill_log]

和

SQLSTATE[HY000] [4031] The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior

数据库配置如下：

'host' => '', 'port' => 3306, 'user' => 'xxxx', 'password' => 'xxxx', 'database' => 'xxxx', 'timeout' => 9, 'charset' => 'utf8mb4', 'fetchModel' => true, 'returnCollection' => true, 'strictType' => true, 'minObjectNum' => 15, 'intervalCheckTime' => 3580, 'maxObjectNum' => 120, 'maxIdleTime' => 15, 'autoPing' => 5,

msyql8.3

wait_timeout配置为 28800

eayswoole版本为 3.4.4 swoole版本为 4.6.7

请问这是什么原因呢

我按照https://www.easyswoole.com/Components/Orm/problem.html的试了下缺缺少invoke方法 按照https://github.com/easy-swoole/orm缺是缺少Model::invoke()

是不是1.x 2.x两个版本完全不一样了？ 有没有2.x的文档？

https://www.easyswoole.com/Components/Orm/query.html

同时报告下 文档有误 https://github.com/easy-swoole/orm