ZooKeeper只完美解决Unable to read additional data from server sessionid 0x0报错问题,并带你深度理解ZooKeeper内部机制之选举机制

这篇具有很好参考价值的文章主要介绍了ZooKeeper只完美解决Unable to read additional data from server sessionid 0x0报错问题,并带你深度理解ZooKeeper内部机制之选举机制。希望对大家有所帮助。如果存在错误或未考虑完全的地方,请大家不吝赐教,您也可以点击"举报违法"按钮提交疑问。

🍅 作者简介:上火不找我,CSDN2022新星计划top4🏆、算法领域新星创造者💪
🍅有什么问题直接私信作者,秒回哦💪💪💪


一、问题描述

Linux环境下

今天搭建了一个zookeeper集群,分别为server2,server3,server4。

ZooKeeper只完美解决Unable to read additional data from server sessionid 0x0报错问题,并带你深度理解ZooKeeper内部机制之选举机制

报错如下:

2022-08-08 22:10:44,294 [myid:localhost:2181] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@1240] - Unable to read additional data from server sessionid 0x0, likely server has closed socket, closing socket connection and attempting reconnect
2022-08-08 22:10:45,716 [myid:localhost:2181] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@1112] - Opening socket connection to server localhost/0:0:0:0:0:0:0:1:2181. Will not attempt to authenticate using SASL (unknown error)
2022-08-08 22:10:45,717 [myid:localhost:2181] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@959] - Socket connection established, initiating session, client: /0:0:0:0:0:0:0:1:41288, server: localhost/0:0:0:0:0:0:0:1:2181
2022-08-08 22:10:45,718 [myid:localhost:2181] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@1240] - Unable to read additional data from server sessionid 0x0, likely server has closed socket, closing socket connection and attempting reconnect
2022-08-08 22:10:47,382 [myid:localhost:2181] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@1112] - Opening socket connection to server localhost/0:0:0:0:0:0:0:1:2181. Will not attempt to authenticate using SASL (unknown error)
2022-08-08 22:10:47,383 [myid:localhost:2181] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@959] - Socket connection established, initiating session, client: /0:0:0:0:0:0:0:1:41290, server: localhost/0:0:0:0:0:0:0:1:2181
2022-08-08 22:10:47,384 [myid:localhost:2181] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@1240] - Unable to read additional data from server sessionid 0x0, likely server has closed socket, closing socket connection and attempting reconnect
2022-08-08 22:10:48,849 [myid:localhost:2181] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@1112] - Opening socket connection to server localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL (unknown error)
2022-08-08 22:10:48,850 [myid:localhost:2181] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@959] - Socket connection established, initiating session, client: /127.0.0.1:39428, server: localhost/127.0.0.1:2181
2022-08-08 22:10:48,852 [myid:localhost:2181] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@1240] - Unable to read additional data from server sessionid 0x0, likely server has closed socket, closing socket connection and attempting reconnect
2022-08-08 22:10:50,397 [myid:localhost:2181] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@1112] - Opening socket connection to server localhost/0:0:0:0:0:0:0:1:2181. Will not attempt to authenticate using SASL (unknown error)
2022-08-08 22:10:50,398 [myid:localhost:2181] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@959] - Socket connection established, initiating session, client: /0:0:0:0:0:0:0:1:41294, server: localhost/0:0:0:0:0:0:0:1:2181
2022-08-08 22:10:50,399 [myid:localhost:2181] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@1240] - Unable to read additional data from server sessionid 0x0, likely server has closed socket, closing socket connection and attempting reconnect
2022-08-08 22:10:52,214 [myid:localhost:2181] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@1112] - Opening socket connection to server localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL (unknown error)
2022-08-08 22:10:52,215 [myid:localhost:2181] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@959] - Socket connection established, initiating session, client: /127.0.0.1:39432, server: localhost/127.0.0.1:2181
2022-08-08 22:10:52,217 [myid:localhost:2181] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@1240] - Unable to read additional data from server sessionid 0x0, likely server has closed socket, closing socket connection and attempting reconnect
2022-08-08 22:10:54,073 [myid:localhost:2181] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@1112] - Opening socket connection to server localhost/0:0:0:0:0:0:0:1:2181. Will not attempt to authenticate using SASL (unknown error)
2022-08-08 22:10:54,074 [myid:localhost:2181] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@959] - Socket connection established, initiating session, client: /0:0:0:0:0:0:0:1:41298, server: localhost/0:0:0:0:0:0:0:1:2181
2022-08-08 22:10:54,077 [myid:localhost:2181] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@1240] - Unable to read additional data from server sessionid 0x0, likely server has closed socket, closing socket connection and attempting reconnect
2022-08-08 22:10:55,613 [myid:localhost:2181] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@1112] - Opening socket connection to server localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL (unknown error)
2022-08-08 22:10:55,614 [myid:localhost:2181] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@959] - Socket connection established, initiating session, client: /127.0.0.1:39436, server: localhost/127.0.0.1:2181

在一个节点上进入到zookeeper命令行执行zkCli.sh 时,报了下面这个异常!

ZooKeeper只完美解决Unable to read additional data from server sessionid 0x0报错问题,并带你深度理解ZooKeeper内部机制之选举机制


二、原因分析

一开始我以为配置文件的错误,但是经过检查后发现并不是这里的问题,所以我开始思考zookeeper的搭建机制

例如:半数机制:集群中半数以上机器存活,集群可用。所以Zookeeper适合安装奇数台服务器。


三、解决方案

例如你一次性启动了三台服务器,并且都使用zookeeper进行调度的话,就至少需要启动两台的zookeeper

那么你只需要再启动一台机器的zookeeper,多按几下回车刷新就可以了

ZooKeeper只完美解决Unable to read additional data from server sessionid 0x0报错问题,并带你深度理解ZooKeeper内部机制之选举机制

🍅 作者简介:上火不找我,CSDN2022新星计划top4🏆、算法领域新星创造者💪
🍅有什么问题直接私信作者,秒回哦💪💪💪

🍅有帮助的记得给个三连支持一下,谢谢~~~💪💪💪文章来源地址https://www.toymoban.com/news/detail-404133.html

到了这里,关于ZooKeeper只完美解决Unable to read additional data from server sessionid 0x0报错问题,并带你深度理解ZooKeeper内部机制之选举机制的文章就介绍完了。如果您还想了解更多内容,请在右上角搜索TOY模板网以前的文章或继续浏览下面的相关文章,希望大家以后多多支持TOY模板网!

本文来自互联网用户投稿,该文观点仅代表作者本人,不代表本站立场。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如若转载,请注明出处: 如若内容造成侵权/违法违规/事实不符,请点击违法举报进行投诉反馈,一经查实,立即删除!

领支付宝红包 赞助服务器费用

相关文章

  • error: unable to read askpass response from 解决办法

    出现这个报错,我认为原因与你的码云账号有关,因为我在网上大量搜过这个问题,最后 检查了一番原来是gitee账号登录过期,于是重新进行登录,可是登录成功还是提示错误,最后网上找了好久的方法终于找到解决办法,特此记录一下。 直接修改项目目录下面的.git文件夹

    2024年02月10日
    浏览(16)
  • Git配置代理:fatal: unable to access*** github Failure when receiving data from

    github自从被微软收购以后,大多数情况没点科技上网都进不去了,还是怀念以前随时访问的时光。 我一直都是开着系统代理的,但是今天拉一个项目发现拉不下来了,报错: 这只能说明我自己的Git里面代理没生效咯~ 那就自己手动设置吧! 首先看一下自己的配置 设置代理

    2024年02月05日
    浏览(22)
  • IDEA GIT error:unable to read askpass response from,bash: /dev/tty: No such device or address

    1. 删除windows凭据,方法这里就不说了自行百度,这种应该只适合账号密码输入错误的情况,我试了没啥用 2. git的拉取代码地址上拼接上账号密码,操作步骤如下 亲测有用 ,修改后的格式如下,虽然可以拉取代码但是总觉得不够优雅,又去找找有没有其他方法 https://[userNam

    2024年02月13日
    浏览(17)
  • 【git提示error: unable to read askpass response from ‘xxxintellij-git-askpass.bat‘ bash: /dev/tty: No 】

    原因:昨天项目还可以进行pull push,可以今天就不行了,idea提示 error: unable to read askpass response from ‘xxxintellij-git-askpass.bat’ bash: /dev/tty: No such device or address. 检查了一番原来是gitee账号登录过期,于是重新进行登录,可是登录成功还是提示错误,最后网上找了好久的方法终于

    2024年02月14日
    浏览(13)
  • error: unable to read askpass response from ‘C:\Users\***\AppData\Local\JetBrains\IntelliJIdea20

    18:38:15.369: [tianji] git -c credential.helper= -c core.quotepath=false -c log.showSignature=false push --progress --porcelain origin refs/heads/dev:dev --set-upstream Enumerating objects: 23, done. ..... Writing objects: 100% (12/12), 920 bytes | 184.00 KiB/s, done. Total 12 (delta 5), reused 0 (delta 0), pack-reused 0 Invocation failed Server returned inv

    2024年02月14日
    浏览(12)
  • 完美解决 fatal: unable to access ‘https://github.com/Homebrew/brew/‘

    更新了系统,安装 Homebrew 老失败,报错: fatal: unable to access \\\'https://github.com/Homebrew/brew/\\\': 解决方案,执行下面两行命令: 其他错误解决

    2024年02月11日
    浏览(24)
  • 一文教你完美解决Linux中Unable to locate package xxx问题,解决不了你打我!

    使用Ubuntu系统进行开发 这两天跟着一门网 课学 把html的网页部署到云服务器,于是租了个Ubuntu云服务器,照着网课的代码去执行,然后一直出现这个问题,各种包都找不到,以及之前用Ubuntu的时候也出现过这个问题,从网上搜了30个中文的回答,解决方案大抵一致,全都试了

    2024年02月02日
    浏览(17)
  • 解决Hbase报错:ERROR: Can‘t get master address from ZooKeeper; znode data == null

    报错了:这啥公司啊,怎么给的文档怎么错这么多,起一服务,集群里总有几个组件报错 继上次Flume 脚本,使用hdfs sink报错了以后,hbase又报错了,报错提示如下: 此报错呢,可能是因为zookeeper集群不稳定导致,zookeeper集群和目前的跑数据脚本的集群不一致,我询问了一下,

    2024年02月04日
    浏览(34)
  • unable to read askpass response from ‘C:\Users\EDY\AppData\Local\JetBrains\IntelliJIdea2023.2\tmp\in

    在Windows中安装git之后,在idea中又配置git的仓库。 在我通过VCS方式去拉取远程代码的时候就出现如下问题: unable to read askpass response from \\\'C:UsersEDYAppDataLocalJetBrainsIntelliJIdea2023.2tmpintellij-git-askpass-local.sh\\\' bash: line 1: /dev/tty: No such device or address failed to execute prompt script (exit c

    2024年02月07日
    浏览(15)
  • 【解决】axios 下载文件 Failed to read the 'responseText' property from 'XMLHttpRequest'

    主要解决以下两个问题 问题一:idm一些网站不允许请求同一文件两次 故障原因: IDM 在发神经 因为它检测到浏览器集成插件未安装,所以诱导你安装。实际上,装了插件问题也会出现。改参数都没用。 1.很可能是你点击网页的 下载链接 有问题(换个网页下载试试,就不提示

    2024年02月01日
    浏览(11)

觉得文章有用就打赏一下文章作者

支付宝扫一扫打赏

博客赞助

微信扫一扫打赏

请作者喝杯咖啡吧~博客赞助

支付宝扫一扫领取红包,优惠每天领

二维码1

领取红包

二维码2

领红包