言尽于此，完结
无论是一个初级的 coder，高级的程序员，还是顶级的系统架构师，应该都有深刻的领会到设计模式的重要性。
- 第一，设计模式能让专业人之间交流方便，如下：
程序员A：这里我用了XXX设计模式
程序员B：那我大致了解你程序的设计思路了
- 第二，易维护
项目经理：今天客户有这样一个需求…
程序员：明白了，这里我使用了XXX设计模式，所以改起来很快
- 第三，设计模式是编程经验的总结
程序员A：B，你怎么想到要这样去构建你的代码
程序员B：在我学习了XXX设计模式之后，好像自然而然就感觉这样写能避免一些问题
- 第四，学习设计模式并不是必须的
程序员A：B，你这段代码使用的是XXX设计模式对吗？
程序员B：不好意思，我没有学习过设计模式，但是我的经验告诉我是这样写的
从设计思想解读开源框架，一步一步到Spring、Spring5、SpringMVC、MyBatis等源码解读，我都已收集整理全套，篇幅有限，这块只是详细的解说了23种设计模式，整理的文件如下图一览无余！
搜集费时费力，能看到此处的都是真爱！
- dataDir : the location to store the in-memory database snapshots and, unless specified otherwise, the transaction log of updates to the database.
- clientPort : the port to listen for client connections
Now that you created the configuration file, you can start ZooKeeper:
该文件可以被命名为任何文件，但是为了便于讨论，将其命名为conf / zoo.cfg。更改dataDir的值指定以现有（一开始是空文件）目录。以下是每个字段的含义：
-
tickTime：ZooKeeper使用的基本时间单位（毫秒）。它用于做心跳，并且最小会话超时将是tickTime的两倍。
-
dataDir：存储内存数据库快照的位置，除非另有说明，否则存储数据库更新的事务日志。
-
clientPort：用于侦听客户端连接的端口
现在，您已经创建了配置文件，您可以启动ZooKeeper：
bin/zkServer.sh start
ZooKeeper logs messages using log4j – more detail available in the Logging section of the Programmer’s Guide. You will see log messages coming to the console (default) and/or a log file depending on the log4j configuration.
The steps outlined here run ZooKeeper in standalone mode. There is no replication, so if ZooKeeper process fails, the service will go down. This is fine for most development situations, but to run ZooKeeper in replicated mode, please see Running Replicated ZooKeeper.
ZooKeeper使用log4j记录消息-有关详细信息，请参阅《程序员指南》的“记录”部分。您将看到进入控制台的日志消息（默认）和/或一个日志文件，具体取决于log4j配置。
此处概述的步骤以独立模式运行ZooKeeper。没有集群，因此，如果ZooKeeper进程失败，该服务将关闭。这对于大多数开发情况都很好，但是要以集群方式运行ZooKeeper，请参阅“运行ZooKeeper集群”。
Managing ZooKeeper Storage
For long running production systems ZooKeeper storage must be managed externally (dataDir and logs). See the section on maintenance for more details.
Connecting to ZooKeeper
管理ZooKeeper存储
对于长时间运行的生产系统，必须从外部管理ZooKeeper存储（dataDir和日志）。有关更多详细信息，请参见维护部分。
连接到ZooKeeper
$ bin/zkCli.sh -server 127.0.0.1:2181
This lets you perform simple, file-like operations.
Once you have connected, you should see something like:
这使您可以执行简单的类似文件的操作。
连接后，您应该会看到类似以下内容的信息：
Connecting to localhost:2181 log4j:WARN No appenders could be found for logger (org.apache.zookeeper.ZooKeeper). log4j:WARN Please initialize the log4j system properly. Welcome to ZooKeeper! JLine support is enabled [zkshell: 0]
From the shell, type
helpto get a listing of commands that can be executed from the client, as in:
在shell中，键入help以获取可以在客户端执行的命令的列表，如下所示：
[zkshell: 0] help ZooKeeper -server host:port cmd args addauth scheme auth close config [-c] [-w] [-s] connect host:port create [-s] [-e] [-c] [-t ttl] path [data] [acl] delete [-v version] path deleteall path delquota [-n|-b] path get [-s] [-w] path getAcl [-s] path getAllChildrenNumber path getEphemerals path history listquota path ls [-s] [-w] [-R] path ls2 path [watch] printwatches on|off quit reconfig [-s] [-v version] [[-file path] | [-members serverID=host:port1:port2;port3[,...]*]] | [-add serverId=host:port1:port2;port3[,...]]* [-remove serverId[,...]*] redo cmdno removewatches path [-c|-d|-a] [-l] rmr path set [-s] [-v version] path data setAcl [-s] [-v version] [-R] path acl setquota -n|-b val path stat [-w] path sync path
From here, you can try a few simple commands to get a feel for this simple command line interface. First, start by issuing the list command, as in
ls, yielding:
从这里，您可以尝试一些简单的命令，以了解这种简单的命令行界面。首先，如中下所示ls 发出list命令，得到：
[zkshell: 8] ls / [zookeeper]
Next, create a new znode by running
create /zk_test my_data. This creates a new znode and associates the string “my_data” with the node. You should see:
接下来，通过运行创建一个新的znode create /zk_test my_data。这将创建一个新的znode并将字符串“ my_data”与该节点关联。您应该看到：
[zkshell: 9] create /zk_test my_data Created /zk_test
Issue another
ls /command to see what the directory looks like:
发出另一个ls /命令以查看目录的情况：
[zkshell: 11] ls / [zookeeper, zk_test]
Notice that the zk_test directory has now been created.
Next, verify that the data was associated with the znode by running the
getcommand, as in:
请注意，现在已创建zk_test目录。
接下来，通过运行get命令来验证数据是否与znode关联，如下所示：
[zkshell: 12] get /zk_test my_data cZxid = 5 ctime = Fri Jun 05 13:57:06 PDT 2009 mZxid = 5 mtime = Fri Jun 05 13:57:06 PDT 2009 pZxid = 5 cversion = 0 dataVersion = 0 aclVersion = 0 ephemeralOwner = 0 dataLength = 7 numChildren = 0
We can change the data associated with zk_test by issuing the
setcommand, as in:
我们可以通过发出set命令来更改与zk_test相关的数据，如下所示：
[zkshell: 14] set /zk_test junk cZxid = 5 ctime = Fri Jun 05 13:57:06 PDT 2009 mZxid = 6 mtime = Fri Jun 05 14:01:52 PDT 2009 pZxid = 5 cversion = 0 dataVersion = 1 aclVersion = 0 ephemeralOwner = 0 dataLength = 4 numChildren = 0 [zkshell: 15] get /zk_test junk cZxid = 5 ctime = Fri Jun 05 13:57:06 PDT 2009 mZxid = 6 mtime = Fri Jun 05 14:01:52 PDT 2009 pZxid = 5 cversion = 0 dataVersion = 1 aclVersion = 0 ephemeralOwner = 0 dataLength = 4 numChildren = 0
(Notice we did a
getafter setting the data and it did, indeed, change.
Finally, let’s
deletethe node by issuing:
（请注意，我们在设置数据后做了一个改变，get确认确实发生了变化。
最后，通过发出以下命令delete来删除节点：
[zkshell: 16] delete /zk_test [zkshell: 17] ls / [zookeeper] [zkshell: 18]
That’s it for now. To explore more, see the Zookeeper CLI.
现在就这样。要了解更多信息，请参见Zookeeper CLI。
Programming to ZooKeeper
ZooKeeper has a Java bindings and C bindings. They are functionally equivalent. The C bindings exist in two variants: single threaded and multi-threaded. These differ only in how the messaging loop is done. For more information, see the Programming Examples in the ZooKeeper Programmer’s Guide for sample code using the different APIs.
Running Replicated ZooKeeper
Running ZooKeeper in standalone mode is convenient for evaluation, some development, and testing. But in production, you should run ZooKeeper in replicated mode. A replicated group of servers in the same application is called a quorum, and in replicated mode, all servers in the quorum have copies of the same configuration file.
针对ZooKeeper编程
ZooKeeper具有Java绑定和C绑定。它们在功能上是等效的。C绑定存在两种变体：单线程和多线程。这些区别仅在于消息传递循环的完成方式。有关更多信息，请参见《ZooKeeper程序员指南》中的“编程示例”，以获取使用不同API的示例代码。
运行集群的ZooKeeper
以独立模式运行ZooKeeper便于评估，某些开发和测试。但是在生产中，您应该在集群模式下运行ZooKeeper。同一应用程序中的一组服务器的集群组称为（quorum）仲裁，并且在集群模式下，仲裁中的所有服务器都具有相同配置文件的副本。
Note
For replicated mode, a minimum of three servers are required, and it is strongly recommended that you have an odd number of servers. If you only have two servers, then you are in a situation where if one of them fails, there are not enough machines to form a majority quorum. Two servers are inherently less stable than a single server, because there are two single points of failure.
The required conf/zoo.cfg file for replicated mode is similar to the one used in standalone mode, but with a few differences. Here is an example:
注意
对于集群模式，至少需要三个服务器，并且强烈建议您使用奇数个服务器。如果只有两台服务器，那么您将处于一种情况，如果其中一台服务器发生故障，则没有足够的计算机构成多数仲裁。由于存在两个单点故障，因此两个服务器就不如单个服务器稳定。
集群模式所需的conf / zoo.cfg文件类似于独立模式下使用的文件，但有一些区别。这是一个例子：
tickTime=2000 dataDir=/var/lib/zookeeper clientPort=2181 initLimit=5 syncLimit=2 server.1=zoo1:2888:3888 server.2=zoo2:2888:3888 server.3=zoo3:2888:3888
The new entry, initLimit is timeouts ZooKeeper uses to limit the length of time the ZooKeeper servers in quorum have to connect to a leader. The entry syncLimit limits how far out of date a server can be from a leader.
总结
这份面试题几乎包含了他在一年内遇到的所有面试题以及答案，甚至包括面试中的细节对话以及语录，可谓是细节到极致，甚至简历优化和怎么投简历更容易得到面试机会也包括在内！也包括教你怎么去获得一些大厂，比如阿里，腾讯的内推名额！
某位名人说过成功是靠99%的汗水和1%的机遇得到的，而你想获得那1%的机遇你首先就得付出99%的汗水！你只有朝着你的目标一步一步坚持不懈的走下去你才能有机会获得成功！
成功只会留给那些有准备的人！
也包括在内！也包括教你怎么去获得一些大厂，比如阿里，腾讯的内推名额！
某位名人说过成功是靠99%的汗水和1%的机遇得到的，而你想获得那1%的机遇你首先就得付出99%的汗水！你只有朝着你的目标一步一步坚持不懈的走下去你才能有机会获得成功！
成功只会留给那些有准备的人！
[外链图片转存中…(img-Rh0H0XA1-1715585034052)]
2879
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
