dubbo3 RPC超时

Timeout

获取超时时间

dubbo RPC 调用的超时时间在provider端或者consumer端设置都可以，consumer在调用时，会去获取超时时间，超时时间的获取顺序： consumer 引用配置的超时时间(ReferenceConfig.timeout) > provider 服务暴露的超时时间(ServiceConfig.timeout) > 默认超时时间(1000ms)
调用栈：

consumer/provider 优先级顺序的逻辑在InstanceAddressURL中，在该类中，即有consumer URL，也有provider的service 信息，获取逻辑的代码如下：
InstanceAddressURL#getMethodParameter()

    @Override
    public String getMethodParameter(String method, String key) {
        if (consumerParamFirst(key)) {
            URL consumerUrl = RpcContext.getServiceContext().getConsumerUrl();
            if (consumerUrl != null) {
                String v = consumerUrl.getMethodParameter(method, key);
                if (StringUtils.isNotEmpty(v)) {
                    return v;
                }
            }
        }

        String protocolServiceKey = getProtocolServiceKey();
        if (isEmpty(protocolServiceKey)) {
            return null;
        }
        return getServiceMethodParameter(protocolServiceKey, method, key);
    }

RPC调用

dubbo rpc调用底层是通过netty nio tcp实现的通信交互，在tcp的通信层是异步的，如果我们以同步的方式调用接口，就涉及到异步转同步，dubbo中关于异步转同步采用的是DefaultFuture，它继承自java.util.concurrent.CompletableFuture；
具体的步骤如下：

consumer 新建一个DefaultFuture对象，将其放入一个静态的Map中，key是request.id
consumer 发送request请求，并调用AsyncRpcResult.get(long, TimeUnit) (为什么没有调用DefaultFuture.get(long, TimeUnit)请看下一节)
provider处理完业务逻辑后，在返回时将request.id一并返回过来
consumer收回响应后，通过request.id再获取到DefaultFuture对象，再调用该对象的complete()方法

以上一次RPC的正常流程，但是超时流程在另一分支，不过代码逻辑是一样一样的。

RPC 超时处理

dubbo超时处理逻辑有三处：

DefaultFuture.timeoutCheck()
该方法是在创建DefaultFuture时，就会被执行

    public static DefaultFuture newFuture(Channel channel, Request request, int timeout, ExecutorService executor) {
        final DefaultFuture future = new DefaultFuture(channel, request, timeout);
        future.setExecutor(executor);
        // ThreadlessExecutor needs to hold the waiting future in case of circuit return.
        if (executor instanceof ThreadlessExecutor) {
            ((ThreadlessExecutor) executor).setWaitingFuture(future);
        }
        // timeout check
        timeoutCheck(future);
        long diff = System.currentTimeMillis() - future.start;
        if(diff>5){
            System.out.println("diff: " + diff);
        }
        return future;
    }

该方法会创建一个TimeoutCheckTask添加到dubbo的时间轮中处理，代码如下：

    private static void timeoutCheck(DefaultFuture future) {
        TimeoutCheckTask task = new TimeoutCheckTask(future.getId());
        future.timeoutCheckTask = TIME_OUT_TIMER.get().newTimeout(task, future.getTimeout(), TimeUnit.MILLISECONDS);
    }

AsyncRpcResult.get(long, TimeUnit)
获取响应的调用链：

调用的是AsyncRpcResult.get(long, TimeUtit)方法；
AsyncRpcResult是dubbo对于响应结果的统一封装，获取结果的有两个方法：

    @Override
    public Result get() throws InterruptedException, ExecutionException {
        if (executor != null && executor instanceof ThreadlessExecutor) {
            ThreadlessExecutor threadlessExecutor = (ThreadlessExecutor) executor;
            threadlessExecutor.waitAndDrain();
        }
        return responseFuture.get();
    }

    @Override
    public Result get(long timeout, TimeUnit unit) throws InterruptedException, ExecutionException, TimeoutException {
        if (executor != null && executor instanceof ThreadlessExecutor) {
            ThreadlessExecutor threadlessExecutor = (ThreadlessExecutor) executor;
            threadlessExecutor.waitAndDrain();
        }
        return responseFuture.get(timeout, unit);
    }

两个方法中都有ThreadlessExecutor的判断，以及threadlessExecutor.waitAndDrain()的调用，该方法会一直等待，直到有响应结果为止。
ThreadlessExecutor是 duubo2.7版本中引入的，它在dubbo中应用于同步的RPC方法。
dubbo会在发起RPC调用之前检查是否为同步调用，如果是就创建ThreadlessExecutor用于后面的RPC流程中。

AbstractInvoker.getCallbackExecutor()方法代码：

    protected ExecutorService getCallbackExecutor(URL url, Invocation inv) {
        if (InvokeMode.SYNC == RpcUtils.getInvokeMode(getUrl(), inv)) {
            return new ThreadlessExecutor();
        }
        return url.getOrDefaultApplicationModel().getExtensionLoader(ExecutorRepository.class)
            .getDefaultExtension()
            .getExecutor(url);
    }

TimeoutCheckTask
TimeoutCheckTask会被添加到时间轮中，超时时间到就会被执行；TimeoutCheckTask逻辑比较简单，传递一个超时的结果；
代码如下：

    private static class TimeoutCheckTask implements TimerTask {

        private final Long requestID;

        TimeoutCheckTask(Long requestID) {
            this.requestID = requestID;
        }

        @Override
        public void run(Timeout timeout) {
            DefaultFuture future = DefaultFuture.getFuture(requestID);
            long end = System.currentTimeMillis();
            if (future == null || future.isDone()) {
                return;
            }

            if (future.getExecutor() != null) {
                future.getExecutor().execute(() -> notifyTimeout(future));
            } else {
                notifyTimeout(future);
            }
        }

        private void notifyTimeout(DefaultFuture future) {
            // create exception response.
            Response timeoutResponse = new Response(future.getId());
            // set timeout status.
            timeoutResponse.setStatus(future.isSent() ? Response.SERVER_TIMEOUT : Response.CLIENT_TIMEOUT);
            timeoutResponse.setErrorMessage(future.getTimeoutMessage(true));
            // handle response.
            DefaultFuture.received(future.getChannel(), timeoutResponse, true);
        }
    }

ThreadlessExecutor

在duubo2.7版本中引入了ThreadlessExecutor，它能避免一次线程上下文切换，实际上也是通过队列实现的。
下面是ThreadlessExecutor的三个核心方法：

waitAndDrain()
从队列中获取任务执行，如果队列为空，则等待直到有任务入队列。
execute(Runnable)
将任务添加到队列中
notifyReturn(Throwable)
添加任务入队列，该任务是将Throwable赋值给DefaultFuture。

代码如下：

    private final BlockingQueue<Runnable> queue = new LinkedBlockingQueue<>();

    public void waitAndDrain() throws InterruptedException {
        /**
         * Usually, {@link #waitAndDrain()} will only get called once. It blocks for the response for the first time,
         * once the response (the task) reached and being executed waitAndDrain will return, the whole request process
         * then finishes. Subsequent calls on {@link #waitAndDrain()} (if there're any) should return immediately.
         *
         * There's no need to worry that {@link #finished} is not thread-safe. Checking and updating of
         * 'finished' only appear in waitAndDrain, since waitAndDrain is binding to one RPC call (one thread), the call
         * of it is totally sequential.
         */
        if (isFinished()) {
            return;
        }

        Runnable runnable;
        try {
            runnable = queue.take();
        } catch (InterruptedException e) {
            setWaiting(false);
            throw e;
        }

        synchronized (lock) {
            setWaiting(false);
            runnable.run();
        }

        runnable = queue.poll();
        while (runnable != null) {
            runnable.run();
            runnable = queue.poll();
        }
        // mark the status of ThreadlessExecutor as finished.
        setFinished(true);
    }

    /**
     * If the calling thread is still waiting for a callback task, add the task into the blocking queue to wait for schedule.
     * Otherwise, submit to shared callback executor directly.
     *
     * @param runnable
     */
    @Override
    public void execute(Runnable runnable) {
        runnable = new RunnableWrapper(runnable);
        synchronized (lock) {
            if (!isWaiting()) {
                runnable.run();
                return;
            }
            queue.add(runnable);
        }
    }
    
    public void notifyReturn(Throwable t) {
        // an empty runnable task.
        execute(() -> {
            waitingFuture.completeExceptionally(t);
        });
    }

超时调用栈：

正常响应调用栈：

AllChannelHandler又涉及到dubbo的Dispatcher，这部分内容请自行浏览其它文章。

HashedWheelTimer

本节主要介绍时间轮在dubbo超时场景中的应用，关于其实现及原理这里不过多赘述。
dubbo的时间轮采用的是轮次的方式，每一轮次都有周期/间隔时间(Duration)，一个任务加入到时间轮后，时间轮并不能保证其精确的超时；
比如一个超时时间为5ms的超时任务在T1时间点加入时间轮，那么期望该任务超时T1+5ms时就被执行；但dubbo的时间轮并不是这样的，时间轮会计算当前轮次的时间点(Duration * times + startTime)，如果任务的超时时间< 当前轮次时间点，就会被执行；
以T1+5ms的任务为例，T1+5ms < (Duration * times + startTime)，该任务就会被执行，startTime是时间轮创建启动的时间点。
所以时间轮中的任务被执行的最大延迟时间是 Duration - 1
dubbo3默认的时间轮Duration是30ms

验证

时间点：

时间点	说明
start	dubbo service开始调用的时间
DefaultFuture.starttime	创建DefaultFuture的时间
DefaultFuture.inwheeltime	入时间轮的时间
DefaultFuture.senttime	发送request请求的时间
DefaultFuture.timeoutstart	超时；DefaultFuture.TimeoutCheckTask开始执行的时间
DefaultFuture.timeoutend	DefaultFuture.TimeoutCheckTask.notifyTimeout方法执行完成的时间
AllChannelHandler.receivedtime	netty接收到Result消息的时间
DefaultFuture.receivetime	DefaultFuture处理接收消息的时间
end	dubbo service方法调用结束的时间（正常响应/超时）

正常调用

1
used millis: 0
Hello dubbo generic invoke
[06/04/22 21:22:35:074 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:22:35.05, DefaultFuture.startTime: 2022-04-06T21:22:35.051, diff: 1 ms
[06/04/22 21:22:35:075 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:22:35.051, DefaultFuture.inwheeltime:2022-04-06T21:22:35.051 diff: 0 ms
[06/04/22 21:22:35:075 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:22:35.051, DefaultFuture.senttime:2022-04-06T21:22:35.055 diff: 4 ms
[06/04/22 21:22:35:075 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime:2022-04-06T21:22:35.071, DefaultFuture.senttime: 2022-04-06T21:22:35.055, diff: 16 ms
[06/04/22 21:22:35:076 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime: 2022-04-06T21:22:35.071, end:2022-04-06T21:22:35.073 diff: 2 ms
[06/04/22 21:22:35:076 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:22:35.05, end: 2022-04-06T21:22:35.073, diff: 23 ms
1
used millis: 0
Hello dubbo generic invoke
[06/04/22 21:22:36:089 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:22:36.081, DefaultFuture.startTime: 2022-04-06T21:22:36.082, diff: 1 ms
[06/04/22 21:22:36:089 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:22:36.082, DefaultFuture.inwheeltime:2022-04-06T21:22:36.082 diff: 0 ms
[06/04/22 21:22:36:090 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:22:36.082, DefaultFuture.senttime:2022-04-06T21:22:36.086 diff: 4 ms
[06/04/22 21:22:36:090 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime:2022-04-06T21:22:36.088, DefaultFuture.senttime: 2022-04-06T21:22:36.086, diff: 2 ms
[06/04/22 21:22:36:090 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime: 2022-04-06T21:22:36.088, end:2022-04-06T21:22:36.088 diff: 0 ms
[06/04/22 21:22:36:091 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:22:36.081, end: 2022-04-06T21:22:36.088, diff: 7 ms
1
used millis: 0
Hello dubbo generic invoke
[06/04/22 21:22:37:103 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:22:37.095, DefaultFuture.startTime: 2022-04-06T21:22:37.096, diff: 1 ms
[06/04/22 21:22:37:103 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:22:37.096, DefaultFuture.inwheeltime:2022-04-06T21:22:37.096 diff: 0 ms
[06/04/22 21:22:37:103 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:22:37.096, DefaultFuture.senttime:2022-04-06T21:22:37.097 diff: 1 ms
[06/04/22 21:22:37:103 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime:2022-04-06T21:22:37.102, DefaultFuture.senttime: 2022-04-06T21:22:37.097, diff: 5 ms
[06/04/22 21:22:37:103 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime: 2022-04-06T21:22:37.102, end:2022-04-06T21:22:37.102 diff: 0 ms
[06/04/22 21:22:37:103 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:22:37.095, end: 2022-04-06T21:22:37.102, diff: 7 ms
1
used millis: 0
Hello dubbo generic invoke
[06/04/22 21:22:38:116 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:22:38.108, DefaultFuture.startTime: 2022-04-06T21:22:38.109, diff: 1 ms
[06/04/22 21:22:38:116 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:22:38.109, DefaultFuture.inwheeltime:2022-04-06T21:22:38.109 diff: 0 ms
[06/04/22 21:22:38:116 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:22:38.109, DefaultFuture.senttime:2022-04-06T21:22:38.11 diff: 1 ms
[06/04/22 21:22:38:117 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime:2022-04-06T21:22:38.114, DefaultFuture.senttime: 2022-04-06T21:22:38.11, diff: 4 ms
[06/04/22 21:22:38:117 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime: 2022-04-06T21:22:38.114, end:2022-04-06T21:22:38.115 diff: 1 ms
[06/04/22 21:22:38:117 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:22:38.108, end: 2022-04-06T21:22:38.115, diff: 7 ms
1
used millis: 0
Hello dubbo generic invoke
[06/04/22 21:22:39:127 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:22:39.122, DefaultFuture.startTime: 2022-04-06T21:22:39.123, diff: 1 ms
[06/04/22 21:22:39:127 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:22:39.123, DefaultFuture.inwheeltime:2022-04-06T21:22:39.123 diff: 0 ms
[06/04/22 21:22:39:127 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:22:39.123, DefaultFuture.senttime:2022-04-06T21:22:39.124 diff: 1 ms
[06/04/22 21:22:39:128 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime:2022-04-06T21:22:39.126, DefaultFuture.senttime: 2022-04-06T21:22:39.124, diff: 2 ms
[06/04/22 21:22:39:128 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime: 2022-04-06T21:22:39.126, end:2022-04-06T21:22:39.127 diff: 1 ms
[06/04/22 21:22:39:128 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:22:39.122, end: 2022-04-06T21:22:39.127, diff: 5 ms

正常调用 provider sleep 10ms

1
used millis: 0
Hello dubbo generic invoke
[06/04/22 21:24:23:193 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:24:23.168, DefaultFuture.startTime: 2022-04-06T21:24:23.168, diff: 0 ms
[06/04/22 21:24:23:193 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:24:23.168, DefaultFuture.inwheeltime:2022-04-06T21:24:23.168 diff: 0 ms
[06/04/22 21:24:23:193 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:24:23.168, DefaultFuture.senttime:2022-04-06T21:24:23.17 diff: 2 ms
[06/04/22 21:24:23:194 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime:2022-04-06T21:24:23.192, DefaultFuture.senttime: 2022-04-06T21:24:23.17, diff: 22 ms
[06/04/22 21:24:23:194 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime: 2022-04-06T21:24:23.192, end:2022-04-06T21:24:23.193 diff: 1 ms
[06/04/22 21:24:23:194 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:24:23.168, end: 2022-04-06T21:24:23.193, diff: 25 ms
1
used millis: 0
Hello dubbo generic invoke
[06/04/22 21:24:24:214 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:24:24.198, DefaultFuture.startTime: 2022-04-06T21:24:24.199, diff: 1 ms
[06/04/22 21:24:24:214 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:24:24.199, DefaultFuture.inwheeltime:2022-04-06T21:24:24.199 diff: 0 ms
[06/04/22 21:24:24:214 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:24:24.199, DefaultFuture.senttime:2022-04-06T21:24:24.2 diff: 1 ms
[06/04/22 21:24:24:214 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime:2022-04-06T21:24:24.213, DefaultFuture.senttime: 2022-04-06T21:24:24.2, diff: 13 ms
[06/04/22 21:24:24:215 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime: 2022-04-06T21:24:24.213, end:2022-04-06T21:24:24.214 diff: 1 ms
[06/04/22 21:24:24:215 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:24:24.198, end: 2022-04-06T21:24:24.214, diff: 16 ms
1
used millis: 0
Hello dubbo generic invoke
[06/04/22 21:24:25:236 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:24:25.219, DefaultFuture.startTime: 2022-04-06T21:24:25.22, diff: 1 ms
[06/04/22 21:24:25:236 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:24:25.22, DefaultFuture.inwheeltime:2022-04-06T21:24:25.22 diff: 0 ms
[06/04/22 21:24:25:236 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:24:25.22, DefaultFuture.senttime:2022-04-06T21:24:25.221 diff: 1 ms
[06/04/22 21:24:25:237 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime:2022-04-06T21:24:25.235, DefaultFuture.senttime: 2022-04-06T21:24:25.221, diff: 14 ms
[06/04/22 21:24:25:237 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime: 2022-04-06T21:24:25.235, end:2022-04-06T21:24:25.236 diff: 1 ms
[06/04/22 21:24:25:237 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:24:25.219, end: 2022-04-06T21:24:25.236, diff: 17 ms
1
used millis: 0
Hello dubbo generic invoke
[06/04/22 21:24:26:259 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:24:26.242, DefaultFuture.startTime: 2022-04-06T21:24:26.243, diff: 1 ms
[06/04/22 21:24:26:259 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:24:26.243, DefaultFuture.inwheeltime:2022-04-06T21:24:26.243 diff: 0 ms
[06/04/22 21:24:26:259 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:24:26.243, DefaultFuture.senttime:2022-04-06T21:24:26.243 diff: 0 ms
[06/04/22 21:24:26:259 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime:2022-04-06T21:24:26.258, DefaultFuture.senttime: 2022-04-06T21:24:26.243, diff: 15 ms
[06/04/22 21:24:26:259 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime: 2022-04-06T21:24:26.258, end:2022-04-06T21:24:26.258 diff: 0 ms
[06/04/22 21:24:26:259 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:24:26.242, end: 2022-04-06T21:24:26.258, diff: 16 ms
1
used millis: 0
Hello dubbo generic invoke
[06/04/22 21:24:27:279 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:24:27.26, DefaultFuture.startTime: 2022-04-06T21:24:27.261, diff: 1 ms
[06/04/22 21:24:27:279 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:24:27.261, DefaultFuture.inwheeltime:2022-04-06T21:24:27.261 diff: 0 ms
[06/04/22 21:24:27:279 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:24:27.261, DefaultFuture.senttime:2022-04-06T21:24:27.262 diff: 1 ms
[06/04/22 21:24:27:280 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime:2022-04-06T21:24:27.277, DefaultFuture.senttime: 2022-04-06T21:24:27.262, diff: 15 ms
[06/04/22 21:24:27:280 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime: 2022-04-06T21:24:27.277, end:2022-04-06T21:24:27.278 diff: 1 ms
[06/04/22 21:24:27:280 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:24:27.26, end: 2022-04-06T21:24:27.278, diff: 18 ms
1
used millis: 0
Hello dubbo generic invoke
[06/04/22 21:24:28:304 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:24:28.284, DefaultFuture.startTime: 2022-04-06T21:24:28.286, diff: 2 ms
[06/04/22 21:24:28:305 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:24:28.286, DefaultFuture.inwheeltime:2022-04-06T21:24:28.286 diff: 0 ms
[06/04/22 21:24:28:305 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:24:28.286, DefaultFuture.senttime:2022-04-06T21:24:28.287 diff: 1 ms
[06/04/22 21:24:28:305 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime:2022-04-06T21:24:28.304, DefaultFuture.senttime: 2022-04-06T21:24:28.287, diff: 17 ms
[06/04/22 21:24:28:305 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime: 2022-04-06T21:24:28.304, end:2022-04-06T21:24:28.304 diff: 0 ms
[06/04/22 21:24:28:305 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:24:28.284, end: 2022-04-06T21:24:28.304, diff: 20 ms

超时 provider sleep 10ms, timeout 5ms 超时

1
[06/04/22 21:26:38:713 CST] Dubbo-global-shared-handler-thread-1  WARN support.DefaultFuture:  [DUBBO] The timeout response finally returned at 2022-04-06 21:26:38.713, response status is 20, channel: /192.168.1.4:53692 -> /192.168.1.4:20880, please check provider side for detailed result., dubbo version: , current host: 192.168.1.4
[06/04/22 21:26:38:725 CST] main  WARN support.FailoverClusterInvoker:  [DUBBO] Although retry the method sayHello in the service org.apache.dubbo.rpc.service.GenericService was successful by the provider 192.168.1.4:20880, but there have been failed providers [192.168.1.4:20880] (1/1) from the registry 127.0.0.1:2181 on the consumer 192.168.1.4 using the dubbo version . Last error is: Invoke remote method timeout. method: $invoke, provider: DefaultServiceInstance{serviceName='dubbo-springboot-demo-provider', host='192.168.1.4', port=20880, enabled=true, healthy=true, metadata={dubbo.endpoints=[{"port":20880,"protocol":"dubbo"}], dubbo.metadata-service.url-params={"connections":"1","version":"1.0.0","dubbo":"2.0.2","release":"3.0.8-SNAPSHOT","side":"provider","port":"20880","protocol":"dubbo"}, dubbo.metadata.revision=f33cf55bb420d0545ec1217fad84da87, dubbo.metadata.storage-type=local}}, service{name='org.apache.dubbo.springboot.demo.DemoService',group='null',version='null',protocol='dubbo',params={side=provider, release=3.0.8-SNAPSHOT, methods=sayHello,sayHelloAsync, deprecated=false, dubbo=2.0.2, interface=org.apache.dubbo.springboot.demo.DemoService, service-name-mapping=true, timeout=5, generic=false, application=dubbo-springboot-demo-provider, background=false, dynamic=true, REGISTRY_CLUSTER=zk-registry, anyhost=true},}, cause: org.apache.dubbo.remoting.TimeoutException: Waiting server-side response timeout by scan timer. start time: 2022-04-06 21:26:38.686, end time: 2022-04-06 21:26:38.698, client elapsed: 4 ms, server elapsed: 8 ms, timeout: 5 ms, request: Request [id=27, version=2.0.2, twoway=true, event=false, broken=false, data=null], channel: /192.168.1.4:53692 -> /192.168.1.4:20880, dubbo version: , current host: 192.168.1.4
org.apache.dubbo.rpc.RpcException: Invoke remote method timeout. method: $invoke, provider: DefaultServiceInstance{serviceName='dubbo-springboot-demo-provider', host='192.168.1.4', port=20880, enabled=true, healthy=true, metadata={dubbo.endpoints=[{"port":20880,"protocol":"dubbo"}], dubbo.metadata-service.url-params={"connections":"1","version":"1.0.0","dubbo":"2.0.2","release":"3.0.8-SNAPSHOT","side":"provider","port":"20880","protocol":"dubbo"}, dubbo.metadata.revision=f33cf55bb420d0545ec1217fad84da87, dubbo.metadata.storage-type=local}}, service{name='org.apache.dubbo.springboot.demo.DemoService',group='null',version='null',protocol='dubbo',params={side=provider, release=3.0.8-SNAPSHOT, methods=sayHello,sayHelloAsync, deprecated=false, dubbo=2.0.2, interface=org.apache.dubbo.springboot.demo.DemoService, service-name-mapping=true, timeout=5, generic=false, application=dubbo-springboot-demo-provider, background=false, dynamic=true, REGISTRY_CLUSTER=zk-registry, anyhost=true},}, cause: org.apache.dubbo.remoting.TimeoutException: Waiting server-side response timeout by scan timer. start time: 2022-04-06 21:26:38.686, end time: 2022-04-06 21:26:38.698, client elapsed: 4 ms, server elapsed: 8 ms, timeout: 5 ms, request: Request [id=27, version=2.0.2, twoway=true, event=false, broken=false, data=null], channel: /192.168.1.4:53692 -> /192.168.1.4:20880
	at org.apache.dubbo.rpc.protocol.AbstractInvoker.waitForResultIfSync(AbstractInvoker.java:275)
	at org.apache.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:185)
	at org.apache.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:78)
	at org.apache.dubbo.rpc.filter.GenericImplFilter.invoke(GenericImplFilter.java:125)
	at org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CopyOfFilterChainNode.invoke(FilterChainBuilder.java:321)
	at org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CallbackRegistrationInvoker.invoke(FilterChainBuilder.java:193)
	at org.apache.dubbo.rpc.cluster.support.AbstractClusterInvoker.invokeWithContext(AbstractClusterInvoker.java:378)
	at org.apache.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:80)
	at org.apache.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:340)
	at org.apache.dubbo.rpc.cluster.router.RouterSnapshotFilter.invoke(RouterSnapshotFilter.java:46)
	at org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CopyOfFilterChainNode.invoke(FilterChainBuilder.java:321)
	at org.apache.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:99)
	at org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CopyOfFilterChainNode.invoke(FilterChainBuilder.java:321)
	at org.apache.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(FutureFilter.java:51)
	at org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CopyOfFilterChainNode.invoke(FilterChainBuilder.java:321)
	at org.apache.dubbo.rpc.cluster.filter.support.ConsumerContextFilter.invoke(ConsumerContextFilter.java:109)
	at org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CopyOfFilterChainNode.invoke(FilterChainBuilder.java:321)
	at org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CallbackRegistrationInvoker.invoke(FilterChainBuilder.java:193)
	at org.apache.dubbo.rpc.cluster.support.wrapper.AbstractCluster$ClusterFilterInvoker.invoke(AbstractCluster.java:92)
	at org.apache.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:97)
	at org.apache.dubbo.registry.client.migration.MigrationInvoker.invoke(MigrationInvoker.java:280)
	at org.apache.dubbo.rpc.proxy.InvocationUtil.invoke(InvocationUtil.java:57)
	at org.apache.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:73)
	at com.alibaba.dubbo.rpc.service.GenericServiceDubboProxy1.$invoke(GenericServiceDubboProxy1.java)
	at org.apache.dubbo.demo.consumer.GenericApplication.runWithBootstrap(GenericApplication.java:86)
	at org.apache.dubbo.demo.consumer.GenericApplication.main(GenericApplication.java:46)
Caused by: java.util.concurrent.ExecutionException: org.apache.dubbo.remoting.TimeoutException: Waiting server-side response timeout by scan timer. start time: 2022-04-06 21:26:38.686, end time: 2022-04-06 21:26:38.698, client elapsed: 4 ms, server elapsed: 8 ms, timeout: 5 ms, request: Request [id=27, version=2.0.2, twoway=true, event=false, broken=false, data=null], channel: /192.168.1.4:53692 -> /192.168.1.4:20880
	at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395)
	at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2022)
	at org.apache.dubbo.rpc.AsyncRpcResult.get(AsyncRpcResult.java:195)
	at org.apache.dubbo.rpc.protocol.AbstractInvoker.waitForResultIfSync(AbstractInvoker.java:264)
	... 25 more
Caused by: org.apache.dubbo.remoting.TimeoutException: Waiting server-side response timeout by scan timer. start time: 2022-04-06 21:26:38.686, end time: 2022-04-06 21:26:38.698, client elapsed: 4 ms, server elapsed: 8 ms, timeout: 5 ms, request: Request [id=27, version=2.0.2, twoway=true, event=false, broken=false, data=null], channel: /192.168.1.4:53692 -> /192.168.1.4:20880
	at org.apache.dubbo.remoting.exchange.support.DefaultFuture.doReceived(DefaultFuture.java:229)
	at org.apache.dubbo.remoting.exchange.support.DefaultFuture.received(DefaultFuture.java:192)
	at org.apache.dubbo.remoting.exchange.support.DefaultFuture$TimeoutCheckTask.notifyTimeout(DefaultFuture.java:314)
	at org.apache.dubbo.remoting.exchange.support.DefaultFuture$TimeoutCheckTask.lambda$run$0(DefaultFuture.java:301)
	at org.apache.dubbo.common.threadpool.ThreadlessExecutor$RunnableWrapper.run(ThreadlessExecutor.java:184)
	at org.apache.dubbo.common.threadpool.ThreadlessExecutor.waitAndDrain(ThreadlessExecutor.java:103)
	at org.apache.dubbo.rpc.AsyncRpcResult.get(AsyncRpcResult.java:193)
	... 26 more
[06/04/22 21:26:38:727 CST] main  WARN proxy.InvokerInvocationHandler:  [DUBBO] [Dubbo-Consumer] execute service org.apache.dubbo.springboot.demo.DemoService#$invoke cost 41.329177 ms, this invocation almost (maybe already) timeout. Timeout: 5ms
invocation context:
path=org.apache.dubbo.springboot.demo.DemoService;
remote.application=demo-consumer;
interface=org.apache.dubbo.springboot.demo.DemoService;
version=0.0.0;
generic=true;
timeout=5;
thread info: 
Start time: 1125789532871242
+-[ Offset: 0.000000ms; Usage: 41.329177ms, 100% ] Receive request. Client invoke begin. ServiceKey: org.apache.dubbo.springboot.demo.DemoService MethodName:$invoke
  +-[ Offset: 0.520902ms; Usage: 14.979145ms, 36% ] Invoker invoke. Target Address: 192.168.1.4:20880
  +-[ Offset: 17.960444ms; Usage: 21.790695ms, 52% ] Invoker invoke. Target Address: 192.168.1.4:20880, dubbo version: , current host: 192.168.1.4
used millis: 0
Hello dubbo generic invoke
[06/04/22 21:26:38:727 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:26:38.685, DefaultFuture.startTime: 2022-04-06T21:26:38.704, diff: 19 ms
[06/04/22 21:26:38:727 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:26:38.704, DefaultFuture.inwheeltime:2022-04-06T21:26:38.705 diff: 1 ms
[06/04/22 21:26:38:727 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:26:38.704, DefaultFuture.senttime:2022-04-06T21:26:38.708 diff: 4 ms
[06/04/22 21:26:38:728 CST] main  INFO consumer.GenericApplication: DefaultFuture.senttime:2022-04-06T21:26:38.708, DefaultFuture.timeoutstart: 2022-04-06T21:26:38.698, diff: 10 ms
[06/04/22 21:26:38:728 CST] main  INFO consumer.GenericApplication: DefaultFuture.timeoutstart: 2022-04-06T21:26:38.698, DefaultFuture.timeoutend: 2022-04-06T21:26:38.7, diff: 2 ms
[06/04/22 21:26:38:728 CST] main  INFO consumer.GenericApplication: DefaultFuture.timeoutend: 2022-04-06T21:26:38.7, DefaultFuture.receivetime: 2022-04-06T21:26:38.725, diff: 25 ms
[06/04/22 21:26:38:728 CST] main  INFO consumer.GenericApplication: DefaultFuture.receivetime: 2022-04-06T21:26:38.725, end:2022-04-06T21:26:38.727 diff: 2 ms
[06/04/22 21:26:38:728 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:26:38.685, end: 2022-04-06T21:26:38.727, diff: 42 ms
1
[06/04/22 21:26:39:754 CST] Dubbo-global-shared-handler-thread-1  WARN support.DefaultFuture:  [DUBBO] The timeout response finally returned at 2022-04-06 21:26:39.754, response status is 20, channel: /192.168.1.4:53692 -> /192.168.1.4:20880, please check provider side for detailed result., dubbo version: , current host: 192.168.1.4
[06/04/22 21:26:39:769 CST] main  WARN support.FailoverClusterInvoker:  [DUBBO] Although retry the method sayHello in the service org.apache.dubbo.rpc.service.GenericService was successful by the provider 192.168.1.4:20880, but there have been failed providers [192.168.1.4:20880] (1/1) from the registry 127.0.0.1:2181 on the consumer 192.168.1.4 using the dubbo version . Last error is: Invoke remote method timeout. method: $invoke, provider: DefaultServiceInstance{serviceName='dubbo-springboot-demo-provider', host='192.168.1.4', port=20880, enabled=true, healthy=true, metadata={dubbo.endpoints=[{"port":20880,"protocol":"dubbo"}], dubbo.metadata-service.url-params={"connections":"1","version":"1.0.0","dubbo":"2.0.2","release":"3.0.8-SNAPSHOT","side":"provider","port":"20880","protocol":"dubbo"}, dubbo.metadata.revision=f33cf55bb420d0545ec1217fad84da87, dubbo.metadata.storage-type=local}}, service{name='org.apache.dubbo.springboot.demo.DemoService',group='null',version='null',protocol='dubbo',params={side=provider, release=3.0.8-SNAPSHOT, methods=sayHello,sayHelloAsync, deprecated=false, dubbo=2.0.2, interface=org.apache.dubbo.springboot.demo.DemoService, service-name-mapping=true, timeout=5, generic=false, application=dubbo-springboot-demo-provider, background=false, dynamic=true, REGISTRY_CLUSTER=zk-registry, anyhost=true},}, cause: org.apache.dubbo.remoting.TimeoutException: Waiting server-side response timeout by scan timer. start time: 2022-04-06 21:26:39.733, end time: 2022-04-06 21:26:39.751, client elapsed: 1 ms, server elapsed: 17 ms, timeout: 5 ms, request: Request [id=29, version=2.0.2, twoway=true, event=false, broken=false, data=null], channel: /192.168.1.4:53692 -> /192.168.1.4:20880, dubbo version: , current host: 192.168.1.4
org.apache.dubbo.rpc.RpcException: Invoke remote method timeout. method: $invoke, provider: DefaultServiceInstance{serviceName='dubbo-springboot-demo-provider', host='192.168.1.4', port=20880, enabled=true, healthy=true, metadata={dubbo.endpoints=[{"port":20880,"protocol":"dubbo"}], dubbo.metadata-service.url-params={"connections":"1","version":"1.0.0","dubbo":"2.0.2","release":"3.0.8-SNAPSHOT","side":"provider","port":"20880","protocol":"dubbo"}, dubbo.metadata.revision=f33cf55bb420d0545ec1217fad84da87, dubbo.metadata.storage-type=local}}, service{name='org.apache.dubbo.springboot.demo.DemoService',group='null',version='null',protocol='dubbo',params={side=provider, release=3.0.8-SNAPSHOT, methods=sayHello,sayHelloAsync, deprecated=false, dubbo=2.0.2, interface=org.apache.dubbo.springboot.demo.DemoService, service-name-mapping=true, timeout=5, generic=false, application=dubbo-springboot-demo-provider, background=false, dynamic=true, REGISTRY_CLUSTER=zk-registry, anyhost=true},}, cause: org.apache.dubbo.remoting.TimeoutException: Waiting server-side response timeout by scan timer. start time: 2022-04-06 21:26:39.733, end time: 2022-04-06 21:26:39.751, client elapsed: 1 ms, server elapsed: 17 ms, timeout: 5 ms, request: Request [id=29, version=2.0.2, twoway=true, event=false, broken=false, data=null], channel: /192.168.1.4:53692 -> /192.168.1.4:20880
	at org.apache.dubbo.rpc.protocol.AbstractInvoker.waitForResultIfSync(AbstractInvoker.java:275)
	at org.apache.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:185)
	at org.apache.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:78)
	at org.apache.dubbo.rpc.filter.GenericImplFilter.invoke(GenericImplFilter.java:125)
	at org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CopyOfFilterChainNode.invoke(FilterChainBuilder.java:321)
	at org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CallbackRegistrationInvoker.invoke(FilterChainBuilder.java:193)
	at org.apache.dubbo.rpc.cluster.support.AbstractClusterInvoker.invokeWithContext(AbstractClusterInvoker.java:378)
	at org.apache.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:80)
	at org.apache.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:340)
	at org.apache.dubbo.rpc.cluster.router.RouterSnapshotFilter.invoke(RouterSnapshotFilter.java:46)
	at org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CopyOfFilterChainNode.invoke(FilterChainBuilder.java:321)
	at org.apache.dubbo.monitor.support.MonitorFilter.invoke(MonitorFilter.java:99)
	at org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CopyOfFilterChainNode.invoke(FilterChainBuilder.java:321)
	at org.apache.dubbo.rpc.protocol.dubbo.filter.FutureFilter.invoke(FutureFilter.java:51)
	at org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CopyOfFilterChainNode.invoke(FilterChainBuilder.java:321)
	at org.apache.dubbo.rpc.cluster.filter.support.ConsumerContextFilter.invoke(ConsumerContextFilter.java:109)
	at org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CopyOfFilterChainNode.invoke(FilterChainBuilder.java:321)
	at org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CallbackRegistrationInvoker.invoke(FilterChainBuilder.java:193)
	at org.apache.dubbo.rpc.cluster.support.wrapper.AbstractCluster$ClusterFilterInvoker.invoke(AbstractCluster.java:92)
	at org.apache.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:97)
	at org.apache.dubbo.registry.client.migration.MigrationInvoker.invoke(MigrationInvoker.java:280)
	at org.apache.dubbo.rpc.proxy.InvocationUtil.invoke(InvocationUtil.java:57)
	at org.apache.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:73)
	at com.alibaba.dubbo.rpc.service.GenericServiceDubboProxy1.$invoke(GenericServiceDubboProxy1.java)
	at org.apache.dubbo.demo.consumer.GenericApplication.runWithBootstrap(GenericApplication.java:86)
	at org.apache.dubbo.demo.consumer.GenericApplication.main(GenericApplication.java:46)
Caused by: java.util.concurrent.ExecutionException: org.apache.dubbo.remoting.TimeoutException: Waiting server-side response timeout by scan timer. start time: 2022-04-06 21:26:39.733, end time: 2022-04-06 21:26:39.751, client elapsed: 1 ms, server elapsed: 17 ms, timeout: 5 ms, request: Request [id=29, version=2.0.2, twoway=true, event=false, broken=false, data=null], channel: /192.168.1.4:53692 -> /192.168.1.4:20880
	at java.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395)
	at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2022)
	at org.apache.dubbo.rpc.AsyncRpcResult.get(AsyncRpcResult.java:195)
	at org.apache.dubbo.rpc.protocol.AbstractInvoker.waitForResultIfSync(AbstractInvoker.java:264)
	... 25 more
Caused by: org.apache.dubbo.remoting.TimeoutException: Waiting server-side response timeout by scan timer. start time: 2022-04-06 21:26:39.733, end time: 2022-04-06 21:26:39.751, client elapsed: 1 ms, server elapsed: 17 ms, timeout: 5 ms, request: Request [id=29, version=2.0.2, twoway=true, event=false, broken=false, data=null], channel: /192.168.1.4:53692 -> /192.168.1.4:20880
	at org.apache.dubbo.remoting.exchange.support.DefaultFuture.doReceived(DefaultFuture.java:229)
	at org.apache.dubbo.remoting.exchange.support.DefaultFuture.received(DefaultFuture.java:192)
	at org.apache.dubbo.remoting.exchange.support.DefaultFuture$TimeoutCheckTask.notifyTimeout(DefaultFuture.java:314)
	at org.apache.dubbo.remoting.exchange.support.DefaultFuture$TimeoutCheckTask.lambda$run$0(DefaultFuture.java:301)
	at org.apache.dubbo.common.threadpool.ThreadlessExecutor$RunnableWrapper.run(ThreadlessExecutor.java:184)
	at org.apache.dubbo.common.threadpool.ThreadlessExecutor.waitAndDrain(ThreadlessExecutor.java:103)
	at org.apache.dubbo.rpc.AsyncRpcResult.get(AsyncRpcResult.java:193)
	... 26 more
[06/04/22 21:26:39:770 CST] main  WARN proxy.InvokerInvocationHandler:  [DUBBO] [Dubbo-Consumer] execute service org.apache.dubbo.springboot.demo.DemoService#$invoke cost 37.212631 ms, this invocation almost (maybe already) timeout. Timeout: 5ms
invocation context:
path=org.apache.dubbo.springboot.demo.DemoService;
remote.application=demo-consumer;
interface=org.apache.dubbo.springboot.demo.DemoService;
version=0.0.0;
generic=true;
timeout=5;
thread info: 
Start time: 1125790580464414
+-[ Offset: 0.000000ms; Usage: 37.212631ms, 100% ] Receive request. Client invoke begin. ServiceKey: org.apache.dubbo.springboot.demo.DemoService MethodName:$invoke
  +-[ Offset: 0.249678ms; Usage: 18.652652ms, 50% ] Invoker invoke. Target Address: 192.168.1.4:20880
  +-[ Offset: 19.153993ms; Usage: 17.481482ms, 46% ] Invoker invoke. Target Address: 192.168.1.4:20880, dubbo version: , current host: 192.168.1.4
used millis: 0
Hello dubbo generic invoke
[06/04/22 21:26:39:770 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:26:39.733, DefaultFuture.startTime: 2022-04-06T21:26:39.752, diff: 19 ms
[06/04/22 21:26:39:771 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:26:39.752, DefaultFuture.inwheeltime:2022-04-06T21:26:39.752 diff: 0 ms
[06/04/22 21:26:39:771 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:26:39.752, DefaultFuture.senttime:2022-04-06T21:26:39.753 diff: 1 ms
[06/04/22 21:26:39:771 CST] main  INFO consumer.GenericApplication: DefaultFuture.senttime:2022-04-06T21:26:39.753, DefaultFuture.timeoutstart: 2022-04-06T21:26:39.751, diff: 2 ms
[06/04/22 21:26:39:771 CST] main  INFO consumer.GenericApplication: DefaultFuture.timeoutstart: 2022-04-06T21:26:39.751, DefaultFuture.timeoutend: 2022-04-06T21:26:39.751, diff: 0 ms
[06/04/22 21:26:39:771 CST] main  INFO consumer.GenericApplication: DefaultFuture.timeoutend: 2022-04-06T21:26:39.751, DefaultFuture.receivetime: 2022-04-06T21:26:39.769, diff: 18 ms
[06/04/22 21:26:39:771 CST] main  INFO consumer.GenericApplication: DefaultFuture.receivetime: 2022-04-06T21:26:39.769, end:2022-04-06T21:26:39.77 diff: 1 ms
[06/04/22 21:26:39:771 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:26:39.733, end: 2022-04-06T21:26:39.77, diff: 37 ms
1
[06/04/22 21:26:40:789 CST] main  WARN proxy.InvokerInvocationHandler:  [DUBBO] [Dubbo-Consumer] execute service org.apache.dubbo.springboot.demo.DemoService#$invoke cost 16.183850 ms, this invocation almost (maybe already) timeout. Timeout: 5ms
invocation context:
path=org.apache.dubbo.springboot.demo.DemoService;
remote.application=demo-consumer;
interface=org.apache.dubbo.springboot.demo.DemoService;
version=0.0.0;
generic=true;
timeout=5;
thread info: 
Start time: 1125791620404444
+-[ Offset: 0.000000ms; Usage: 16.183850ms, 100% ] Receive request. Client invoke begin. ServiceKey: org.apache.dubbo.springboot.demo.DemoService MethodName:$invoke
  +-[ Offset: 0.536625ms; Usage: 15.576262ms, 96% ] Invoker invoke. Target Address: 192.168.1.4:20880, dubbo version: , current host: 192.168.1.4
used millis: 0
Hello dubbo generic invoke
[06/04/22 21:26:40:790 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:26:40.773, DefaultFuture.startTime: 2022-04-06T21:26:40.773, diff: 0 ms
[06/04/22 21:26:40:790 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:26:40.773, DefaultFuture.inwheeltime:2022-04-06T21:26:40.773 diff: 0 ms
[06/04/22 21:26:40:790 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:26:40.773, DefaultFuture.senttime:2022-04-06T21:26:40.774 diff: 1 ms
[06/04/22 21:26:40:790 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime:2022-04-06T21:26:40.788, DefaultFuture.senttime: 2022-04-06T21:26:40.774, diff: 14 ms
[06/04/22 21:26:40:790 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime: 2022-04-06T21:26:40.788, end:2022-04-06T21:26:40.789 diff: 1 ms
[06/04/22 21:26:40:791 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:26:40.773, end: 2022-04-06T21:26:40.789, diff: 16 ms
1
[06/04/22 21:26:41:810 CST] main  WARN proxy.InvokerInvocationHandler:  [DUBBO] [Dubbo-Consumer] execute service org.apache.dubbo.springboot.demo.DemoService#$invoke cost 15.095078 ms, this invocation almost (maybe already) timeout. Timeout: 5ms
invocation context:
path=org.apache.dubbo.springboot.demo.DemoService;
remote.application=demo-consumer;
interface=org.apache.dubbo.springboot.demo.DemoService;
version=0.0.0;
generic=true;
timeout=5;
thread info: 
Start time: 1125792642017715
+-[ Offset: 0.000000ms; Usage: 15.095078ms, 100% ] Receive request. Client invoke begin. ServiceKey: org.apache.dubbo.springboot.demo.DemoService MethodName:$invoke
  +-[ Offset: 0.193376ms; Usage: 14.856755ms, 98% ] Invoker invoke. Target Address: 192.168.1.4:20880, dubbo version: , current host: 192.168.1.4
used millis: 0
Hello dubbo generic invoke
[06/04/22 21:26:41:810 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:26:41.794, DefaultFuture.startTime: 2022-04-06T21:26:41.794, diff: 0 ms
[06/04/22 21:26:41:810 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:26:41.794, DefaultFuture.inwheeltime:2022-04-06T21:26:41.794 diff: 0 ms
[06/04/22 21:26:41:810 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:26:41.794, DefaultFuture.senttime:2022-04-06T21:26:41.795 diff: 1 ms
[06/04/22 21:26:41:810 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime:2022-04-06T21:26:41.809, DefaultFuture.senttime: 2022-04-06T21:26:41.795, diff: 14 ms
[06/04/22 21:26:41:811 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime: 2022-04-06T21:26:41.809, end:2022-04-06T21:26:41.81 diff: 1 ms
[06/04/22 21:26:41:811 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:26:41.794, end: 2022-04-06T21:26:41.81, diff: 16 ms
1
[06/04/22 21:26:42:829 CST] main  WARN proxy.InvokerInvocationHandler:  [DUBBO] [Dubbo-Consumer] execute service org.apache.dubbo.springboot.demo.DemoService#$invoke cost 17.188159 ms, this invocation almost (maybe already) timeout. Timeout: 5ms
invocation context:
path=org.apache.dubbo.springboot.demo.DemoService;
remote.application=demo-consumer;
interface=org.apache.dubbo.springboot.demo.DemoService;
version=0.0.0;
generic=true;
timeout=5;
thread info: 
Start time: 1125793659747795
+-[ Offset: 0.000000ms; Usage: 17.188159ms, 100% ] Receive request. Client invoke begin. ServiceKey: org.apache.dubbo.springboot.demo.DemoService MethodName:$invoke
  +-[ Offset: 0.304199ms; Usage: 16.808201ms, 97% ] Invoker invoke. Target Address: 192.168.1.4:20880, dubbo version: , current host: 192.168.1.4
used millis: 0
Hello dubbo generic invoke
[06/04/22 21:26:42:830 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:26:42.812, DefaultFuture.startTime: 2022-04-06T21:26:42.812, diff: 0 ms
[06/04/22 21:26:42:830 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:26:42.812, DefaultFuture.inwheeltime:2022-04-06T21:26:42.812 diff: 0 ms
[06/04/22 21:26:42:830 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:26:42.812, DefaultFuture.senttime:2022-04-06T21:26:42.813 diff: 1 ms
[06/04/22 21:26:42:830 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime:2022-04-06T21:26:42.829, DefaultFuture.senttime: 2022-04-06T21:26:42.813, diff: 16 ms
[06/04/22 21:26:42:830 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime: 2022-04-06T21:26:42.829, end:2022-04-06T21:26:42.829 diff: 0 ms
[06/04/22 21:26:42:830 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:26:42.812, end: 2022-04-06T21:26:42.829, diff: 17 ms
1
[06/04/22 21:26:43:846 CST] main  WARN proxy.InvokerInvocationHandler:  [DUBBO] [Dubbo-Consumer] execute service org.apache.dubbo.springboot.demo.DemoService#$invoke cost 14.162471 ms, this invocation almost (maybe already) timeout. Timeout: 5ms
invocation context:
path=org.apache.dubbo.springboot.demo.DemoService;
remote.application=demo-consumer;
interface=org.apache.dubbo.springboot.demo.DemoService;
version=0.0.0;
generic=true;
timeout=5;
thread info: 
Start time: 1125794679162714
+-[ Offset: 0.000000ms; Usage: 14.162471ms, 100% ] Receive request. Client invoke begin. ServiceKey: org.apache.dubbo.springboot.demo.DemoService MethodName:$invoke
  +-[ Offset: 0.202243ms; Usage: 13.917734ms, 98% ] Invoker invoke. Target Address: 192.168.1.4:20880, dubbo version: , current host: 192.168.1.4
used millis: 0
Hello dubbo generic invoke
[06/04/22 21:26:43:846 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:26:43.831, DefaultFuture.startTime: 2022-04-06T21:26:43.832, diff: 1 ms
[06/04/22 21:26:43:846 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:26:43.832, DefaultFuture.inwheeltime:2022-04-06T21:26:43.832 diff: 0 ms
[06/04/22 21:26:43:846 CST] main  INFO consumer.GenericApplication: DefaultFuture.startTime: 2022-04-06T21:26:43.832, DefaultFuture.senttime:2022-04-06T21:26:43.832 diff: 0 ms
[06/04/22 21:26:43:846 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime:2022-04-06T21:26:43.845, DefaultFuture.senttime: 2022-04-06T21:26:43.832, diff: 13 ms
[06/04/22 21:26:43:846 CST] main  INFO consumer.GenericApplication: AllChannelHandler.receivedtime: 2022-04-06T21:26:43.845, end:2022-04-06T21:26:43.846 diff: 1 ms
[06/04/22 21:26:43:846 CST] main  INFO consumer.GenericApplication: start: 2022-04-06T21:26:43.831, end: 2022-04-06T21:26:43.846, diff: 15 ms

可以看到虽然设置了超时时间5ms,provider 在10ms后返回，可是consumer仍然在15ms的时候正常接收到响应信息，原因就是consumer在收到provider响应时，时间轮中的超时任务还没有被执行，这跟时间轮的tickDuration有关；
以超时时间为5ms的RPC场景为例，时间轮的tickDuration为30ms时间线如下：
T0: 创建时间轮，T0 + (30ms * n) 的时间点执行时间轮中过期的超时任务，n每隔30ms递增+1;
T1: 调用service 方法；
T2: 超时任务 OverTimeTask1 添加到时间轮，期望在T2 + 5ms时执行OverTimeTask1；
T3: = T0 + (30ms * 1) 执行超时任务列表；此时OverTimeTask1并不一定会执行，因为可能存在 (T2 + 5ms) > (T0 + 30ms * 1) 的情况，如果是这种情况，将会在T0 + (30ms * 2) 时执行；

不管如何OverTimeTask1的执行肯定是会延迟的，延迟时间计算公式： delayTime = T0 + (30ms * n) - (T2 + 5ms)

Dubbo2请求超时

Dubbo2请求超时等待采用JUC中的Condition的超时等待，超时时间几乎不存在误差

你可能感兴趣的:(Dubbo,dubbo,超时,时间轮)

为什么wal会提升数据库性能浩澜大大数据库
由于对于一个数据库内会存在很多张表，那么当数据库更新表数据时（1）直接写入磁盘实际写入的位置，会根据表的不同对应到不同的磁盘位置，在写入数据的时候，就会不停的寻找磁盘地址，找到地址后再去写入，对于机械硬盘来说，无规律的寻址是非常耗时的，对应SSD来说虽然性能提升很多，但是也会消耗时间；（2）先写入日志，在写入磁盘（WAL）WAL的过程，由于总是按照在文件末尾追加，只要找到文件写入位置，写入修改后，
亲子日记之祝姑姥姥生日快乐（282）冰心雨露_d504
2021年7月18日，周日，晴周日上班的不上班，上学的不上学，全家都属于休息状态，洗衣做饭是上午的主要任务，中午休息一会儿，下午比较晚了出去给梦怡买了二年级上册的口算题卡，然后去参加姑姑的生日聚餐，本来姑姑应该是周一生日，因为周一都要上班，就提前到周日过了，说是过生日其实就是想借此机会一家人聚聚，毕竟平常都忙，没有时间聚在一起，梦怡还给姑姥姥做了生日贺卡，虽然长相一般，重在心意。生日快乐
100天30本书读书计划（2018-06-11）DAY 62 一个姜姜
【书名】当我谈跑步时，我谈些什么【作者】村上春树【读书页数】51--128/187【读书时间】2018年6月11日【精彩句子】01肌肉难长，易消。赘肉易长，难消。P5502肌肉也同有血有肉的动物一般无二，它也愿意过更舒服的日子，不继续给它负荷，它便会心安理得地将记忆出去。想再度输入的话，必须得从头开始，将同样的模式重复一遍。P7703不管怎样，反正得坚持跑步。每天跑步对我来说好比生命线，不能说忙就
2019-04-08早梦雅的简动力
在上瑜伽课前10分钟的调息中，你的眼睛为什么总是想睁开？（焦虑）。你的眉头为什么总是紧锁？（压力）。练习体式时你为什么总是去看别人？（攀比）保持体式时你为什么总是烦躁？（性急）。保持长久而规律的练习，以上这些，终归离你远去。瑜伽，首先，不是帮你得到，而是教你放下。图片发自App时间，一时间无法跳离这个特殊的词汇毅力，坚持，真诚，需要时间来见证真相，现实，伪装，时间自然会揭秘珍惜它又害怕它可它丝毫不
被隔离的日子（五）@三七会写作营三七会萍海临风
从隔离的初期，我们三人都不适应，彼此说话都还火药味十足。后随着时间的推移，到现在，我们仨人能够心平气和，幽默地对待彼此。看来，时间可真是个好东西，不仅能见证一个人的心性，还能看清自己的需求、他人的本质。今天晚上，孩子跑到厨房，告诉我她给人捐款了。我纳闷，不是给河南捐过款了么。当时，我还落后于她捐的呢。这次又捐给谁？看到我一脸狐疑，孩子说，还记得初四给她补课的那个男老师么？当让记得，当时，就因为是男
unblock with ‘mysqladmin flush-hosts‘ 解决方法祈祷平安,加油数据库常见问题 oracle 数据库
MySqlHostisblockedbecauseofmanyconnectionerrors;unblockwith'mysqladminflush-hosts'解决方法环境：linux，mysql5.5.21错误：Hostisblockedbecauseofmanyconnectionerrors;unblockwith'mysqladminflush-hosts'原因：同一个ip在短时间内产
现在的婚姻是: 高彩礼和诸多要求让感情越来越淡漠朦蒙哒
很多人搞不明白为什么现在的人对婚姻的质量要求那么高可就是维持不了多久时间，有不少人的婚姻是用礼金堆起来的，但恰恰是这些人最容易夫妻感情出问题导致离婚收场。现在的婚姻让年轻人失望，年轻人为什么对婚姻失望甚至没了渴望，无非就是这几个原因01彩礼高了感情淡了我们都知道，结婚要的高彩礼把很多年轻人给搞怕了，搞得很多年轻人都不敢结婚生子了，可以说彩礼高了让很多男女都失去了真感情，就算能在一起也只是男人需要老
学习JavaEE的日子 Day32 线程池 A 北枝学习JavaEE 学习 java-ee java 线程池
Day32线程池1.引入一个线程完成一项任务所需时间为：创建线程时间-Time1线程中执行任务的时间-Time2销毁线程时间-Time32.为什么需要线程池(重要)线程池技术正是关注如何缩短或调整Time1和Time3的时间，从而提高程序的性能。项目中可以把Time1，T3分别安排在项目的启动和结束的时间段或者一些空闲的时间段线程池不仅调整Time1，Time3产生的时间段，而且它还显著减少了创建
淘宝天猫38节活动时间和玩法，2024年焕新周满减优惠多少小小编007
在2024年，淘宝天猫平台即将迎来一年一度的38节活动，这是广大消费者们翘首以待的购物狂欢节。在这篇文章中，我们将为您详细解读淘宝天猫38节活动的时间安排和玩法，以及2024年焕新周的满减优惠力度。一、淘宝天猫38节活动时间2024年淘宝天猫38节活动将于2月28日正式启动，持续至3月8日，为期10天。活动期间，消费者们可以尽情享受各种优惠折扣、满减活动以及限时秒杀，尽情释放购物热情。2024淘宝
所有的突然想起，都是一直放在心里清浅白芷
一天，看到朋友圈发了一张木林的图片，熟悉而又陌生，心里怔住了一下，突然想起他以及往事。想起那年我们在旅途认识，而后又因旅途分开的故事。点点滴滴，在脑海里盘旋，在回忆里辗转。还记得相遇的那天，因为他的幽默风趣，把全场疲惫不堪的人逗笑了，他笑起来的样子不是很好看，但感觉很舒服。后来我们通过在网上联系，加深了对彼此的了解，便互生情愫，然后恋爱。只是后来，经过一年多的相处，我们就分开了。虽然时间很短，但仿
黔东南——苗年（一）非常道yw
苗年是雷山县苗族同胞最隆重的民族传统节日，也是苗族人一年中庆祝丰收和最重要的祭祀性的日子，更是雷山苗族一年里劳作的结束和欢乐的开始。如同汉族的春节。节日期间，各村寨都要举行跳芦笙、篮球赛、斗牛、赛马、斗鸟、铜鼓舞、篝火晚会等民间传统娱乐活动。苗年也是最集中地展示苗族服饰、银饰、手工艺美术等有形文化的节日，时间大都在农历十月。苗族认为，一年只有热、冷两个季节，热季和冷季交替的农历十月，既是热季的结束
手机上赚钱？学会这5种方法！高省app让你轻松赚钱！高省浮沉000018
随着智能手机的普及，越来越多的人开始探索在手机上赚钱的方法。不仅可以利用碎片时间增加收入，还能减少对传统办公室工作的依赖。本文将向您介绍5种在手机上赚钱的方法，并推荐一款高省app，帮助您实现手机赚钱的目标。大家好！我是高省APP最大团队&联合创始人浮沉导师！【高省】APP网购优惠券免费领，分享还能赚钱。【高省】是一个自用省钱佣金高，分享推广赚钱多的平台。佣金更高，模式更好，终端用户不流失。0投资
没有如释重负君远近
虽然只有短短的一个多月的努力复习时间，但今天的整个考试经过，还是发现了效果的，题目做的比较自如，没有慌里慌张，而且提前五分钟完成。至于考试成绩，没有实足的把握，60分都不敢保证。但绝对相信自己，比去年肯定要好！今天早早的赶到考场，见到了刘老师，谈起来学习情况，坦率的说，真的是自己不够重视。总以为会很难，没有信心。其实不是的，只要认真对待，树立足够的信心，绝对可以通过考试的。还向老师询问了，后续再报
暗示的可怕力量，这些话永远不要对孩子说浅来浅去
记得春节的时候，在亲戚家的饭桌上。跟我同坐的是亲戚家的一位老姑父。同桌的几位熟人跟老人谈论他的孙子。“他现在变化真的很大，不错不错！”“我们前段时间遇到他，觉得他现在工作很认真，会有出息的。”“唉，你们不要说了，我还不知道他什么样，快30岁的人了，一事无成。”他说自己不相信。我跟他说，“您得相信他会改变，因为家人相信他会改变，有时真的会改变的。”“您得给他一些正面的暗示。”那天老人脸色凝重，喝了不
为千佩蓉：为家庭放弃事业的男人没出息吗？北京朵多教育
为家庭放弃事业的男人没出息吗我们在搭档的过程中会遇到一些问题，因此要做好心理准备，这样才不会陷入抱怨或双输的局面。关键不是谁比谁能力强，而是夫妻之间如何取长补短。家庭要赢需要每个人的付出和牺牲，大家一起分担和负责，这样才能享受相爱的自由、安全和归属感。我们需要做的牺牲包括自己的时间、自己的一些爱好，甚至事业发展。为千认为做好父亲是非常重要的事，所以他不仅要出席在孩子们的生活中，还要积极地参与和带领
【计算机网络】第 3 问：电路交换、报文交换、分组交换之间的区别？孤独打铁匠Julian #计算机408考研面试计算机网络计算机网络网络
电路交换、报文交换、分组交换之间的区别？省流图详解电路交换电路交换的优点电路交换的缺点建立连接时间长的原因报文交换报文交换的优点报文交换的缺点分组交换分组交换的优点分组交换的缺点比较总结省流图详解电路交换在进行数据传输前，两个结点之间必须先建立一条专用（双方独占）的物理通信路径（由通信双方之间的交换设备和链路逐段连接而成），该路径可能经过许多中间结点。这一路径在整个数据传输期间一直被独占，直到通信
CSV指南：Python程序获取大型CSV文件行数孤独打铁匠Julian 笔记经验分享 python
本指南提供了几种使用Python来获取大型CSV文件行数的方法，并解释了每种方法的适用场景。方法1:使用csv.reader处理复杂CSV文件当你的CSV文件中包含多行字段（即某些字段的值中包含换行符）时，使用csv.reader是一个可靠的选择，因为它能够正确处理这些复杂情况。这个方法适用于大多数大小的CSV文件，但是对于非常大的文件，读取整个文件可能会占用较多的时间和内存。对于极大的文件，考虑
浇灌根部山静幽兰
“浇灌根部。”对，浇灌根部。张学青点醒了我。无论是我自己，还是我学生，都，正需要浇灌。正因为虚度了那么多岁月，不曾懂得浇灌自己，我这棵树才长得如此缓慢，四十多岁才长成今天这个样子。好在我现在的学生还小，犹如一棵棵小芽，浇灌正是时候。是的，要浇就浇根部。我的根，在课堂。根在课堂，就认认真真读书，读有“盐”的书，长智的书。以前也常看那些抚慰灵魂的“心灵鸡汤”，但时间长了觉得发腻，对我的语文教学也帮不了
常用API---初始化，话题和服务对象创建，回旋/头函数，时间（如：获取当前时刻，持续时间执行频率，休眠，定时器等），运行频率，定时器，节点生命周期，日志相关API 李卓璐机器人人工智能 c++
初始化ROS节点ros::init(argc,argv,“name”,options);作用：ros初始化函数参数： 1.argc—封装实参的个数（n+1个->有一个是自身）； 2.argv—封装参数的数组； 3.name—为节点命名（唯一性）； 4.options—节点启动项，解决节点重名问题。返回值：void使用： 1.argc和argv的使用：如果按照ROS中的特定格式传入实参，那么RO
ChatGPT一路狂飙？何鲸洛
2月2日。根据投行瑞银集团在周三发布的一份研究报告。爆红聊天机器人ChatGPT的月活跃用户在今年1月份预计达到了1亿，这距离它推出只有2个月时间，成为史上增长最快的消费者应用。①ChatGPT一路火花带闪电？▽2014年。OpenAI创始人SamAltman早年曾执掌著名的硅谷孵化器YCombinator。2015年。Altman联合马斯克、彼得·泰尔、AWS、印度Infosys和YC等作为出资
家长们的福音：教师对书面作业全批全改，学校不得考试选拔学生丝雨润春风
年前年后教育部门公布了不少措施，来减轻学生负担，维护学生的身心健康成长，随后各地教育局也陆陆续续颁布了各种新政策，这不最近山东教育厅也起草了《山东普通中小学规范办学十五条规定》。在这15条规定内容之中包括了：教师对书面作业全批全改，不给家长布置作业或要求家长评改作业；义务教育学校不得以考试、面试、评测等名义选拔学生；保障学生每天睡眠时间，高中生不少于8个小时。毋庸置疑这个规定的初衷非常得好，是对学
2022-2-13晨间日记越亮也打烊
今天是什么日子起床：7:00就寝：12:08天气：晴心情：糟糕纪念日：无任务清单昨日完成的任务，最重要的三件事：寒假作业，网课，画画改进：作业时间剪短习惯养成：网课不逃～周目标·完成进度数学卷子100％学习·信息·阅读《傅雷家书》《钢铁是怎样炼成的》健康·饮食·锻炼我终于不喝饮料啦，喝茶～人际·家人·朋友邝姐姐带我吃火锅工作·思考啥时候开学，我还有几天赶完作业最美好的三件事1.卷子写完了2.我有冰
中国大学：你站起来！立恒语文
我们先来看看中国大学对外国留学生的“奇葩”待遇。近日，有网友曝出吉林大学有要求中国学生起床后须叫醒外国留学生的服务。看完之后，真是让人大跌眼镜。有网友就直接质问：吉大是大学，还是酒店？中国学生是学生，还是服务员？外国留学生是来求学的，还是享受的？这不仅让人联想到最近一段时间以来网上频频曝出的许多中国大学对外国留学生的一些“奇葩”待遇，这里举几个比较有名的事例，以飨读者。1.山东大学的“三陪”制度，
【转载】SSD测试第一神器——FIO running_sheep
转自：[http://www.ssdfans.com]对于SSD性能测试来说，最好的工具莫过于FIO了。FIO是Jens开发的一个开源测试工具，功能非常强大，本文就只介绍其中一些基本功能。线程，队列深度，Offset，同步异步，DirectIO，BIO使用FIO之前，首先要有一些SSD性能测试的基础知识。线程指的是同时有多少个读或写任务在并行执行，一般来说，CPU里面的一个核心同一时间只能运行一个
#D174-读书会作业-《财务自由之路》3 白洲笔记
最近沉迷于写作营，一直就没时间去弄读书会的作业，书的第二遍也就看了个开头，趁着日更的时间，赶紧把作业做了，这次是15到21课。【1.印象最深刻的部分】(本周所读内容中印象最深刻的部分)*活在未来，最正确的方法是什么？用正确的方法做正确的事情，判断什么是正确的？逻辑。学会思考。"作对事情"永远比“把事情作对“重要的多。”长远思考，耐心验证，小心总结提炼“证明自己正确并不是学习的任务和目标，时刻成长，
感恩日志第【1210】天：（2019.02.01）（腊月二十七）山东慧恩贺守金
今日感悟：二十七撇松枝！今日是真正的第一天假期：吃饭找物业看望父母打麻将。时间过的飞快，转眼间，已经放假5天了，保养车，购置年货，送礼，出差，回家。春节假期：陪伴父母、妻儿的时间，反思的时间，规划的时间。白天太忙，忙着各种琐事，晚上才真正有时间留给自己，思考，总结。感恩这一个充实而忙碌的一天。
Flutter运行flutter doctor 命令长时间未响应如何解决咕噜签名分发-淼淼 flutter
Hello大家好！我是咕噜铁蛋！在移动应用开发领域，Flutter以其高效、跨平台的特性吸引了众多开发者的关注。然而，在使用Flutter进行项目开发时，开发者可能会遇到各种问题，其中之一就是运行flutterdoctor命令时长时间未响应。今天铁蛋将深入探讨这一问题的成因、解决方案以及相关的Flutter环境配置知识。一、Flutter与flutterdoctor命令简介Flutter是Goog
搜索，动态规划，二叉树的时间复杂度计算通用公式鸭蛋蛋_8441
搜索的时间复杂度：O(答案总数*构造每个答案的时间)举例：Subsets问题，求所有的子集。子集个数一共2^n，每个集合的平均长度是O(n)的，所以时间复杂度为O(n*2^n)，同理Permutations问题的时间复杂度为：O(n*n!)动态规划的时间复杂度：O(状态总数*计算每个状态的时间复杂度)举例：triangle，数字三角形的最短路径，状态总数约O(n^2)个，计算每个状态的时间复杂度为
2.5 项目讲解流程王守谦26 项目资料数据库
一、项目讲解1、自我介绍2、项目流程-===============================二、自我介绍（一）、学员自我介绍，讲解存在的问题比如：讲解年份、卡顿、重点学历、忘记（二）自我规则内容1、开场白：礼貌用语2、时间：自我介绍1-2分钟以内3、内容：姓名、籍贯、毕业院校、（拉进面试官距离）4、技能：功能测试、接口测试、自动化测试、app测试、性能测试、安全测试黑盒测试、白盒测试、灰盒
过去一年，这16本好书不容错过 m0_54050778 perl
编者按：2023年在动荡与希望中收尾，2023年注定会被载入史册。疫情寒冬结束，ChatGPT横空出世，带动了人工智能技术的飞速发展；淄博烧烤、天津大爷、尔滨之旅等充满感动与幸福。但与此同时，2023年又是动荡与不安的一年，俄乌冲突的延宕，新一轮的巴以冲突，极端天气频发。在这个大环境下，有一些经典的书籍著作诞生。本文将分享2023年最值得一读的16本书籍，文章来自翻译，希望对你有所启示。关于202
集合框架天子之骄 java 数据结构集合框架
集合框架集合框架可以理解为一个容器，该容器主要指映射(map)、集合(set)、数组(array)和列表(list)等抽象数据结构。从本质上来说，Java集合框架的主要组成是用来操作对象的接口。不同接口描述不同的数据类型。简单介绍： Collection接口是最基本的接口，它定义了List和Set，List又定义了LinkLi
Table Driven（表驱动）方法实例 bijian1013 java enum Table Driven 表驱动
实例一： /** * 驾驶人年龄段 * 保险行业，会对驾驶人的年龄做年龄段的区分判断 * 驾驶人年龄段：01-[18,25);02-[25,30);03-[30-35);04-[35,40);05-[40,45);06-[45,50);07-[50-55);08-[55,+∞) */ public class AgePeriodTest { //if...el
Jquery 总结 cuishikuan java jquery Ajax Web jquery方法
1.$.trim方法用于移除字符串头部和尾部多余的空格。如：$.trim(' Hello ') // Hello2.$.contains方法返回一个布尔值，表示某个DOM元素（第二个参数）是否为另一个DOM元素（第一个参数）的下级元素。如：$.contains(document.documentElement, document.body); 3.$
面向对象概念的提出麦田的设计者 java 面向对象面向过程
面向对象中，一切都是由对象展开的，组织代码，封装数据。在台湾面向对象被翻译为了面向物件编程，这充分说明了，这种编程强调实体。下面就结合编程语言的发展史，聊一聊面向过程和面向对象。 c语言由贝尔实
linux网口绑定被触发 linux
刚在一台IBM Xserver服务器上装了RedHat Linux Enterprise AS 4，为了提高网络的可靠性配置双网卡绑定。一、环境描述我的RedHat Linux Enterprise AS 4安装双口的Intel千兆网卡，通过ifconfig -a命令看到eth0和eth1两张网卡。二、双网卡绑定步骤： 2.1 修改/etc/sysconfig/network
XML基础语法肆无忌惮_ xml
一、什么是XML？ XML全称是Extensible Markup Language，可扩展标记语言。很类似HTML。XML的目的是传输数据而非显示数据。XML的标签没有被预定义，你需要自行定义标签。XML被设计为具有自我描述性。是W3C的推荐标准。二、为什么学习XML？用来解决程序间数据传输的格式问题做配置文件充当小型数据库三、XML与HTM
为网页添加自己喜欢的字体知了ing 字体秒表 css
@font-face { font-family: miaobiao;//定义字体名字 font-style: normal; font-weight: 400; src: url('font/DS-DIGI-e.eot');//字体文件 } 使用： <label style="font-size:18px;font-famil
redis范围查询应用-查找IP所在城市矮蛋蛋 redis
原文地址： http://www.tuicool.com/articles/BrURbqV 需求根据IP找到对应的城市原来的解决方案 oracle表（ip_country）：查询IP对应的城市： 1.把a.b.c.d这样格式的IP转为一个数字，例如为把210.21.224.34转为3524648994 2. select city from ip_
输入两个整数，计算百分比 alleni123 java
public static String getPercent(int x, int total){ double result=(x*1.0)/(total*1.0); System.out.println(result); DecimalFormat df1=new DecimalFormat("0.0000%");
百合——————>怎么学习计算机语言百合不是茶 java 移动开发
对于一个从没有接触过计算机语言的人来说，一上来就学面向对象，就算是心里上面接受的了，灵魂我觉得也应该是跟不上的，学不好是很正常的现象，计算机语言老师讲的再多，你在课堂上面跟着老师听的再多，我觉得你应该还是学不会的，最主要的原因是你根本没有想过该怎么来学习计算机编程语言，记得大一的时候金山网络公司在湖大招聘我们学校一个才来大学几天的被金山网络录取，一个刚到大学的就能够去和
linux下tomcat开机自启动 bijian1013 tomcat
方法一：修改Tomcat/bin/startup.sh 为: export JAVA_HOME=/home/java1.6.0_27 export CLASSPATH=$CLASSPATH:$JAVA_HOME/lib/tools.jar:$JAVA_HOME/lib/dt.jar:. export PATH=$JAVA_HOME/bin:$PATH export CATALINA_H
spring aop实例 bijian1013 java spring AOP
1.AdviceMethods.java package com.bijian.study.spring.aop.schema; public class AdviceMethods { public void preGreeting() { System.out.println("--how are you!--"); } } 2.beans.x
[Gson八]GsonBuilder序列化和反序列化选项enableComplexMapKeySerialization bit1129 serialization
enableComplexMapKeySerialization配置项的含义 Gson在序列化Map时，默认情况下，是调用Key的toString方法得到它的JSON字符串的Key，对于简单类型和字符串类型，这没有问题，但是对于复杂数据对象，如果对象没有覆写toString方法，那么默认的toString方法将得到这个对象的Hash地址。 GsonBuilder用于
【Spark九十一】Spark Streaming整合Kafka一些值得关注的问题 bit1129 Stream
包括Spark Streaming在内的实时计算数据可靠性指的是三种级别： 1. At most once，数据最多只能接受一次，有可能接收不到 2. At least once, 数据至少接受一次，有可能重复接收 3. Exactly once 数据保证被处理并且只被处理一次，具体的多读几遍http://spark.apache.org/docs/lates
shell脚本批量检测端口是否被占用脚本 ronin47
#!/bin/bash cat ports |while read line do#nc -z -w 10 $line nc -z -w 2 $line 58422>/dev/null2>&1if[ $?-eq 0]then echo $line:ok else echo $line:fail fi done 这里的ports 既可以是文件
java-2.设计包含min函数的栈 bylijinnan java
具体思路参见：http://zhedahht.blog.163.com/blog/static/25411174200712895228171/ import java.util.ArrayList; import java.util.List; public class MinStack { //maybe we can use origin array rathe
Netty源码学习-ChannelHandler bylijinnan java netty
一般来说，“有状态”的ChannelHandler不应该是“共享”的，“无状态”的ChannelHandler则可“共享” 例如ObjectEncoder是“共享”的, 但 ObjectDecoder 不是因为每一次调用decode方法时，可能数据未接收完全（incomplete），它与上一次decode时接收到的数据“累计”起来才有可能是完整的数据，是“有状态”的 p
java生成随机数 cngolon java
方法一： /** * 生成随机数 * @author [email protected] * @return */ public synchronized static String getChargeSequenceNum(String pre){ StringBuffer sequenceNum = new StringBuffer(); Date dateTime = new D
POI读写海量数据 ctrain 海量数据
import java.io.FileOutputStream; import java.io.OutputStream; import org.apache.poi.xssf.streaming.SXSSFRow; import org.apache.poi.xssf.streaming.SXSSFSheet; import org.apache.poi.xssf.streaming
mysql 日期格式化date_format详细使用 daizj mysql date_format 日期格式转换日期格式化
日期转换函数的详细使用说明 DATE_FORMAT(date,format) Formats the date value according to the format string. The following specifiers may be used in the format string. The&n
一个程序员分享8年的开发经验 dcj3sjt126com 程序员
在中国有很多人都认为IT行为是吃青春饭的，如果过了30岁就很难有机会再发展下去!其实现实并不是这样子的，在下从事.NET及JAVA方面的开发的也有8年的时间了，在这里在下想凭借自己的亲身经历，与大家一起探讨一下。明确入行的目的很多人干IT这一行都冲着“收入高”这一点的，因为只要学会一点HTML, DIV+CSS，要做一个页面开发人员并不是一件难事，而且做一个页面开发人员更容
android欢迎界面淡入淡出效果 dcj3sjt126com android
很多Android应用一开始都会有一个欢迎界面，淡入淡出效果也是用得非常多的，下面来实现一下。主要代码如下： package com.myaibang.activity; import android.app.Activity;import android.content.Intent;import android.os.Bundle;import android.os.CountDown
linux 复习笔记之常见压缩命令 eksliang tar解压 linux系统常见压缩命令 linux压缩命令 tar压缩
转载请出自出处:http://eksliang.iteye.com/blog/2109693 linux中常见压缩文件的拓展名 *.gz gzip程序压缩的文件 *.bz2 bzip程序压缩的文件 *.tar tar程序打包的数据，没有经过压缩 *.tar.gz tar程序打包后，并经过gzip程序压缩 *.tar.bz2 tar程序打包后，并经过bzip程序压缩 *.zi
Android 应用程序发送shell命令 gqdy365 android
项目中需要直接在APP中通过发送shell指令来控制lcd灯，其实按理说应该是方案公司在调好lcd灯驱动之后直接通过service送接口上来给APP，APP调用就可以控制了，这是正规流程，但我们项目的方案商用的mtk方案，方案公司又没人会改，只调好了驱动，让应用程序自己实现灯的控制，这不蛋疼嘛！！！！发就发吧！一、关于shell指令：我们知道，shell指令是Linux里面带的
java 无损读取文本文件 hw1287789687 读取文件无损读取读取文本文件 charset
java 如何无损读取文本文件呢？以下是有损的 @Deprecated public static String getFullContent(File file, String charset) { BufferedReader reader = null; if (!file.exists()) { System.out.println("getFull
Firebase 相关文章索引 justjavac firebase
Awesome Firebase 最近谷歌收购Firebase的新闻又将Firebase拉入了人们的视野，于是我做了这个 github 项目。 Firebase 是一个数据同步的云服务，不同于 Dropbox 的「文件」，Firebase 同步的是「数据」，服务对象是网站开发者，帮助他们开发具有「实时」（Real-Time）特性的应用。开发者只需引用一个 API 库文件就可以使用标准 RE
C++学习重点 lx.asymmetric C++笔记
1.c++面向对象的三个特性：封装性，继承性以及多态性。 2.标识符的命名规则：由字母和下划线开头，同时由字母、数字或下划线组成；不能与系统关键字重名。 3.c++语言常量包括整型常量、浮点型常量、布尔常量、字符型常量和字符串性常量。 4.运算符按其功能开以分为六类：算术运算符、位运算符、关系运算符、逻辑运算符、赋值运算符和条件运算符。 &n
java bean和xml相互转换 q821424508 java bean xml xml和bean转换 java bean和xml转换
这几天在做微信公众号做的过程中想找个java bean转xml的工具，找了几个用着不知道是配置不好还是怎么回事，都会有一些问题，然后脑子一热谢了一个javabean和xml的转换的工具里，自己用着还行，虽然有一些约束吧，还是贴出来记录一下顺便你提一下下，这个转换工具支持属性为集合、数组和非基本属性的对象。 packag
C 语言初级位运算 1140566087 位运算 c
第十章位运算 1、位运算对象只能是整形或字符型数据，在VC6.0中int型数据占4个字节 2、位运算符：运算符作用 ~ 按位求反 << 左移 >> 右移 & 按位与 ^ 按位异或 | 按位或他们的优先级从高到低； 3、位运算符的运算功能： a、按位取反： ~01001101 = 101
14点睛Spring4.1-脚本编程 wiselyman spring4
14.1 Scripting脚本编程脚本语言和java这类静态的语言的主要区别是:脚本语言无需编译,源码直接可运行; 如果我们经常需要修改的某些代码,每一次我们至少要进行编译,打包,重新部署的操作,步骤相当麻烦; 如果我们的应用不允许重启,这在现实的情况中也是很常见的; 在spring中使用脚本编程给上述的应用场景提供了解决方案,即动态加载bean; spring支持脚本