如何调整Worker线程等Machine.config 参数

最新推荐文章于 2020-07-23 08:33:06 发布
原创 最新推荐文章于 2020-07-23 08:33:06 发布 · 1.2k 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

博客提供了一个微软支持的链接，具体为http://support.microsoft.com/default.aspx?scid=kb;en-us;821268 ，可用于获取相关帮助。
一个RUNNABLE状态的线程hang在了java.io.FileOutputStream.writeBytes方法上
chiduopao3871的博客
05-24 1525
1. 问题背景 web项目要定时拉取其他系统的数据，用Quartz做了一个定时作业。在联调时，为了知道作业的运行情况，将logback的root logger从warn调到了debug， root logger有两个appender，一个是ConsoleAppender，一个是Rollin...
本地部署Qwen2大模型之四：模型参数调整
F8_11的博客
12-27 1743
继续深入调试vLLM方式部署Qwen2大模型，经过各种尝试，最后终于跑起来了，完成一问一答。
ASP.NET配置文件machine.config与性能
RainyLin-SunnyLin的专栏
07-29 1740
本文详细介绍了如何配置ASP.NET以获得最大的系统性能。原文请见http://www.xefteri.com/articles/show.cfm?id=14介绍 与传统的ASP不同的是，ASP.NET不是运行在IIS的地址空间，而是有自己的进程。该进程可以通过XML配置文件machine.config进行配置。 ASP.NET进程: aspnet_wp.exe传统的ASP程序
ASP.NET配置文件machine.config与性能[转]
diaguo7961的博客
04-09 140
转 http://www.cnblogs.com/chenlulouis/archive/2010/05/26/1744261.html http://www.cnblogs.com/zhangronghua/archive/2008/12/23/1360759.html ASP.NET配置文件machine.config与性能 与传统的ASP不同的是，ASP.NET不是运行在I...
IIS处理并发请求时出现的问题及解决
xxoo
09-01 3784
一个ASP.NET项目在部署到生产环境时，当用户并发量达到200左右时，IIS出现了明显的请求排队现象，发送的请求都进入等待，无法及时响应，系统基本处于不可用状态。因经验不足，花了很多时间精力解决这个问题，本文记录了我查找问题的过程和最后解决方案，供大家参考。   软硬件环境： IBM刀片服务器，Intel至强处理器，4物理核，16个逻辑核心，内存32G Windows Server200
asp.net 站点请求超时
diaoxiangsi1087的博客
09-25 361
　　最近由于受到攻击，而出现了请求超时，也不得不再次研究起了有关IIS的东东。 　　关于iis的相关东东，个人强烈推荐：http://www.iis.net/ 　　出现请求超时一下就让我们想到了是访问量大或者说是服务器顶不住垃圾程序了。一般情况我们自然是去看程序有什么问题了，所以也就开始研究超时这个东东了。（注：不要否认攻击的存在，暴雨般的流量只有天上会掉下来，否则就是人为的。天上掉...
如何在JavaScript中构建Electron桌面应用程序：多线程，SQLite，本机模块和其他常见痛点...
cumian8165的博客
07-23 2180
by Andrew Walsh 通过安德鲁·沃尔什(Andrew Walsh) 如何在JavaScript中构建Electron桌面应用程序：多线程，SQLite，本机模块和其他常见痛点 (How to Build an Electron Desktop App in JavaScript: Multithreading, SQLite, Native Modules, and other C...
2025-09-25 10:12:59.478 INFO 31516 — [ main] c.t.n.demo.basicspringboot.KafkaDemoApp : Starting KafkaDemoApp using Java 1.8.0_462-462 on 18088363-BG with PID 31516 (D:\r\idmdemo\target\classes started by admin in D:\r\idmdemo) 2025-09-25 10:12:59.480 INFO 31516 — [ main] c.t.n.demo.basicspringboot.KafkaDemoApp : No active profile set, falling back to 1 default profile: “default” 2025-09-25 10:13:00.103 INFO 31516 — [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8080 (http) 2025-09-25 10:13:00.110 INFO 31516 — [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat] 2025-09-25 10:13:00.110 INFO 31516 — [ main] org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.71] 2025-09-25 10:13:00.170 INFO 31516 — [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext 2025-09-25 10:13:00.170 INFO 31516 — [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 668 ms 2025-09-25 10:13:00.594 INFO 31516 — [ main] o.s.b.a.e.web.EndpointLinksResolver : Exposing 1 endpoint(s) beneath base path ‘/actuator’ 2025-09-25 10:13:00.625 INFO 31516 — [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8080 (http) with context path ‘’ 2025-09-25 10:13:00.633 INFO 31516 — [ main] c.t.n.demo.basicspringboot.KafkaDemoApp : Started KafkaDemoApp in 1.371 seconds (JVM running for 1.656) 2025-09-25 10:13:00.648 INFO 31516 — [ main] c.t.s.e.port.kafka.KafkaEventCenter : start to register topic: hello-topic, groupId: demo-group 2025-09-25 10:13:00.654 INFO 31516 — [ main] c.t.s.e.port.kafka.KafkaEventCenter : start to register topic: vms_dlq_hello-topic, groupId: dlq-demo-group 2025-09-25 10:13:00.665 INFO 31516 — [_dlq-demo-group] o.a.k.clients.consumer.ConsumerConfig : ConsumerConfig values: allow.auto.create.topics = true auto.commit.interval.ms = 5000 auto.offset.reset = latest bootstrap.servers = [192.168.203.128:9092] check.crcs = true client.dns.lookup = use_all_dns_ips client.id = consumer_10.13.35.30_c7bcb7ca-7123-40ce-99e3-8228f4657299 client.rack = connections.max.idle.ms = 540000 default.api.timeout.ms = 60000 enable.auto.commit = false exclude.internal.topics = true fetch.max.bytes = 52428800 fetch.max.wait.ms = 500 fetch.min.bytes = 1 group.id = dlq-demo-group group.instance.id = null heartbeat.interval.ms = 3000 interceptor.classes = [] internal.leave.group.on.close = true internal.throw.on.fetch.stable.offset.unsupported = false isolation.level = read_uncommitted key.deserializer = class org.apache.kafka.common.serialization.StringDeserializer max.partition.fetch.bytes = 1048576 max.poll.interval.ms = 300000 max.poll.records = 200 metadata.max.age.ms = 300000 metric.reporters = [] metrics.num.samples = 2 metrics.recording.level = INFO metrics.sample.window.ms = 30000 partition.assignment.strategy = [org.apache.kafka.clients.consumer.CooperativeStickyAssignor] receive.buffer.bytes = -1 reconnect.backoff.max.ms = 1000 reconnect.backoff.ms = 50 request.timeout.ms = 30000 retry.backoff.ms = 100 sasl.client.callback.handler.class = null sasl.jaas.config = null sasl.kerberos.kinit.cmd = /usr/bin/kinit sasl.kerberos.min.time.before.relogin = 60000 sasl.kerberos.service.name = null sasl.kerberos.ticket.renew.jitter = 0.05 sasl.kerberos.ticket.renew.window.factor = 0.8 sasl.login.callback.handler.class = null sasl.login.class = null sasl.login.refresh.buffer.seconds = 300 sasl.login.refresh.min.period.seconds = 60 sasl.login.refresh.window.factor = 0.8 sasl.login.refresh.window.jitter = 0.05 sasl.mechanism = GSSAPI security.protocol = PLAINTEXT security.providers = null send.buffer.bytes = 131072 session.timeout.ms = 45000 socket.connection.setup.timeout.max.ms = 30000 socket.connection.setup.timeout.ms = 10000 ssl.cipher.suites = null ssl.enabled.protocols = [TLSv1.2] ssl.endpoint.identification.algorithm = https ssl.engine.factory.class = null ssl.key.password = null ssl.keymanager.algorithm = SunX509 ssl.keystore.certificate.chain = null ssl.keystore.key = null ssl.keystore.location = null ssl.keystore.password = null ssl.keystore.type = JKS ssl.protocol = TLSv1.2 ssl.provider = null ssl.secure.random.implementation = null ssl.trustmanager.algorithm = PKIX ssl.truststore.certificates = null ssl.truststore.location = null ssl.truststore.password = null ssl.truststore.type = JKS value.deserializer = class org.apache.kafka.common.serialization.ByteArrayDeserializer 2025-09-25 10:13:00.665 INFO 31516 — [opic_demo-group] o.a.k.clients.consumer.ConsumerConfig : ConsumerConfig values: allow.auto.create.topics = true auto.commit.interval.ms = 5000 auto.offset.reset = latest bootstrap.servers = [192.168.203.128:9092] check.crcs = true client.dns.lookup = use_all_dns_ips client.id = consumer_10.13.35.30_84858b4f-b0ce-4324-90e8-3ceb81cfcf65 client.rack = connections.max.idle.ms = 540000 default.api.timeout.ms = 60000 enable.auto.commit = false exclude.internal.topics = true fetch.max.bytes = 52428800 fetch.max.wait.ms = 500 fetch.min.bytes = 1 group.id = demo-group group.instance.id = null heartbeat.interval.ms = 3000 interceptor.classes = [] internal.leave.group.on.close = true internal.throw.on.fetch.stable.offset.unsupported = false isolation.level = read_uncommitted key.deserializer = class org.apache.kafka.common.serialization.StringDeserializer max.partition.fetch.bytes = 1048576 max.poll.interval.ms = 300000 max.poll.records = 200 metadata.max.age.ms = 300000 metric.reporters = [] metrics.num.samples = 2 metrics.recording.level = INFO metrics.sample.window.ms = 30000 partition.assignment.strategy = [org.apache.kafka.clients.consumer.CooperativeStickyAssignor] receive.buffer.bytes = -1 reconnect.backoff.max.ms = 1000 reconnect.backoff.ms = 50 request.timeout.ms = 30000 retry.backoff.ms = 100 sasl.client.callback.handler.class = null sasl.jaas.config = null sasl.kerberos.kinit.cmd = /usr/bin/kinit sasl.kerberos.min.time.before.relogin = 60000 sasl.kerberos.service.name = null sasl.kerberos.ticket.renew.jitter = 0.05 sasl.kerberos.ticket.renew.window.factor = 0.8 sasl.login.callback.handler.class = null sasl.login.class = null sasl.login.refresh.buffer.seconds = 300 sasl.login.refresh.min.period.seconds = 60 sasl.login.refresh.window.factor = 0.8 sasl.login.refresh.window.jitter = 0.05 sasl.mechanism = GSSAPI security.protocol = PLAINTEXT security.providers = null send.buffer.bytes = 131072 session.timeout.ms = 45000 socket.connection.setup.timeout.max.ms = 30000 socket.connection.setup.timeout.ms = 10000 ssl.cipher.suites = null ssl.enabled.protocols = [TLSv1.2] ssl.endpoint.identification.algorithm = https ssl.engine.factory.class = null ssl.key.password = null ssl.keymanager.algorithm = SunX509 ssl.keystore.certificate.chain = null ssl.keystore.key = null ssl.keystore.location = null ssl.keystore.password = null ssl.keystore.type = JKS ssl.protocol = TLSv1.2 ssl.provider = null ssl.secure.random.implementation = null ssl.trustmanager.algorithm = PKIX ssl.truststore.certificates = null ssl.truststore.location = null ssl.truststore.password = null ssl.truststore.type = JKS value.deserializer = class org.apache.kafka.common.serialization.ByteArrayDeserializer 2025-09-25 10:13:00.678 INFO 31516 — [ main] o.a.k.clients.producer.ProducerConfig : ProducerConfig values: acks = -1 batch.size = 4096 bootstrap.servers = [192.168.203.128:9092] buffer.memory = 33554432 client.dns.lookup = use_all_dns_ips client.id = producer-1 compression.type = none connections.max.idle.ms = 540000 delivery.timeout.ms = 120000 enable.idempotence = false interceptor.classes = [] internal.auto.downgrade.txn.commit = false key.serializer = class org.apache.kafka.common.serialization.StringSerializer linger.ms = 1 max.block.ms = 60000 max.in.flight.requests.per.connection = 5 max.request.size = 1048576 metadata.max.age.ms = 300000 metadata.max.idle.ms = 300000 metric.reporters = [] metrics.num.samples = 2 metrics.recording.level = INFO metrics.sample.window.ms = 30000 partitioner.class = class org.apache.kafka.clients.producer.internals.DefaultPartitioner receive.buffer.bytes = 32768 reconnect.backoff.max.ms = 1000 reconnect.backoff.ms = 50 request.timeout.ms = 30000 retries = 2147483647 retry.backoff.ms = 100 sasl.client.callback.handler.class = null sasl.jaas.config = null sasl.kerberos.kinit.cmd = /usr/bin/kinit sasl.kerberos.min.time.before.relogin = 60000 sasl.kerberos.service.name = null sasl.kerberos.ticket.renew.jitter = 0.05 sasl.kerberos.ticket.renew.window.factor = 0.8 sasl.login.callback.handler.class = null sasl.login.class = null sasl.login.refresh.buffer.seconds = 300 sasl.login.refresh.min.period.seconds = 60 sasl.login.refresh.window.factor = 0.8 sasl.login.refresh.window.jitter = 0.05 sasl.mechanism = GSSAPI security.protocol = PLAINTEXT security.providers = null send.buffer.bytes = 131072 socket.connection.setup.timeout.max.ms = 30000 socket.connection.setup.timeout.ms = 10000 ssl.cipher.suites = null ssl.enabled.protocols = [TLSv1.2] ssl.endpoint.identification.algorithm = https ssl.engine.factory.class = null ssl.key.password = null ssl.keymanager.algorithm = SunX509 ssl.keystore.certificate.chain = null ssl.keystore.key = null ssl.keystore.location = null ssl.keystore.password = null ssl.keystore.type = JKS ssl.protocol = TLSv1.2 ssl.provider = null ssl.secure.random.implementation = null ssl.trustmanager.algorithm = PKIX ssl.truststore.certificates = null ssl.truststore.location = null ssl.truststore.password = null ssl.truststore.type = JKS transaction.timeout.ms = 60000 transactional.id = null value.serializer = class org.apache.kafka.common.serialization.ByteArraySerializer 2025-09-25 10:13:00.700 INFO 31516 — [ main] o.a.kafka.common.utils.AppInfoParser : Kafka version: 2.8.0 2025-09-25 10:13:00.700 INFO 31516 — [ main] o.a.kafka.common.utils.AppInfoParser : Kafka commitId: ebb1d6e21cc92130 2025-09-25 10:13:00.700 INFO 31516 — [ main] o.a.kafka.common.utils.AppInfoParser : Kafka startTimeMs: 1758766380699 2025-09-25 10:13:00.711 INFO 31516 — [opic_demo-group] o.a.kafka.common.utils.AppInfoParser : Kafka version: 2.8.0 2025-09-25 10:13:00.711 INFO 31516 — [opic_demo-group] o.a.kafka.common.utils.AppInfoParser : Kafka commitId: ebb1d6e21cc92130 2025-09-25 10:13:00.711 INFO 31516 — [opic_demo-group] o.a.kafka.common.utils.AppInfoParser : Kafka startTimeMs: 1758766380711 2025-09-25 10:13:00.711 INFO 31516 — [opic_demo-group] c.t.s.e.p.k.consumer.KafkaConsumerTask : start to consumer kafka topic: hello-topic 2025-09-25 10:13:00.711 INFO 31516 — [opic_demo-group] c.t.s.e.p.k.c.AbstractTaskService : KafkaConsumerTask is running! topic:hello-topic 2025-09-25 10:13:00.711 INFO 31516 — [_dlq-demo-group] o.a.kafka.common.utils.AppInfoParser : Kafka version: 2.8.0 2025-09-25 10:13:00.711 INFO 31516 — [_dlq-demo-group] o.a.kafka.common.utils.AppInfoParser : Kafka commitId: ebb1d6e21cc92130 2025-09-25 10:13:00.711 INFO 31516 — [_dlq-demo-group] o.a.kafka.common.utils.AppInfoParser : Kafka startTimeMs: 1758766380711 2025-09-25 10:13:00.711 INFO 31516 — [_dlq-demo-group] c.t.s.e.p.k.consumer.KafkaConsumerTask : start to consumer kafka topic: vms_dlq_hello-topic 2025-09-25 10:13:00.711 INFO 31516 — [_dlq-demo-group] c.t.s.e.p.k.c.AbstractTaskService : KafkaConsumerTask is running! topic:vms_dlq_hello-topic 2025-09-25 10:13:00.711 INFO 31516 — [_dlq-demo-group] o.a.k.clients.consumer.KafkaConsumer : [Consumer clientId=consumer_10.13.35.30_c7bcb7ca-7123-40ce-99e3-8228f4657299, groupId=dlq-demo-group] Subscribed to topic(s): vms_dlq_hello-topic 2025-09-25 10:13:00.711 INFO 31516 — [opic_demo-group] o.a.k.clients.consumer.KafkaConsumer : [Consumer clientId=consumer_10.13.35.30_84858b4f-b0ce-4324-90e8-3ceb81cfcf65, groupId=demo-group] Subscribed to topic(s): hello-topic 2025-09-25 10:13:00.863 INFO 31516 — [ad | producer-1] org.apache.kafka.clients.Metadata : [Producer clientId=producer-1] Cluster ID: ZzP7spDrRwuJk27muhJ29g 2025-09-25 10:13:00.863 INFO 31516 — [opic_demo-group] org.apache.kafka.clients.Metadata : [Consumer clientId=consumer_10.13.35.30_84858b4f-b0ce-4324-90e8-3ceb81cfcf65, groupId=demo-group] Cluster ID: ZzP7spDrRwuJk27muhJ29g 2025-09-25 10:13:00.863 INFO 31516 — [_dlq-demo-group] org.apache.kafka.clients.Metadata : [Consumer clientId=consumer_10.13.35.30_c7bcb7ca-7123-40ce-99e3-8228f4657299, groupId=dlq-demo-group] Cluster ID: ZzP7spDrRwuJk27muhJ29g 2025-09-25 10:13:00.863 INFO 31516 — [_dlq-demo-group] o.a.k.c.c.internals.AbstractCoordinator : [Consumer clientId=consumer_10.13.35.30_c7bcb7ca-7123-40ce-99e3-8228f4657299, groupId=dlq-demo-group] Discovered group coordinator admin1-virtual-machine:9092 (id: 2147483647 rack: null) 2025-09-25 10:13:00.863 INFO 31516 — [opic_demo-group] o.a.k.c.c.internals.AbstractCoordinator : [Consumer clientId=consumer_10.13.35.30_84858b4f-b0ce-4324-90e8-3ceb81cfcf65, groupId=demo-group] Discovered group coordinator admin1-virtual-machine:9092 (id: 2147483647 rack: null) 2025-09-25 10:13:01.300 INFO 31516 — [_dlq-demo-group] o.a.k.c.c.internals.AbstractCoordinator : [Consumer clientId=consumer_10.13.35.30_c7bcb7ca-7123-40ce-99e3-8228f4657299, groupId=dlq-demo-group] (Re-)joining group 2025-09-25 10:13:01.300 INFO 31516 — [opic_demo-group] o.a.k.c.c.internals.AbstractCoordinator : [Consumer clientId=consumer_10.13.35.30_84858b4f-b0ce-4324-90e8-3ceb81cfcf65, groupId=demo-group] (Re-)joining group 2025-09-25 10:13:01.320 INFO 31516 — [opic_demo-group] o.a.k.c.c.internals.AbstractCoordinator : [Consumer clientId=consumer_10.13.35.30_84858b4f-b0ce-4324-90e8-3ceb81cfcf65, groupId=demo-group] (Re-)joining group 2025-09-25 10:13:01.320 INFO 31516 — [_dlq-demo-group] o.a.k.c.c.internals.AbstractCoordinator : [Consumer clientId=consumer_10.13.35.30_c7bcb7ca-7123-40ce-99e3-8228f4657299, groupId=dlq-demo-group] (Re-)joining group 2025-09-25 10:13:01.323 INFO 31516 — [_dlq-demo-group] o.a.k.c.c.internals.AbstractCoordinator : [Consumer clientId=consumer_10.13.35.30_c7bcb7ca-7123-40ce-99e3-8228f4657299, groupId=dlq-demo-group] Successfully joined group with generation Generation{generationId=30, memberId=‘consumer_10.13.35.30_c7bcb7ca-7123-40ce-99e3-8228f4657299-67bf5860-c183-4894-acbb-8837abf647f6’, protocol=‘cooperative-sticky’} 2025-09-25 10:13:01.323 INFO 31516 — [opic_demo-group] o.a.k.c.c.internals.AbstractCoordinator : [Consumer clientId=consumer_10.13.35.30_84858b4f-b0ce-4324-90e8-3ceb81cfcf65, groupId=demo-group] Successfully joined group with generation Generation{generationId=31, memberId=‘consumer_10.13.35.30_84858b4f-b0ce-4324-90e8-3ceb81cfcf65-c3379cf9-80c6-40cc-a872-71b04e2f7b27’, protocol=‘cooperative-sticky’} 2025-09-25 10:13:01.324 INFO 31516 — [_dlq-demo-group] o.a.k.c.c.internals.ConsumerCoordinator : [Consumer clientId=consumer_10.13.35.30_c7bcb7ca-7123-40ce-99e3-8228f4657299, groupId=dlq-demo-group] Finished assignment for group at generation 30: {consumer_10.13.35.30_c7bcb7ca-7123-40ce-99e3-8228f4657299-67bf5860-c183-4894-acbb-8837abf647f6=Assignment(partitions=[vms_dlq_hello-topic-0])} 2025-09-25 10:13:01.324 INFO 31516 — [opic_demo-group] o.a.k.c.c.internals.ConsumerCoordinator : [Consumer clientId=consumer_10.13.35.30_84858b4f-b0ce-4324-90e8-3ceb81cfcf65, groupId=demo-group] Finished assignment for group at generation 31: {consumer_10.13.35.30_84858b4f-b0ce-4324-90e8-3ceb81cfcf65-c3379cf9-80c6-40cc-a872-71b04e2f7b27=Assignment(partitions=[hello-topic-0])} 2025-09-25 10:13:01.327 INFO 31516 — [opic_demo-group] o.a.k.c.c.internals.AbstractCoordinator : [Consumer clientId=consumer_10.13.35.30_84858b4f-b0ce-4324-90e8-3ceb81cfcf65, groupId=demo-group] Successfully synced group in generation Generation{generationId=31, memberId=‘consumer_10.13.35.30_84858b4f-b0ce-4324-90e8-3ceb81cfcf65-c3379cf9-80c6-40cc-a872-71b04e2f7b27’, protocol=‘cooperative-sticky’} 2025-09-25 10:13:01.327 INFO 31516 — [opic_demo-group] o.a.k.c.c.internals.ConsumerCoordinator : [Consumer clientId=consumer_10.13.35.30_84858b4f-b0ce-4324-90e8-3ceb81cfcf65, groupId=demo-group] Updating assignment with Assigned partitions: [hello-topic-0] Current owned partitions: [] Added partitions (assigned - owned): [hello-topic-0] Revoked partitions (owned - assigned): [] 2025-09-25 10:13:01.327 INFO 31516 — [opic_demo-group] o.a.k.c.c.internals.ConsumerCoordinator : [Consumer clientId=consumer_10.13.35.30_84858b4f-b0ce-4324-90e8-3ceb81cfcf65, groupId=demo-group] Notifying assignor about the new Assignment(partitions=[hello-topic-0]) 2025-09-25 10:13:01.328 INFO 31516 — [_dlq-demo-group] o.a.k.c.c.internals.AbstractCoordinator : [Consumer clientId=consumer_10.13.35.30_c7bcb7ca-7123-40ce-99e3-8228f4657299, groupId=dlq-demo-group] Successfully synced group in generation Generation{generationId=30, memberId=‘consumer_10.13.35.30_c7bcb7ca-7123-40ce-99e3-8228f4657299-67bf5860-c183-4894-acbb-8837abf647f6’, protocol=‘cooperative-sticky’} 2025-09-25 10:13:01.328 INFO 31516 — [_dlq-demo-group] o.a.k.c.c.internals.ConsumerCoordinator : [Consumer clientId=consumer_10.13.35.30_c7bcb7ca-7123-40ce-99e3-8228f4657299, groupId=dlq-demo-group] Updating assignment with Assigned partitions: [vms_dlq_hello-topic-0] Current owned partitions: [] Added partitions (assigned - owned): [vms_dlq_hello-topic-0] Revoked partitions (owned - assigned): [] 2025-09-25 10:13:01.328 INFO 31516 — [_dlq-demo-group] o.a.k.c.c.internals.ConsumerCoordinator : [Consumer clientId=consumer_10.13.35.30_c7bcb7ca-7123-40ce-99e3-8228f4657299, groupId=dlq-demo-group] Notifying assignor about the new Assignment(partitions=[vms_dlq_hello-topic-0]) 2025-09-25 10:13:01.328 INFO 31516 — [opic_demo-group] o.a.k.c.c.internals.ConsumerCoordinator : [Consumer clientId=consumer_10.13.35.30_84858b4f-b0ce-4324-90e8-3ceb81cfcf65, groupId=demo-group] Adding newly assigned partitions: hello-topic-0 2025-09-25 10:13:01.328 INFO 31516 — [_dlq-demo-group] o.a.k.c.c.internals.ConsumerCoordinator : [Consumer clientId=consumer_10.13.35.30_c7bcb7ca-7123-40ce-99e3-8228f4657299, groupId=dlq-demo-group] Adding newly assigned partitions: vms_dlq_hello-topic-0 2025-09-25 10:13:01.328 INFO 31516 — [opic_demo-group] com.tplink.smb.eventcenter.api.Handler : ending rebalance! 2025-09-25 10:13:01.328 INFO 31516 — [_dlq-demo-group] com.tplink.smb.eventcenter.api.Handler : ending rebalance! 2025-09-25 10:13:01.333 INFO 31516 — [opic_demo-group] o.a.k.c.c.internals.ConsumerCoordinator : [Consumer clientId=consumer_10.13.35.30_84858b4f-b0ce-4324-90e8-3ceb81cfcf65, groupId=demo-group] Setting offset for partition hello-topic-0 to the committed offset FetchPosition{offset=17, offsetEpoch=Optional.empty, currentLeader=LeaderAndEpoch{leader=Optional[admin1-virtual-machine:9092 (id: 0 rack: null)], epoch=absent}} 2025-09-25 10:13:01.333 INFO 31516 — [_dlq-demo-group] o.a.k.c.c.internals.ConsumerCoordinator : [Consumer clientId=consumer_10.13.35.30_c7bcb7ca-7123-40ce-99e3-8228f4657299, groupId=dlq-demo-group] Setting offset for partition vms_dlq_hello-topic-0 to the committed offset FetchPosition{offset=0, offsetEpoch=Optional.empty, currentLeader=LeaderAndEpoch{leader=Optional[admin1-virtual-machine:9092 (id: 0 rack: null)], epoch=absent}} 尝试处理消息: Hello Kafka! 这是一条会触发死信的消息 2025-09-25 10:13:01.371 WARN 31516 — [nPool-worker-22] c.t.s.e.p.k.d.DLQEventHandlerWrapper : Event handle failed (attempt 1/2): 模拟业务处理失败 2025-09-25 10:13:01.371 INFO 31516 — [nPool-worker-22] c.t.s.e.p.k.d.DLQEventHandlerWrapper : Scheduled retry delay: delay=1000ms 尝试处理消息: Hello Kafka! 这是一条会触发死信的消息 2025-09-25 10:13:02.379 WARN 31516 — [nPool-worker-22] c.t.s.e.p.k.d.DLQEventHandlerWrapper : Event handle failed (attempt 2/2): 模拟业务处理失败 2025-09-25 10:13:02.381 INFO 31516 — [nPool-worker-22] c.t.s.e.port.kafka.KafkaEventCenter : not implement yet 2025-09-25 10:13:02.382 INFO 31516 — [nPool-worker-22] c.t.s.e.p.k.d.DLQEventHandlerWrapper : Eventsent to DLQ topic: vms_dlq_hello-topic 2025-09-25 10:13:02.382 ERROR 31516 — [nPool-worker-22] c.t.s.e.p.k.d.DLQEventHandlerWrapper : Event failed after 2 retries (sent to DLQ)请根据这段日志分析，死信队列如果想获取offset和目标topic应该在哪里侵入
最新发布
09-26
从日志中可以看到，处理消息的线程是ForkJoinPool线程（[nPool-worker-22]）。而在我们的代码中，`executeWithContext`方法使用了`CompletableFuture.runAsync`，这会导致任务在另一个线程中执行，而ThreadLocal变量...
修改machine.Config 提高iis性能
diaoxiangsi1087的博客
09-25 929
Tuning IIS - machine.config settings Recently I needed to try and reduce contention within IIS when calling a number of web services. Eventually this led to the need to make some changes to t...
修改网站的最小工作线程WorkerThreads
sxf359的博客
06-17 2217
如果在machine.config中修改此项值，则对所有服务器的网站都起作用。因此需要在网站的global.asax的Application_Start 方法中进行设置: int minWorker, minIOC; // Get the current settings. ThreadPool.GetMinThreads(out minWorke
配置线程池时线程数设置多少好
数据库
04-14 964
一般总结哦，有其他更好的方式，希望各位留言，谢谢。 CPU密集型时，任务可以少配置线程数，大概和机器的cpu核数相当，这样可以使得每个线程都在执行任务 IO密集型时，大部分线程都阻塞，故需要多配置线程数，2*cpu核数 操作系统之名称解释： 某些进程花费了绝大多数时间在计算上，而其他则在等待I/O上花费了大多是时间， 前者称为计算密集型（CPU密集型）computer-bound，后...
关于machine.config的那些事儿
RollingFeel的专栏
05-14 1282
Recently I needed to try and reduce contention within IIS when calling a number of web services.  Eventually this led to the need to make some changes to the machine.config file. The changes identifi
记5.28大促压测的性能优化—线程池相关问题
dengzai7446的博客
06-04 242
目录： 1.环境介绍 2.症状 3.诊断 4.结论 5.解决 6.对比java实现 废话就不多说了，本文分享下博主在5.28大促压测期间解决的一个性能问题，觉得这个还是比较有意思的，值得总结拿出来分享下。 博主所服务的部门是作为公共业务平台，公共业务平台支持上层所有业务系统（2C、UGC、直播等）。平台中核心之一的就是订单域相关服务，下单服务、查单服务、支付回调服务，当然...
IIS 之 在IIS7、IIS7.5中应用程序池最优配置方案
weixin_34113237的博客
10-10 1698
　　找到Web站点对应的应用程序池，“应用程序池” → 找到对应的“应用程序池” → 右键“高级设置...” 　　 一、一般优化方案 .imageplus-append-lu-img-txt { overflow: hidden; margin: 10px 0; font-family: Microsoft YaHei; line-height: normal } .imageplus-appen...
asp.net 配置文件（Machine.config、Web.config、App.config）
ydm东方旭日的专栏
03-28 4727
Machine.config 1.该文件在Windows目录下\Microsoft.net\framework\[version]\Config\ 2.为了提高性能，该文件只包含不同于默认值的设置。并且定义了配置文件项可包含的配置节，就像是一个基础的定义。可以使用System.Configuration命名空间中的类读取配置文件 3.Configuration元素的主要子元素 appSet
争用、 较差的性能和死锁时使 ASP.NET 应用程序的 Web 服务请求
冰的城
07-17 2648
文章编号: 821268 - 查看本文应用于的产品 症状 当您从 ASP.NET 应用程序调用 XML Web 服务时，您可能会遇到争用、 较差的性能和死锁。客户端可能会报告请求停止响应 （或"挂起"），或需要很长时间才能执行。如果怀疑死锁，则可能是回收工作进程。在应用程序事件日志中可能会收到以下消息。 如果您使用的 Microsoft Internet Informat
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

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

余额充值