新增js代码规范笔记

新增kafka配置文件笔记
新增zk配置文件笔记
新增阿里一面笔记

Git学习笔记/README.md

@@ -1,9 +0,0 @@
->123
->1231
->>>12313123
->>>123213
-adas 
-ada s
-
-
-as d

Git学习笔记/开发规范.md

@@ -0,0 +1,25 @@
+### 开发规范
+
+**分支命名**：日期_姓名首字母缩写_功能单词，如：`220804_shb_redisCache`
+
+**提交规范**：`作者，type: desc` 如：`seamew，feat：增加redis缓存` *参考Commit message 规范*
+
+```
+# 主要type
+feat:     增加新功能
+fix:      修复bug
+
+# 特殊type
+docs:     只改动了文档相关的内容
+style:    不影响代码含义的改动，例如去掉空格、改变缩进、增删分号
+build:    构造工具的或者外部依赖的改动，例如webpack，npm
+refactor: 代码重构时使用
+revert:   执行git revert打印的message
+
+# 暂不使用type
+test:     添加测试或者修改现有测试
+perf:     提高性能的改动
+ci:       与CI（持续集成服务）有关的改动
+chore:    不修改src或者test的其余修改，例如构建过程或辅助工具的变动
+```
+

大数据/kafka/3.kafka配置文件详解.md

@@ -0,0 +1,154 @@
+```properties
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements.  See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# 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 ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+# see kafka.server.KafkaConfig for additional details and defaults
+
+############################# Server Basics #############################
+
+# The id of the broker. This must be set to a unique integer for each broker.
+broker.id=0
+
+############################# Socket Server Settings #############################
+
+# The address the socket server listens on. It will get the value returned from 
+# java.net.InetAddress.getCanonicalHostName() if not configured.
+#   FORMAT:
+#     listeners = listener_name://host_name:port
+#   EXAMPLE:
+#     listeners = PLAINTEXT://your.host.name:9092
+#listeners=PLAINTEXT://:9092
+listeners=PLAINTEXT://192.168.0.4:9092
+# Hostname and port the broker will advertise to producers and consumers. If not set, 
+# it uses the value for "listeners" if configured.  Otherwise, it will use the value
+# returned from java.net.InetAddress.getCanonicalHostName().
+# 远程监控端口+IP
+advertised.listeners=PLAINTEXT://180.76.231.231:9092
+
+# Maps listener names to security protocols, the default is for them to be the same. See the config documentation for more details
+#listener.security.protocol.map=PLAINTEXT:PLAINTEXT,SSL:SSL,SASL_PLAINTEXT:SASL_PLAINTEXT,SASL_SSL:SASL_SSL
+
+# The number of threads that the server uses for receiving requests from the network and sending responses to the network
+# 网络线程数
+num.network.threads=20
+
+# The number of threads that the server uses for processing requests, which may include disk I/O
+# io线程数量
+num.io.threads=20
+
+# The send buffer (SO_SNDBUF) used by the socket server
+socket.send.buffer.bytes=102400
+
+# The receive buffer (SO_RCVBUF) used by the socket server
+socket.receive.buffer.bytes=102400
+
+# The maximum size of a request that the socket server will accept (protection against OOM)
+socket.request.max.bytes=104857600
+
+
+############################# Log Basics #############################
+
+# A comma separated list of directories under which to store log files
+# r
+log.dirs=/opt/modules/kafka/logs
+
+# The default number of log partitions per topic. More partitions allow greater
+# parallelism for consumption, but this will also result in more files across
+# the brokers.
+num.partitions=1
+
+# The number of threads per data directory to be used for log recovery at startup and flushing at shutdown.
+# This value is recommended to be increased for installations with data dirs located in RAID array.
+num.recovery.threads.per.data.dir=1
+
+############################# Internal Topic Settings  #############################
+# The replication factor for the group metadata internal topics "__consumer_offsets" and "__transaction_state"
+# For anything other than development testing, a value greater than 1 is recommended to ensure availability such as 3.
+offsets.topic.replication.factor=3
+transaction.state.log.replication.factor=3
+transaction.state.log.min.isr=3
+
+############################# Log Flush Policy #############################
+
+# Messages are immediately written to the filesystem but by default we only fsync() to sync
+# the OS cache lazily. The following configurations control the flush of data to disk.
+# There are a few important trade-offs here:
+#    1. Durability: Unflushed data may be lost if you are not using replication.
+#    2. Latency: Very large flush intervals may lead to latency spikes when the flush does occur as there will be a lot of data to flush.
+#    3. Throughput: The flush is generally the most expensive operation, and a small flush interval may lead to excessive seeks.
+# The settings below allow one to configure the flush policy to flush data after a period of time or
+# every N messages (or both). This can be done globally and overridden on a per-topic basis.
+
+# The number of messages to accept before forcing a flush of data to disk
+#log.flush.interval.messages=10000
+
+# The maximum amount of time a message can sit in a log before we force a flush
+#log.flush.interval.ms=1000
+
+############################# Log Retention Policy #############################
+
+# The following configurations control the disposal of log segments. The policy can
+# be set to delete segments after a period of time, or after a given size has accumulated.
+# A segment will be deleted whenever *either* of these criteria are met. Deletion always happens
+# from the end of the log.
+
+# The minimum age of a log file to be eligible for deletion due to age
+log.retention.hours=168
+
+# A size-based retention policy for logs. Segments are pruned from the log unless the remaining
+# segments drop below log.retention.bytes. Functions independently of log.retention.hours.
+#log.retention.bytes=1073741824
+
+# The maximum size of a log segment file. When this size is reached a new log segment will be created.
+log.segment.bytes=1073741824
+
+# The interval at which log segments are checked to see if they can be deleted according
+# to the retention policies
+log.retention.check.interval.ms=300000
+
+############################# Zookeeper #############################
+
+# Zookeeper connection string (see zookeeper docs for details).
+# This is a comma separated host:port pairs, each corresponding to a zk
+# server. e.g. "127.0.0.1:3000,127.0.0.1:3001,127.0.0.1:3002".
+# You can also append an optional chroot string to the urls to specify the
+# root directory for all kafka znodes.
+zookeeper.connect=192.168.0.4:2181
+# 是否运行删除topic
+delete.topic.enable=true
+
+# Timeout in ms for connecting to zookeeper
+# zookeeper.connection.timeout.ms 是 Kafka 配置文件中用于配置与 ZooKeeper 建立连接时的超时时间，表示在连接 ZooKeeper 时等待响应的时间。如果在超时时间内没有收到来自 ZooKeeper 的响应，连接将被视为已经断开。
+
+# 默认情况下，zookeeper.connection.timeout.ms 的值为 6000 毫秒（即 6 秒），如果你的 Kafka 集群中 ZooKeeper 响应时间较慢，你可能需要增加此值以避免因连接超时而导致的故障。
+zookeeper.connection.timeout.ms=60000
+# 这个值非常重要
+# 如果 Kafka Broker 与 ZooKeeper 之间的连接在 zookeeper.session.timeout.ms 时间内没有收到任何通信，
+# 那么 Kafka Broker 将被认为已失去与 ZooKeeper 的联系，并会退出运行。
+# 因此，确保 zookeeper.session.timeout.ms 参数足够长，以确保 Kafka Broker 与 ZooKeeper 之间的连接稳定并避免异常退出是很重要的。
+zookeeper.session.timeout.ms=60000
+
+
+############################# Group Coordinator Settings #############################
+
+# The following configuration specifies the time, in milliseconds, that the GroupCoordinator will delay the initial consumer rebalance.
+# The rebalance will be further delayed by the value of group.initial.rebalance.delay.ms as new members join the group, up to a maximum of max.poll.interval.ms.
+# The default value for this is 3 seconds.
+# We override this to 0 here as it makes for a better out-of-the-box experience for development and testing.
+# However, in production environments the default value of 3 seconds is more suitable as this will help to avoid unnecessary, and potentially expensive, rebalances during application startup.
+group.initial.rebalance.delay.ms=3
+
+```
+

大数据/zookeeper/zookeeper配置文件详解.md

@@ -0,0 +1,41 @@
+```properties
+# The number of milliseconds of each tick
+# 在ZooKeeper中，tickTime是指ZooKeeper服务器之间通信的基本时间单位，通常为毫秒。ZooKeeper使用tickTime来进行时间同步和心跳检测，用于保证ZooKeeper集群中所有服务器的时钟保持同步。tickTime的值越小，ZooKeeper服务器之间进行心跳检测的时间就越短，集群的同步性就越好，但同时也会增加网络通信的负载。因此，在设置tickTime的值时，需要根据具体的场景和需求进行权衡和调整。
+tickTime=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=/opt/modules/zookeeper/conf/data
+# the port at which the clients will connect
+clientPort=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
+
+## Metrics Providers
+#
+# https://prometheus.io Metrics Exporter
+#metricsProvider.className=org.apache.zookeeper.metrics.prometheus.PrometheusMetricsProvider
+#metricsProvider.httpPort=7000
+#metricsProvider.exportJvmInfo=true
+dataLogDir=/opt/modules/zookeeper/conf/logs
+
+```
+

面经/2023年暑期实习/阿里一面.md

@@ -0,0 +1,23 @@
+# 2023/4/4 电话面试 -- 35分钟
+
+1. kafka消费乱序如何解决
+2. kafka消费乱序的原因
+3. kafka消息丢失问题
+4. 如何保证消息不能丢失
+5. 消息如何保证幂等性，全链路的幂等性
+6. mysql和redis锁的优化，性能的提升
+7. redis分布式锁的问题 -- 故障转移，锁的丢失
+8. hashmap的get和put函数
+9. put函数的细节
+10. hashmap的数组长度为什么是16？ ---  扩容方便，只有一半的节点需要移位
+11. 链表什么时候为转换为红黑树
+12. 链表为什么不直接转换为红黑树？为什么选择扩容就可以解决冲突？ --- 不会
+13. jvm判断对象是否死亡
+14. 哪些对象可以作为 GC Roots 呢？
+15. 年轻代回收和老年代回收的差异  
+16. 为什么年轻代使用标记复制算法    -- 不会
+17. 如何理解微服务 -- 不会
+18. mysql如何提升查询性能
+19. 加入索引的讲究 --- 数据检索的条件字段，聚合函数的聚合字段，排序字段，防止回表，关键字段
+20. 联合索引a,b的顺序
+