# The number of milliseconds of each ticktickTime=2000# The number of ticks that the initial # synchronization phase can take#initLimit=10# The number of ticks that can pass between # sending a request and getting an acknowledgement#syncLimit=5# the directory where the snapshot is stored.# do not use /tmp for storage, /tmp here is just # example sakes.dataDir=E:\JetBrains\zookeeper-3.4.10\datadataLogDir=E:\JetBrains\zookeeper-3.4.10\log# the port at which the clients will connectclientPort=2181# the maximum number of client connections.# increase this if you need to handle more clients#maxClientCnxns=60## Be sure to read the maintenance section of the # administrator guide before turning on autopurge.## http://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_maintenance## The number of snapshots to retain in dataDir#autopurge.snapRetainCount=3# Purge task interval in hours# Set to "0" to disable auto purge feature#autopurge.purgeInterval=1

tickTime：这个时间是作为 Zookeeper 服务器之间或客户端与服务器之间维持心跳的时间间隔，也就是每个 tickTime 时间就会发送一个心跳。initLimit：这个配置项是用来配置 Zookeeper 接受客户端（这里所说的客户端不是用户连接 Zookeeper 服务器的客户端，而是 Zookeeper 服务器集群中连接到 Leader 的 Follower 服务器）初始化连接时最长能忍受多少个心跳时间间隔数。当已经超过 10 个心跳的时间（也就是 tickTime）长度后 Zookeeper 服务器还没有收到客户端的返回信息，那么表明这个客户端连接失败。总的时间长度就是 5*2000=10 秒syncLimit：这个配置项标识 Leader 与 Follower 之间发送消息，请求和应答时间长度，最长不能超过多少个 tickTime 的时间长度，总的时间长度就是 2*2000=4 秒dataDir：顾名思义就是 Zookeeper 保存数据的目录，默认情况下，Zookeeper 将写数据的日志文件也保存在这个目录里。clientPort：这个端口就是客户端连接 Zookeeper 服务器的端口，Zookeeper 会监听这个端口，接受客户端的访问请求。

1.添加系统变量 ZOOKEEPER_HOME:E:\JetBrains\zookeeper-3.4.102.新建在Path变量 Path:%ZOOKEEPER_HOME%/bin;%ZOOKEEPER_HOME%/conf

C:\Users\Chova>node -vC:\Users\Chova>npm -v

npm config set prefix  E:\JetBrains\nodejs\node_global  npm config set cache E:\JetBrains\nodejs\node_cache

1.在 系统变量 下新建 NODE_PATH ,输入E:\JetBrains\nodej\node_global\node_modules2.将 用户变量 下的 Path 修改为 E:\JetBrains\nodej\node_global

npm start

A complete log of this run can be found in:C:\Users\56386\AppData\Roaming\npm-cache\_logs\2019-04-26T02_09_33_735Z-debug.log

npm i npm -g  全局更新
或者
npm cache clean --force    清理后重新安装
或者
npm install webpack --save    强制安装依赖

npm install webpack@3.6.0 -g
npm i optimize-css-assets-webpack-plugin@3.2.0

npm install webpack --save    # 强制安装依赖

C:\Users\Chova>redis-server.exe

redis-server.exe：服务端程序，提供redis服务redis-cli.exe: 客户端程序，通过它连接redis服务并进行操作redis-check-dump.exe：本地数据库检查redis-check-aof.exe：更新日志检查redis-benchmark.exe：性能测试，用以模拟同时由N个客户端发送M个 SETs/GETs 查询 (类似于 Apache 的ab 工具).redis.windows.conf: 配置文件，将redis作为普通软件使用的配置，命令行关闭则redis关闭redis.windows-service.conf：配置文件，将redis作为系统服务的配置，用以区别开两种不同的使用方式

redis-server.exe redis.windows.conf

redis-server.exe redis.windows.conf

mongo   使用数据库mongod  开机mongoimport  导入数据
开机命令:(开机完成后,这个cmd窗口就保持这样)mongod --dpath c:\mongo
新开一个cmd窗口输入:mongo
运行数据库语法:show dbs  列出所有数据库use dbname  使用数据库db      查看当前所在数据库db.dbname.insert({});  插入数据db.dropDatabase();    删除数据库，删除当前所在的数据库
db.restaurants.find();  查找数据，用find。find中没有参数，那么将列出这个集合的所有文档db.dbname.find({"score.shuxue":70});  精确匹配db.dbname.find({"score.shuxue":70 , "age":12});    多个条件db.dbname.find({"score.yuwen":{$gt:50}});      大于条件  db.dbname.find({$or:[{"age":9},{"age":11}]});    寻找所有年龄是9岁，或者11岁的db.dbname.find().sort({ "borough": 1, "address.zipcode": 1 })  查找完毕之后，打点调用sort，表示升降排序
db.dbname.update({"name":"小明"},{$set:{"age":16}});      查找名字叫做小明的，把年龄更改为16岁db.dbname.update({"score.shuxue":70},{$set:{"age":33}});    查找数学成绩是70，把年龄更改为33岁db.dbname.update({"sex":"男"},{$set:{"age":33}},{multi: true});  更改所有匹配项目db.restaurants.remove( { "borough": "Manhattan" } );      删除数据

E:\JetBrains\maven\apache-maven-3.6.1\conf\settings.xml

<?xml version="1.0" encoding="UTF-8"?>
<!--Licensed to the Apache Software Foundation (ASF) under oneor more contributor license agreements.  See the NOTICE filedistributed with this work for additional informationregarding copyright ownership.  The ASF licenses this fileto you under the Apache License, Version 2.0 (the"License"); you may not use this file except in compliancewith the License.  You may obtain a copy of the License at
    http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,software distributed under the License is distributed on an"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANYKIND, either express or implied.  See the License for thespecific language governing permissions and limitationsunder the License.-->
<!-- | This is the configuration file for Maven. It can be specified at two levels: | |  1. User Level. This settings.xml file provides configuration for a single user, |                 and is normally provided in ${user.home}/.m2/settings.xml. | |                 NOTE: This location can be overridden with the CLI option: | |                 -s /path/to/user/settings.xml | |  2. Global Level. This settings.xml file provides configuration for all Maven |                 users on a machine (assuming they're all using the same Maven |                 installation). It's normally provided in |                 ${maven.home}/conf/settings.xml. | |                 NOTE: This location can be overridden with the CLI option: | |                 -gs /path/to/global/settings.xml | | The sections in this sample file are intended to give you a running start at | getting the most out of your Maven installation. Where appropriate, the default | values (values used when the setting is not specified) are provided. | |--><settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">  <!-- localRepository   | The path to the local repository maven will use to store artifacts.   |   | Default: ${user.home}/.m2/repository  <localRepository>/path/to/local/repo</localRepository>  --><localRepository>D:/maven-XD/repository</localRepository>  <!-- interactiveMode   | This will determine whether maven prompts you when it needs input. If set to false,   | maven will use a sensible default value, perhaps based on some other setting, for   | the parameter in question.   |   | Default: true  <interactiveMode>true</interactiveMode>  -->
  <!-- offline   | Determines whether maven should attempt to connect to the network when executing a build.   | This will have an effect on artifact downloads, artifact deployment, and others.   |   | Default: false  <offline>false</offline>  -->
  <!-- pluginGroups   | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.   | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers   | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.   |-->  <pluginGroups>    <!-- pluginGroup     | Specifies a further group identifier to use for plugin lookup.    <pluginGroup>com.your.plugins</pluginGroup>    -->  </pluginGroups>
  <!-- proxies   | This is a list of proxies which can be used on this machine to connect to the network.   | Unless otherwise specified (by system property or command-line switch), the first proxy   | specification in this list marked as active will be used.   |-->  <proxies>    <!-- proxy     | Specification for one proxy, to be used in connecting to the network.     |    <proxy>      <id>optional</id>      <active>true</active>      <protocol>http</protocol>      <username>proxyuser</username>      <password>proxypass</password>      <host>proxy.host.net</host>      <port>80</port>      <nonProxyHosts>local.net|some.host.com</nonProxyHosts>    </proxy>    -->  </proxies>
  <!-- servers   | This is a list of authentication profiles, keyed by the server-id used within the system.   | Authentication profiles can be used whenever maven must make a connection to a remote server.   |-->  <servers>    <!-- server     | Specifies the authentication information to use when connecting to a particular server, identified by     | a unique name within the system (referred to by the 'id' attribute below).     |     | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are     |       used together.     |    <server>      <id>deploymentRepo</id>      <username>repouser</username>      <password>repopwd</password>    </server>    -->    <server>      <id>tomcat7</id>      <username>admin</username>      <password>admin</password>    </server>    <!-- Another sample, using keys to authenticate.    <server>      <id>siteServer</id>      <privateKey>/path/to/private/key</privateKey>      <passphrase>optional; leave empty if not used.</passphrase>    </server>    -->      <server>            <id>nexus-public</id>              <username>admin</username>              <password>admin123</password>          </server>    <server>            <id>3rd</id>              <username>admin</username>              <password>admin123</password>          </server>    <server>            <id>nexus-releases</id>              <username>admin</username>              <password>admin123</password>          </server>    <server>            <id>nexus-snapshots</id>              <username>admin</username>              <password>admin123</password>          </server>  </servers>
  <!-- mirrors   | This is a list of mirrors to be used in downloading artifacts from remote repositories.   |   | It works like this: a POM may declare a repository to use in resolving certain artifacts.   | However, this repository may have problems with heavy traffic at times, so people have mirrored   | it to several places.   |   | That repository definition will have a unique id, so we can create a mirror reference for that   | repository, to be used as an alternate download site. The mirror site will be the preferred   | server for that repository.   |-->  <mirrors>    <!-- mirror     | Specifies a repository mirror site to use instead of a given repository. The repository that     | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used     | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.     |    <mirror>      <id>mirrorId</id>      <mirrorOf>repositoryId</mirrorOf>      <name>Human Readable Name for this Mirror.</name>      <url>http://my.repository.com/repo/path</url>    </mirror>     -->    <!--  <mirror>                        <id>nexus-aliyun</id>                        <mirrorOf>*,!jeecg,!jeecg-snapshots</mirrorOf>                        <name>Nexus aliyun</name>                        <url>http://maven.aliyun.com/nexus/content/groups/public</url>        </mirror>  -->     <!--<repository>        <id>repository.springframework.maven.milestone</id>        <name>Spring Framework Maven Milestone Repository</name>        <url>http://repo.spring.io/milestone/</url>    </repository>-->   <mirror>      <id>nexus-public</id>      <name>nexus-public</name>      <url>http://47.97.168.188:8888/nexus/content/groups/public/</url>      <mirrorOf>*</mirrorOf>            </mirror>    <mirror>      <id>alimaven</id>      <name>aliyun maven</name>      <url>http://maven.aliyun.com/nexus/content/groups/public/</url>      <mirrorOf>central</mirrorOf>            </mirror>   <mirror>      <id>3rd</id>      <name>3rd</name>      <url>http://47.97.168.188:8888/nexus/content/repositories/thirdparty/</url>      <mirrorOf>*</mirrorOf>            </mirror>       </mirrors>
  <!-- profiles   | This is a list of profiles which can be activated in a variety of ways, and which can modify   | the build process. Profiles provided in the settings.xml are intended to provide local machine-   | specific paths and repository locations which allow the build to work in the local environment.   |   | For example, if you have an integration testing plugin - like cactus - that needs to know where   | your Tomcat instance is installed, you can provide a variable here such that the variable is   | dereferenced during the build process to configure the cactus plugin.   |   | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles   | section of this document (settings.xml) - will be discussed later. Another way essentially   | relies on the detection of a system property, either matching a particular value for the property,   | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a   | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.   | Finally, the list of active profiles can be specified directly from the command line.   |   | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact   |       repositories, plugin repositories, and free-form properties to be used as configuration   |       variables for plugins in the POM.   |   |-->  <profiles>        <!-- profile     | Specifies a set of introductions to the build process, to be activated using one or more of the     | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>     | or the command line, profiles have to have an ID that is unique.     |     | An encouraged best practice for profile identification is to use a consistent naming convention     | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.     | This will make it more intuitive to understand what the set of introduced profiles is attempting     | to accomplish, particularly when you only have a list of profile id's for debug.     |     | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.    <profile>      <id>jdk-1.4</id>
      <activation>        <jdk>1.4</jdk>      </activation>
      <repositories>        <repository>          <id>jdk14</id>          <name>Repository for JDK 1.4 builds</name>          <url>http://www.myhost.com/maven/jdk14</url>          <layout>default</layout>          <snapshotPolicy>always</snapshotPolicy>        </repository>      </repositories>    </profile>    -->
    <!--     | Here is another profile, activated by the system property 'target-env' with a value of 'dev',     | which provides a specific path to the Tomcat instance. To use this, your plugin configuration     | might hypothetically look like:     |     | ...     | <plugin>     |   <groupId>org.myco.myplugins</groupId>     |   <artifactId>myplugin</artifactId>     |     |   <configuration>     |     <tomcatLocation>${tomcatPath}</tomcatLocation>     |   </configuration>     | </plugin>     | ...     |     | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to     |       anything, you could just leave off the <value/> inside the activation-property.     |    <profile>      <id>env-dev</id>
      <activation>        <property>          <name>target-env</name>          <value>dev</value>        </property>      </activation>
      <properties>        <tomcatPath>/path/to/tomcat/instance</tomcatPath>      </properties>    </profile>    -->  </profiles>  
  <!-- activeProfiles   | List of profiles that are active for all builds.   |  <activeProfiles>    <activeProfile>alwaysActiveProfile</activeProfile>    <activeProfile>anotherAlwaysActiveProfile</activeProfile>  </activeProfiles>  --></settings>