主頁 > 資料庫 > 使用Docker運行Kafka,似乎沒有正確使用SSL選項

使用Docker運行Kafka,似乎沒有正確使用SSL選項

2022-06-15 06:06:23 資料庫

我有以下 docker-compose.yml 檔案,以便運行 Zookeeper 的單個實體和一個代理。我以為我在 SSL 握手方面遇到了各種各樣的問題,但是當我深入挖掘時,它似乎只關注我正在通過的一小部分配置選項。

version: '3.5'
networks:
  secNet:
    name: secNet

services:
  sec-zookeeper:
    image: confluentinc/cp-zookeeper:5.5.0
    container_name: sec-zookeeper
    networks:
      - secNet
    environment:
      ZOOKEEPER_CLIENT_PORT: 2181

  sec-broker-one:
    image: confluentinc/cp-kafka:5.5.0
    container_name: sec-broker-one
    networks:
      - secNet
    restart: always
    ports:
      - "19092:19092"
    depends_on:
      - sec-zookeeper
    volumes:
      - ./ssl/:/etc/kafka/secrets
    environment:
      KAFKA_BROKER_ID: 1
      KAFKA_ZOOKEEPER_CONNECT: sec-zookeeper:2181
      KAFKA_ADVERTISED_LISTENERS: PLAINTEXT://sec-broker-one:9092,SSL://sec-broker-one:9192
      KAFKA_OFFSETS_TOPIC_REPLICATION_FACTOR: 1
      KAFKA_ADVERTISED_LISTENERS: PLAINTEXT://sec-broker-one:9092,CONNECTIONS_FROM_HOST://localhost:19092
      KAFKA_LISTENER_SECURITY_PROTOCOL_MAP: PLAINTEXT:PLAINTEXT,CONNECTIONS_FROM_HOST:SSL
      KAFKA_LOG_MESSAGE_TIMESTAMP_TYPE: CreateTime
      KAFKA_LOG_RETENTION_HOURS: 2232
      KAFKA_SSL_KEYSTORE_FILENAME: kafka.server.keystore.jks
      KAFKA_SSL_KEYSTORE_CREDENTIALS: server.password
      KAFKA_SSL_KEY_CREDENTIALS: server.password
      KAFKA_SSL_TRUSTSTORE_FILENAME: kafka.server.truststore.jks
      KAFKA_SSL_TRUSTSTORE_CREDENTIALS: server.password
      KAFKA_SSL_ENDPOINT_IDENTIFICATION_ALGORITHM: ""
      KAFKA_OPTS: -Djavax.net.debug=all      
      KAFKA_SSL_CLIENT_AUTH: required

如果我們看一下docker-compose up輸出的結果:

sec-broker-one    | ===> Launching kafka ... 
sec-broker-one    | [2022-06-10 05:14:22,327] INFO Registered kafka:type=kafka.Log4jController MBean (kafka.utils.Log4jControllerRegistration$)
sec-broker-one    | [2022-06-10 05:14:22,738] INFO KafkaConfig values: 
sec-broker-one    |     advertised.host.name = null
sec-broker-one    |     advertised.listeners = PLAINTEXT://sec-broker-one:9092,CONNECTIONS_FROM_HOST://localhost:19092
sec-broker-one    |     advertised.port = null
sec-broker-one    |     alter.config.policy.class.name = null
sec-broker-one    |     alter.log.dirs.replication.quota.window.num = 11
sec-broker-one    |     alter.log.dirs.replication.quota.window.size.seconds = 1
sec-broker-one    |     authorizer.class.name = 
sec-broker-one    |     auto.create.topics.enable = true
sec-broker-one    |     auto.leader.rebalance.enable = true
sec-broker-one    |     background.threads = 10
sec-broker-one    |     broker.id = 1
sec-broker-one    |     broker.id.generation.enable = true
sec-broker-one    |     broker.rack = null
sec-broker-one    |     client.quota.callback.class = null
sec-broker-one    |     compression.type = producer
sec-broker-one    |     connection.failed.authentication.delay.ms = 100
sec-broker-one    |     connections.max.idle.ms = 600000
sec-broker-one    |     connections.max.reauth.ms = 0
sec-broker-one    |     control.plane.listener.name = null
sec-broker-one    |     controlled.shutdown.enable = true
sec-broker-one    |     controlled.shutdown.max.retries = 3
sec-broker-one    |     controlled.shutdown.retry.backoff.ms = 5000
sec-broker-one    |     controller.socket.timeout.ms = 30000
sec-broker-one    |     create.topic.policy.class.name = null
sec-broker-one    |     default.replication.factor = 1
sec-broker-one    |     delegation.token.expiry.check.interval.ms = 3600000
sec-broker-one    |     delegation.token.expiry.time.ms = 86400000
sec-broker-one    |     delegation.token.master.key = null
sec-broker-one    |     delegation.token.max.lifetime.ms = 604800000
sec-broker-one    |     delete.records.purgatory.purge.interval.requests = 1
sec-broker-one    |     delete.topic.enable = true
sec-broker-one    |     fetch.max.bytes = 57671680
sec-broker-one    |     fetch.purgatory.purge.interval.requests = 1000
sec-broker-one    |     group.initial.rebalance.delay.ms = 3000
sec-broker-one    |     group.max.session.timeout.ms = 1800000
sec-broker-one    |     group.max.size = 2147483647
sec-broker-one    |     group.min.session.timeout.ms = 6000
sec-broker-one    |     host.name = 
sec-broker-one    |     inter.broker.listener.name = null
sec-broker-one    |     inter.broker.protocol.version = 2.5-IV0
sec-broker-one    |     kafka.metrics.polling.interval.secs = 10
sec-broker-one    |     kafka.metrics.reporters = []
sec-broker-one    |     leader.imbalance.check.interval.seconds = 300
sec-broker-one    |     leader.imbalance.per.broker.percentage = 10
sec-broker-one    |     listener.security.protocol.map = PLAINTEXT:PLAINTEXT,CONNECTIONS_FROM_HOST:SSL
sec-broker-one    |     listeners = PLAINTEXT://0.0.0.0:9092,CONNECTIONS_FROM_HOST://0.0.0.0:19092
sec-broker-one    |     log.cleaner.backoff.ms = 15000
sec-broker-one    |     log.cleaner.dedupe.buffer.size = 134217728
sec-broker-one    |     log.cleaner.delete.retention.ms = 86400000
sec-broker-one    |     log.cleaner.enable = true
sec-broker-one    |     log.cleaner.io.buffer.load.factor = 0.9
sec-broker-one    |     log.cleaner.io.buffer.size = 524288
sec-broker-one    |     log.cleaner.io.max.bytes.per.second = 1.7976931348623157E308
sec-broker-one    |     log.cleaner.max.compaction.lag.ms = 9223372036854775807
sec-broker-one    |     log.cleaner.min.cleanable.ratio = 0.5
sec-broker-one    |     log.cleaner.min.compaction.lag.ms = 0
sec-broker-one    |     log.cleaner.threads = 1
sec-broker-one    |     log.cleanup.policy = [delete]
sec-broker-one    |     log.dir = /tmp/kafka-logs
sec-broker-one    |     log.dirs = /var/lib/kafka/data
sec-broker-one    |     log.flush.interval.messages = 9223372036854775807
sec-broker-one    |     log.flush.interval.ms = null
sec-broker-one    |     log.flush.offset.checkpoint.interval.ms = 60000
sec-broker-one    |     log.flush.scheduler.interval.ms = 9223372036854775807
sec-broker-one    |     log.flush.start.offset.checkpoint.interval.ms = 60000
sec-broker-one    |     log.index.interval.bytes = 4096
sec-broker-one    |     log.index.size.max.bytes = 10485760
sec-broker-one    |     log.message.downconversion.enable = true
sec-broker-one    |     log.message.format.version = 2.5-IV0
sec-broker-one    |     log.message.timestamp.difference.max.ms = 9223372036854775807
sec-broker-one    |     log.message.timestamp.type = CreateTime
sec-broker-one    |     log.preallocate = false
sec-broker-one    |     log.retention.bytes = -1
sec-broker-one    |     log.retention.check.interval.ms = 300000
sec-broker-one    |     log.retention.hours = 2232
sec-broker-one    |     log.retention.minutes = null
sec-broker-one    |     log.retention.ms = null
sec-broker-one    |     log.roll.hours = 168
sec-broker-one    |     log.roll.jitter.hours = 0
sec-broker-one    |     log.roll.jitter.ms = null
sec-broker-one    |     log.roll.ms = null
sec-broker-one    |     log.segment.bytes = 1073741824
sec-broker-one    |     log.segment.delete.delay.ms = 60000
sec-broker-one    |     max.connections = 2147483647
sec-broker-one    |     max.connections.per.ip = 2147483647
sec-broker-one    |     max.connections.per.ip.overrides = 
sec-broker-one    |     max.incremental.fetch.session.cache.slots = 1000
sec-broker-one    |     message.max.bytes = 1048588
sec-broker-one    |     metric.reporters = []
sec-broker-one    |     metrics.num.samples = 2
sec-broker-one    |     metrics.recording.level = INFO
sec-broker-one    |     metrics.sample.window.ms = 30000
sec-broker-one    |     min.insync.replicas = 1
sec-broker-one    |     num.io.threads = 8
sec-broker-one    |     num.network.threads = 3
sec-broker-one    |     num.partitions = 1
sec-broker-one    |     num.recovery.threads.per.data.dir = 1
sec-broker-one    |     num.replica.alter.log.dirs.threads = null
sec-broker-one    |     num.replica.fetchers = 1
sec-broker-one    |     offset.metadata.max.bytes = 4096
sec-broker-one    |     offsets.commit.required.acks = -1
sec-broker-one    |     offsets.commit.timeout.ms = 5000
sec-broker-one    |     offsets.load.buffer.size = 5242880
sec-broker-one    |     offsets.retention.check.interval.ms = 600000
sec-broker-one    |     offsets.retention.minutes = 10080
sec-broker-one    |     offsets.topic.compression.codec = 0
sec-broker-one    |     offsets.topic.num.partitions = 50
sec-broker-one    |     offsets.topic.replication.factor = 1
sec-broker-one    |     offsets.topic.segment.bytes = 104857600
sec-broker-one    |     password.encoder.cipher.algorithm = AES/CBC/PKCS5Padding
sec-broker-one    |     password.encoder.iterations = 4096
sec-broker-one    |     password.encoder.key.length = 128
sec-broker-one    |     password.encoder.keyfactory.algorithm = null
sec-broker-one    |     password.encoder.old.secret = null
sec-broker-one    |     password.encoder.secret = null
sec-broker-one    |     port = 9092
sec-broker-one    |     principal.builder.class = null
sec-broker-one    |     producer.purgatory.purge.interval.requests = 1000
sec-broker-one    |     queued.max.request.bytes = -1
sec-broker-one    |     queued.max.requests = 500
sec-broker-one    |     quota.consumer.default = 9223372036854775807
sec-broker-one    |     quota.producer.default = 9223372036854775807
sec-broker-one    |     quota.window.num = 11
sec-broker-one    |     quota.window.size.seconds = 1
sec-broker-one    |     replica.fetch.backoff.ms = 1000
sec-broker-one    |     replica.fetch.max.bytes = 1048576
sec-broker-one    |     replica.fetch.min.bytes = 1
sec-broker-one    |     replica.fetch.response.max.bytes = 10485760
sec-broker-one    |     replica.fetch.wait.max.ms = 500
sec-broker-one    |     replica.high.watermark.checkpoint.interval.ms = 5000
sec-broker-one    |     replica.lag.time.max.ms = 30000
sec-broker-one    |     replica.selector.class = null
sec-broker-one    |     replica.socket.receive.buffer.bytes = 65536
sec-broker-one    |     replica.socket.timeout.ms = 30000
sec-broker-one    |     replication.quota.window.num = 11
sec-broker-one    |     replication.quota.window.size.seconds = 1
sec-broker-one    |     request.timeout.ms = 30000
sec-broker-one    |     reserved.broker.max.id = 1000
sec-broker-one    |     sasl.client.callback.handler.class = null
sec-broker-one    |     sasl.enabled.mechanisms = [GSSAPI]
sec-broker-one    |     sasl.jaas.config = null
sec-broker-one    |     sasl.kerberos.kinit.cmd = /usr/bin/kinit
sec-broker-one    |     sasl.kerberos.min.time.before.relogin = 60000
sec-broker-one    |     sasl.kerberos.principal.to.local.rules = [DEFAULT]
sec-broker-one    |     sasl.kerberos.service.name = null
sec-broker-one    |     sasl.kerberos.ticket.renew.jitter = 0.05
sec-broker-one    |     sasl.kerberos.ticket.renew.window.factor = 0.8
sec-broker-one    |     sasl.login.callback.handler.class = null
sec-broker-one    |     sasl.login.class = null
sec-broker-one    |     sasl.login.refresh.buffer.seconds = 300
sec-broker-one    |     sasl.login.refresh.min.period.seconds = 60
sec-broker-one    |     sasl.login.refresh.window.factor = 0.8
sec-broker-one    |     sasl.login.refresh.window.jitter = 0.05
sec-broker-one    |     sasl.mechanism.inter.broker.protocol = GSSAPI
sec-broker-one    |     sasl.server.callback.handler.class = null
sec-broker-one    |     security.inter.broker.protocol = PLAINTEXT
sec-broker-one    |     security.providers = null
sec-broker-one    |     socket.receive.buffer.bytes = 102400
sec-broker-one    |     socket.request.max.bytes = 104857600
sec-broker-one    |     socket.send.buffer.bytes = 102400
sec-broker-one    |     ssl.cipher.suites = []
sec-broker-one    |     ssl.client.auth = required
sec-broker-one    |     ssl.enabled.protocols = [TLSv1.2, TLSv1.1, TLSv1]
sec-broker-one    |     ssl.endpoint.identification.algorithm = 
sec-broker-one    |     ssl.key.password = null
sec-broker-one    |     ssl.keymanager.algorithm = SunX509
sec-broker-one    |     ssl.keystore.location = null
sec-broker-one    |     ssl.keystore.password = null
sec-broker-one    |     ssl.keystore.type = JKS
sec-broker-one    |     ssl.principal.mapping.rules = DEFAULT
sec-broker-one    |     ssl.protocol = TLS
sec-broker-one    |     ssl.provider = null
sec-broker-one    |     ssl.secure.random.implementation = null
sec-broker-one    |     ssl.trustmanager.algorithm = PKIX
sec-broker-one    |     ssl.truststore.location = null
sec-broker-one    |     ssl.truststore.password = null
sec-broker-one    |     ssl.truststore.type = JKS
sec-broker-one    |     transaction.abort.timed.out.transaction.cleanup.interval.ms = 10000
sec-broker-one    |     transaction.max.timeout.ms = 900000
sec-broker-one    |     transaction.remove.expired.transaction.cleanup.interval.ms = 3600000
sec-broker-one    |     transaction.state.log.load.buffer.size = 5242880
sec-broker-one    |     transaction.state.log.min.isr = 2
sec-broker-one    |     transaction.state.log.num.partitions = 50
sec-broker-one    |     transaction.state.log.replication.factor = 3
sec-broker-one    |     transaction.state.log.segment.bytes = 104857600
sec-broker-one    |     transactional.id.expiration.ms = 604800000
sec-broker-one    |     unclean.leader.election.enable = false
sec-broker-one    |     zookeeper.clientCnxnSocket = null
sec-broker-one    |     zookeeper.connect = sec-zookeeper:2181
sec-broker-one    |     zookeeper.connection.timeout.ms = null
sec-broker-one    |     zookeeper.max.in.flight.requests = 10
sec-broker-one    |     zookeeper.session.timeout.ms = 18000
sec-broker-one    |     zookeeper.set.acl = false
sec-broker-one    |     zookeeper.ssl.cipher.suites = null
sec-broker-one    |     zookeeper.ssl.client.enable = false
sec-broker-one    |     zookeeper.ssl.crl.enable = false
sec-broker-one    |     zookeeper.ssl.enabled.protocols = null
sec-broker-one    |     zookeeper.ssl.endpoint.identification.algorithm = HTTPS
sec-broker-one    |     zookeeper.ssl.keystore.location = null
sec-broker-one    |     zookeeper.ssl.keystore.password = null
sec-broker-one    |     zookeeper.ssl.keystore.type = null
sec-broker-one    |     zookeeper.ssl.ocsp.enable = false
sec-broker-one    |     zookeeper.ssl.protocol = TLSv1.2
sec-broker-one    |     zookeeper.ssl.truststore.location = null
sec-broker-one    |     zookeeper.ssl.truststore.password = null
sec-broker-one    |     zookeeper.ssl.truststore.type = null
sec-broker-one    |     zookeeper.sync.time.ms = 2000

它忽略了幾乎所有的設定,即 KAFKA_SSL_KEYSTORE 和 KAFKA_SSL_TRUSTSTORE 變數。我在容器中閑逛了一下,配置值在 kafka.properties 中,因此它們被復制進來,但是在運行代理時它似乎被底層影像忽略了。我從代理影像內部提供了屬性檔案的視圖:

# cat /etc/kafka/kafka.properties
broker.id=1
ssl.key.credentials=server.password
advertised.listeners=PLAINTEXT://sec-broker-one:9092,CONNECTIONS_FROM_HOST://localhost:19092
offsets.topic.replication.factor=1
ssl.endpoint.identification.algorithm=
ssl.keystore.filename=kafka.server.keystore.jks
zookeeper.connect=sec-zookeeper:2181
listener.security.protocol.map=PLAINTEXT:PLAINTEXT,CONNECTIONS_FROM_HOST:SSL
log.dirs=/var/lib/kafka/data
ssl.truststore.filename=kafka.server.truststore.jks
listeners=PLAINTEXT://0.0.0.0:9092,CONNECTIONS_FROM_HOST://0.0.0.0:19092
ssl.truststore.credentials=server.password
ssl.client.auth=required
log.message.timestamp.type=CreateTime
ssl.keystore.credentials=server.password
log.retention.hours=2232

從 listener.security.protocol.map 正確設定為 PLAINTEXT:PLAINTEXT,CONNECTIONS_FROM_HOST:SSL 可以看出,一些屬性很好

但不是全部。

uj5u.com熱心網友回復:

查看日志,您會看到變數以 結尾.location,這需要容器中的絕對路徑

ssl.*.filename不是有效的經紀人屬性,也不是ssl.*.credentials

轉載請註明出處,本文鏈接:https://www.uj5u.com/shujuku/490862.html

標籤:码头工人 ssl 阿帕奇卡夫卡

上一篇:TLSGolang上的Http未接收標頭

下一篇:MQTT埠8883和1883同時啟用不作業

標籤雲
其他(157675) Python(38076) JavaScript(25376) Java(17977) C(15215) 區塊鏈(8255) C#(7972) AI(7469) 爪哇(7425) MySQL(7132) html(6777) 基礎類(6313) sql(6102) 熊猫(6058) PHP(5869) 数组(5741) R(5409) Linux(5327) 反应(5209) 腳本語言(PerlPython)(5129) 非技術區(4971) Android(4554) 数据框(4311) css(4259) 节点.js(4032) C語言(3288) json(3245) 列表(3129) 扑(3119) C++語言(3117) 安卓(2998) 打字稿(2995) VBA(2789) Java相關(2746) 疑難問題(2699) 细绳(2522) 單片機工控(2479) iOS(2429) ASP.NET(2402) MongoDB(2323) 麻木的(2285) 正则表达式(2254) 字典(2211) 循环(2198) 迅速(2185) 擅长(2169) 镖(2155) 功能(1967) .NET技术(1958) Web開發(1951) python-3.x(1918) HtmlCss(1915) 弹簧靴(1913) C++(1909) xml(1889) PostgreSQL(1872) .NETCore(1853) 谷歌表格(1846) Unity3D(1843) for循环(1842)

熱門瀏覽
  • GPU虛擬機創建時間深度優化

    **?桔妹導讀:**GPU虛擬機實體創建速度慢是公有云面臨的普遍問題,由于通常情況下創建虛擬機屬于低頻操作而未引起業界的重視,實際生產中還是存在對GPU實體創建時間有苛刻要求的業務場景。本文將介紹滴滴云在解決該問題時的思路、方法、并展示最終的優化成果。 從公有云服務商那里購買過虛擬主機的資深用戶,一 ......

    uj5u.com 2020-09-10 06:09:13 more
  • 可編程網卡芯片在滴滴云網路的應用實踐

    **?桔妹導讀:**隨著云規模不斷擴大以及業務層面對延遲、帶寬的要求越來越高,采用DPDK 加速網路報文處理的方式在橫向縱向擴展都出現了局限性。可編程芯片成為業界熱點。本文主要講述了可編程網卡芯片在滴滴云網路中的應用實踐,遇到的問題、帶來的收益以及開源社區貢獻。 #1. 資料中心面臨的問題 隨著滴滴 ......

    uj5u.com 2020-09-10 06:10:21 more
  • 滴滴資料通道服務演進之路

    **?桔妹導讀:**滴滴資料通道引擎承載著全公司的資料同步,為下游實時和離線場景提供了必不可少的源資料。隨著任務量的不斷增加,資料通道的整體架構也隨之發生改變。本文介紹了滴滴資料通道的發展歷程,遇到的問題以及今后的規劃。 #1. 背景 資料,對于任何一家互聯網公司來說都是非常重要的資產,公司的大資料 ......

    uj5u.com 2020-09-10 06:11:05 more
  • 滴滴AI Labs斬獲國際機器翻譯大賽中譯英方向世界第三

    **桔妹導讀:**深耕人工智能領域,致力于探索AI讓出行更美好的滴滴AI Labs再次斬獲國際大獎,這次獲獎的專案是什么呢?一起來看看詳細報道吧! 近日,由國際計算語言學協會ACL(The Association for Computational Linguistics)舉辦的世界最具影響力的機器 ......

    uj5u.com 2020-09-10 06:11:29 more
  • MPP (Massively Parallel Processing)大規模并行處理

    1、什么是mpp? MPP (Massively Parallel Processing),即大規模并行處理,在資料庫非共享集群中,每個節點都有獨立的磁盤存盤系統和記憶體系統,業務資料根據資料庫模型和應用特點劃分到各個節點上,每臺資料節點通過專用網路或者商業通用網路互相連接,彼此協同計算,作為整體提供 ......

    uj5u.com 2020-09-10 06:11:41 more
  • 滴滴資料倉庫指標體系建設實踐

    **桔妹導讀:**指標體系是什么?如何使用OSM模型和AARRR模型搭建指標體系?如何統一流程、規范化、工具化管理指標體系?本文會對建設的方法論結合滴滴資料指標體系建設實踐進行解答分析。 #1. 什么是指標體系 ##1.1 指標體系定義 指標體系是將零散單點的具有相互聯系的指標,系統化的組織起來,通 ......

    uj5u.com 2020-09-10 06:12:52 more
  • 單表千萬行資料庫 LIKE 搜索優化手記

    我們經常在資料庫中使用 LIKE 運算子來完成對資料的模糊搜索,LIKE 運算子用于在 WHERE 子句中搜索列中的指定模式。 如果需要查找客戶表中所有姓氏是“張”的資料,可以使用下面的 SQL 陳述句: SELECT * FROM Customer WHERE Name LIKE '張%' 如果需要 ......

    uj5u.com 2020-09-10 06:13:25 more
  • 滴滴Ceph分布式存盤系統優化之鎖優化

    **桔妹導讀:**Ceph是國際知名的開源分布式存盤系統,在工業界和學術界都有著重要的影響。Ceph的架構和演算法設計發表在國際系統領域頂級會議OSDI、SOSP、SC等上。Ceph社區得到Red Hat、SUSE、Intel等大公司的大力支持。Ceph是國際云計算領域應用最廣泛的開源分布式存盤系統, ......

    uj5u.com 2020-09-10 06:14:51 more
  • es~通過ElasticsearchTemplate進行聚合~嵌套聚合

    之前寫過《es~通過ElasticsearchTemplate進行聚合操作》的文章,這一次主要寫一個嵌套的聚合,例如先對sex集合,再對desc聚合,最后再對age求和,共三層嵌套。 Aggregations的部分特性類似于SQL語言中的group by,avg,sum等函式,Aggregation ......

    uj5u.com 2020-09-10 06:14:59 more
  • 爬蟲日志監控 -- Elastc Stack(ELK)部署

    傻瓜式部署,只需替換IP與用戶 導讀: 現ELK四大組件分別為:Elasticsearch(核心)、logstash(處理)、filebeat(采集)、kibana(可視化) 下載均在https://www.elastic.co/cn/downloads/下tar包,各組件版本最好一致,配合fdm會 ......

    uj5u.com 2020-09-10 06:15:05 more
最新发布
  • day02-2-商鋪查詢快取

    功能02-商鋪查詢快取 3.商鋪詳情快取查詢 3.1什么是快取? 快取就是資料交換的緩沖區(稱作Cache),是存盤資料的臨時地方,一般讀寫性能較高。 快取的作用: 降低后端負載 提高讀寫效率,降低回應時間 快取的成本: 資料一致性成本 代碼維護成本 運維成本 3.2需求說明 如下,當我們點擊商店詳 ......

    uj5u.com 2023-04-20 08:33:24 more
  • MySQL中binlog備份腳本分享

    關于MySQL的二進制日志(binlog),我們都知道二進制日志(binlog)非常重要,尤其當你需要point to point災難恢復的時侯,所以我們要對其進行備份。關于二進制日志(binlog)的備份,可以基于flush logs方式先切換binlog,然后拷貝&壓縮到到遠程服務器或本地服務器 ......

    uj5u.com 2023-04-20 08:28:06 more
  • day02-短信登錄

    功能實作02 2.功能01-短信登錄 2.1基于Session實作登錄 2.1.1思路分析 2.1.2代碼實作 2.1.2.1發送短信驗證碼 發送短信驗證碼: 發送驗證碼的介面為:http://127.0.0.1:8080/api/user/code?phone=xxxxx<手機號> 請求方式:PO ......

    uj5u.com 2023-04-20 08:27:27 more
  • 快取與資料庫雙寫一致性幾種策略分析

    本文將對幾種快取與資料庫保證資料一致性的使用方式進行分析。為保證高并發性能,以下分析場景不考慮執行的原子性及加鎖等強一致性要求的場景,僅追求最終一致性。 ......

    uj5u.com 2023-04-20 08:26:48 more
  • sql陳述句優化

    問題查找及措施 問題查找 需要找到具體的代碼,對其進行一對一優化,而非一直把關注點放在服務器和sql平臺 降低簡化每個事務中處理的問題,盡量不要讓一個事務拖太長的時間 例如檔案上傳時,應將檔案上傳這一步放在事務外面 微軟建議 4.啟動sql定時執行計劃 怎么啟動sqlserver代理服務-百度經驗 ......

    uj5u.com 2023-04-20 08:26:35 more
  • 云時代,MySQL到ClickHouse資料同步產品對比推薦

    ClickHouse 在執行分析查詢時的速度優勢很好的彌補了MySQL的不足,但是對于很多開發者和DBA來說,如何將MySQL穩定、高效、簡單的同步到 ClickHouse 卻很困難。本文對比了 NineData、MaterializeMySQL(ClickHouse自帶)、Bifrost 三款產品... ......

    uj5u.com 2023-04-20 08:26:29 more
  • sql陳述句優化

    問題查找及措施 問題查找 需要找到具體的代碼,對其進行一對一優化,而非一直把關注點放在服務器和sql平臺 降低簡化每個事務中處理的問題,盡量不要讓一個事務拖太長的時間 例如檔案上傳時,應將檔案上傳這一步放在事務外面 微軟建議 4.啟動sql定時執行計劃 怎么啟動sqlserver代理服務-百度經驗 ......

    uj5u.com 2023-04-20 08:25:13 more
  • Redis 報”OutOfDirectMemoryError“(堆外記憶體溢位)

    Redis 報錯“OutOfDirectMemoryError(堆外記憶體溢位) ”問題如下: 一、報錯資訊: 使用 Redis 的業務介面 ,產生 OutOfDirectMemoryError(堆外記憶體溢位),如圖: 格式化后的報錯資訊: { "timestamp": "2023-04-17 22: ......

    uj5u.com 2023-04-20 08:24:54 more
  • day02-2-商鋪查詢快取

    功能02-商鋪查詢快取 3.商鋪詳情快取查詢 3.1什么是快取? 快取就是資料交換的緩沖區(稱作Cache),是存盤資料的臨時地方,一般讀寫性能較高。 快取的作用: 降低后端負載 提高讀寫效率,降低回應時間 快取的成本: 資料一致性成本 代碼維護成本 運維成本 3.2需求說明 如下,當我們點擊商店詳 ......

    uj5u.com 2023-04-20 08:24:03 more
  • day02-短信登錄

    功能實作02 2.功能01-短信登錄 2.1基于Session實作登錄 2.1.1思路分析 2.1.2代碼實作 2.1.2.1發送短信驗證碼 發送短信驗證碼: 發送驗證碼的介面為:http://127.0.0.1:8080/api/user/code?phone=xxxxx<手機號> 請求方式:PO ......

    uj5u.com 2023-04-20 08:23:11 more