FastDFS蛋疼的集群和负载均衡(二)之tracker和stroage集群配置

最新推荐文章于 2024-04-30 17:15:06 发布
最新推荐文章于 2024-04-30 17:15:06 发布
阅读量314 收藏
点赞数
文章标签： 网络 运维
原文链接：https://juejin.im/post/5b27758a51882574af280b39
版权

###Interesting things

接着上一篇来写。

###What did you do today

With RHEL 7 / CentOS 7, firewalld was introduced to manage iptables. IMHO, firewalld is more suited for workstations than for server environments. It is possible to go back to a more classic iptables setup. First, stop and mask the firewalld service

  • 上一篇我们发现在/etc/sysconfig/下没有看到iptables，并且我们使用iptbales -P INPUT ACCESPT service iptables save命令写入防火墙策略的时候，抛出了"The service command supports only basic LSB actions (start, stop, restart, try-restart, reload, force-reload, status). For other actions, please try to use systemctl."异常，而且用service iptables status查看防火墙的状态也提示"Unit iptables.service could not found"

  • 查阅资料发现，CentOS 7引入(默认firewalld)了firewalld来管理iptables，如果我们想回到iptables设置，首先我们需要停止firewalld，命令: systemctl stop firewalld, 然后屏蔽firewalld, systemctl mask firewalld，它是创建一个/etc/systemd/system/firewalld.service到 /dev/null的符号链接去屏蔽firewalld的服务。

  • 安装iptables-services, yum install iptables-services

  • 启用iptables, systemctl enable iptables.

  • 启动iptables, systemctl start iptables,然后我们进入/etc/sysconfig/，发现iptables文件出现了

  • 我们进入/etc/sysconfig/iptables，添加访问22122端口的策略，直接复制上面就行了，改个端口号就ok了。 -A INPUT -p tcp -m state --state NEW -m tcp --dport 22122 -j ACCEPT

  • 让防火墙策略生效。service iptables save.

  • 重启防火墙，二种方式都可以。systemctl restart iptables service iptables restart

  • 通过/etc/init.d/fdfs_trackerd start来启动，然后用ps -ef|grep fdfs来查看tracker是否正常启动。

  • 还记得我们之前配置tracker.conf的时候把里面的base_path改成了/fastdfs/tracker，我们进入/fastdfs/tracker里面发现多了data，logs两个文件夹

  • 我们打开logs文件夹会发现trackerd.log

[2017-12-27 10:38:41] INFO - FastDFS v5.05, base_path=/fastdfs/tracker, run_by_group=, run_by_user=, connect_timeout=30s, network_timeout=60s, port=22122, bind_addr=, max_connections=256, accept_threads=1, work_threads=4, store_lookup=0, store_group=, store_server=0, store_path=0, reserved_storage_space=10.00%, download_server=0, allow_ip_count=-1, sync_log_buff_interval=10s, check_active_interval=120s, thread_stack_size=64 KB, storage_ip_changed_auto_adjust=1, storage_sync_file_max_delay=86400s, storage_sync_file_max_time=300s, use_trunk_file=0, slot_min_size=256, slot_max_size=16 MB, trunk_file_size=64 MB, trunk_create_file_advance=0, trunk_create_file_time_base=02:00, trunk_create_file_interval=86400, trunk_create_file_space_threshold=20 GB, trunk_init_check_occupying=0, trunk_init_reload_from_binlog=0, trunk_compress_binlog_min_interval=0, use_storage_id=0, id_type_in_filename=ip, storage_id_count=0, rotate_error_log=0, error_log_rotate_time=00:00, rotate_error_log_size=0, log_file_keep_days=0, store_slave_file_use_link=0, use_connection_pool=0, g_connection_pool_max_idle_time=3600s

  • 打开data文件夹，会发现fdfs_trackerd.pid(里面是3185，进程标识符)和storage_changelog.dat(里面为空)。

  • 接下来我们需要配置storage，将group1(192.168.12.33, 192.168.12.44)和group2(192.18.12.55, 192.168.12.66)作为我们的存储节点。

  • 拷贝storage.conf.sample,并且重命名为storage.conf。

  • 给192.168.12.44、192.168.12.55、192.168.12.66都拷贝一份storage.conf

  • 更改group1的storage.conf，把base_path改成/fastdfs/storage

  • 我们可以storage server的端口号是23000，group_name修改成自己所在的组，192.168.12.33和192.168.12.44对应的group_name=group1, 192.168.12.55和192.168.12.66对应的group_name=group2。

  • 默认storage存储路径的个数是1， 我们把storage_path0修改成/fastdfs/storage

  • 配置tracker_server=192.168.12.11:22122、tracker_server=192.168.12.22:2212 所配置的地址也就是tracker1和tracker2地址。

  • 我们可以到storage的web端口是8888。

  • 然后把配置完的stroage.conf拷贝给192.168.12.44、192.168.12.55、192.168.12.66。192.168.12.44不用做任何修改，192.168.12.55和192.168.12.66只用把group_name修改为group2即可。

  • 创建/fastdfs/storage。mkdir -p /fastdfs/storage

  • 同样的往iptables里面添加端口23000。 -A INPUT -p tcp -m state --state NEW -m tcp --dport 23000 -j ACCEPT

  • 我们在192.168.12.33启动storage。

  • 我们进入/fastdfs/storage,会发现也生成了logs和data文件夹。

  • 我们先把所有的tracker1和tracker2， group1和group2都关闭。然后我先启动tracker2(192.168.12.22)，tracker2会去尝试连接tracker1，tracker1肯定没有开启，所以会连接失败，tracker2会成为tracker leader。

  • 开启tracker1，tracker2此时已经是leader了。所以会打印出"the tracker leader 192.168.12.22:22122"

  • 开启192.168.12.33，发现成功连接tracker1，tracker2。tracker2是tracker leader。而且成功连接同一个group下的192.168.12.44.

  • 开启192.168.12.44，成功连接tracker1，tracker2，192.168.12.33。

  • 开启192.168.12.55 和 192.168.12.66，彼此相互连接成功，连接成功tracker1，tracker2.

  • tracker和storage集群搭建完毕了，我们可以测试一下tracker的高可用性。tracker leader一开始是tracker2(192.168.12.22)，如果我们把tracker2关闭，tracker1（192.168.12.11）就会成为我们的tracker leader。

  • 我们随便挑一个group1和group2所属的storage，也发现tracker leader切换到了tracker1，简直美滋滋。

  • 接着我再启动tracker2，发现依然悍动不了tracker2身为leader的宝座。

  • 所有的tracker和storage节点都启动成功后，我们可以在任意的一个storage查看storage集群信息。我这里就选192.168.12.33把，命令: /usr/bin/fdfs_monitor /etc/fdfs/storage.conf

 [root@localhost logs]# /usr/bin/fdfs_monitor /etc/fdfs/storage.conf
[2017-12-27 16:26:30] DEBUG - base_path=/fastdfs/storage, connect_timeout=30, network_timeout=60, tracker_server_count=2, anti_steal_token=0, anti_steal_secret_key length=0, use_connection_pool=0, g_connection_pool_max_idle_time=3600s, use_storage_id=0, storage server id count: 0

server_count=2, server_index=0

tracker server is 192.168.12.11:22122

group count: 2

Group 1:
group name = group1
disk total space = 18414 MB
disk free space = 17044 MB
trunk free space = 0 MB
storage server count = 2
active server count = 2
storage server port = 23000
storage HTTP port = 8888
store path count = 1
subdir count per path = 256
current write server index = 0
current trunk file id = 0

	Storage 1:
		id = 192.168.12.33
		ip_addr = 192.168.12.33 (localhost.localdomain)  ACTIVE
		http domain = 
		version = 5.05
		join time = 2017-12-27 11:52:50
		up time = 2017-12-27 16:01:59
		total storage = 18414 MB
		free storage = 17151 MB
		upload priority = 10
		store_path_count = 1
		subdir_count_per_path = 256
		storage_port = 23000
		storage_http_port = 8888
		current_write_path = 0
		source storage id = 
		if_trunk_server = 0
		connection.alloc_count = 256
		connection.current_count = 1
		connection.max_count = 1
		total_upload_count = 0
		success_upload_count = 0
		total_append_count = 0
		success_append_count = 0
		total_modify_count = 0
		success_modify_count = 0
		total_truncate_count = 0
		success_truncate_count = 0
		total_set_meta_count = 0
		success_set_meta_count = 0
		total_delete_count = 0
		success_delete_count = 0
		total_download_count = 0
		success_download_count = 0
		total_get_meta_count = 0
		success_get_meta_count = 0
		total_create_link_count = 0
		success_create_link_count = 0
		total_delete_link_count = 0
		success_delete_link_count = 0
		total_upload_bytes = 0
		success_upload_bytes = 0
		total_append_bytes = 0
		success_append_bytes = 0
		total_modify_bytes = 0
		success_modify_bytes = 0
		stotal_download_bytes = 0
		success_download_bytes = 0
		total_sync_in_bytes = 0
		success_sync_in_bytes = 0
		total_sync_out_bytes = 0
		success_sync_out_bytes = 0
		total_file_open_count = 0
		success_file_open_count = 0
		total_file_read_count = 0
		success_file_read_count = 0
		total_file_write_count = 0
		success_file_write_count = 0
		last_heart_beat_time = 2017-12-27 16:25:58
		last_source_update = 1970-01-01 08:00:00
		last_sync_update = 1970-01-01 08:00:00
		last_synced_timestamp = 1970-01-01 08:00:00 
	Storage 2:
		id = 192.168.12.44
		ip_addr = 192.168.12.44  ACTIVE
		http domain = 
		version = 5.05
		join time = 2017-12-27 13:30:50
		up time = 2017-12-27 15:53:28
		total storage = 18414 MB
		free storage = 17044 MB
		upload priority = 10
		store_path_count = 1
		subdir_count_per_path = 256
		storage_port = 23000
		storage_http_port = 8888
		current_write_path = 0
		source storage id = 
		if_trunk_server = 0
		connection.alloc_count = 256
		connection.current_count = 1
		connection.max_count = 1
		total_upload_count = 0
		success_upload_count = 0
		total_append_count = 0
		success_append_count = 0
		total_modify_count = 0
		success_modify_count = 0
		total_truncate_count = 0
		success_truncate_count = 0
		total_set_meta_count = 0
		success_set_meta_count = 0
		total_delete_count = 0
		success_delete_count = 0
		total_download_count = 0
		success_download_count = 0
		total_get_meta_count = 0
		success_get_meta_count = 0
		total_create_link_count = 0
		success_create_link_count = 0
		total_delete_link_count = 0
		success_delete_link_count = 0
		total_upload_bytes = 0
		success_upload_bytes = 0
		total_append_bytes = 0
		success_append_bytes = 0
		total_modify_bytes = 0
		success_modify_bytes = 0
		stotal_download_bytes = 0
		success_download_bytes = 0
		total_sync_in_bytes = 0
		success_sync_in_bytes = 0
		total_sync_out_bytes = 0
		success_sync_out_bytes = 0
		total_file_open_count = 0
		success_file_open_count = 0
		total_file_read_count = 0
		success_file_read_count = 0
		total_file_write_count = 0
		success_file_write_count = 0
		last_heart_beat_time = 2017-12-27 16:26:27
		last_source_update = 1970-01-01 08:00:00
		last_sync_update = 1970-01-01 08:00:00
		last_synced_timestamp = 1970-01-01 08:00:00 

Group 2:
group name = group2
disk total space = 17394 MB
disk free space = 16128 MB
trunk free space = 0 MB
storage server count = 2
active server count = 2
storage server port = 23000
storage HTTP port = 8888
store path count = 1
subdir count per path = 256
current write server index = 0
current trunk file id = 0

	Storage 1:
		id = 192.168.12.55
		ip_addr = 192.168.12.55  ACTIVE
		http domain = 
		version = 5.05
		join time = 2017-12-27 13:35:06
		up time = 2017-12-27 15:56:07
		total storage = 17394 MB
		free storage = 16128 MB
		upload priority = 10
		store_path_count = 1
		subdir_count_per_path = 256
		storage_port = 23000
		storage_http_port = 8888
		current_write_path = 0
		source storage id = 
		if_trunk_server = 0
		connection.alloc_count = 256
		connection.current_count = 1
		connection.max_count = 1
		total_upload_count = 0
		success_upload_count = 0
		total_append_count = 0
		success_append_count = 0
		total_modify_count = 0
		success_modify_count = 0
		total_truncate_count = 0
		success_truncate_count = 0
		total_set_meta_count = 0
		success_set_meta_count = 0
		total_delete_count = 0
		success_delete_count = 0
		total_download_count = 0
		success_download_count = 0
		total_get_meta_count = 0
		success_get_meta_count = 0
		total_create_link_count = 0
		success_create_link_count = 0
		total_delete_link_count = 0
		success_delete_link_count = 0
		total_upload_bytes = 0
		success_upload_bytes = 0
		total_append_bytes = 0
		success_append_bytes = 0
		total_modify_bytes = 0
		success_modify_bytes = 0
		stotal_download_bytes = 0
		success_download_bytes = 0
		total_sync_in_bytes = 0
		success_sync_in_bytes = 0
		total_sync_out_bytes = 0
		success_sync_out_bytes = 0
		total_file_open_count = 0
		success_file_open_count = 0
		total_file_read_count = 0
		success_file_read_count = 0
		total_file_write_count = 0
		success_file_write_count = 0
		last_heart_beat_time = 2017-12-27 16:26:07
		last_source_update = 1970-01-01 08:00:00
		last_sync_update = 1970-01-01 08:00:00
		last_synced_timestamp = 1970-01-01 08:00:00 
	Storage 2:
		id = 192.168.12.66
		ip_addr = 192.168.12.66  ACTIVE
		http domain = 
		version = 5.05
		join time = 2017-12-27 13:36:48
		up time = 2017-12-27 15:56:54
		total storage = 18414 MB
		free storage = 17044 MB
		upload priority = 10
		store_path_count = 1
		subdir_count_per_path = 256
		storage_port = 23000
		storage_http_port = 8888
		current_write_path = 0
		source storage id = 192.168.12.55
		if_trunk_server = 0
		connection.alloc_count = 256
		connection.current_count = 1
		connection.max_count = 1
		total_upload_count = 0
		success_upload_count = 0
		total_append_count = 0
		success_append_count = 0
		total_modify_count = 0
		success_modify_count = 0
		total_truncate_count = 0
		success_truncate_count = 0
		total_set_meta_count = 0
		success_set_meta_count = 0
		total_delete_count = 0
		success_delete_count = 0
		total_download_count = 0
		success_download_count = 0
		total_get_meta_count = 0
		success_get_meta_count = 0
		total_create_link_count = 0
		success_create_link_count = 0
		total_delete_link_count = 0
		success_delete_link_count = 0
		total_upload_bytes = 0
		success_upload_bytes = 0
		total_append_bytes = 0
		success_append_bytes = 0
		total_modify_bytes = 0
		success_modify_bytes = 0
		stotal_download_bytes = 0
		success_download_bytes = 0
		total_sync_in_bytes = 0
		success_sync_in_bytes = 0
		total_sync_out_bytes = 0
		success_sync_out_bytes = 0
		total_file_open_count = 0
		success_file_open_count = 0
		total_file_read_count = 0
		success_file_read_count = 0
		total_file_write_count = 0
		success_file_write_count = 0
		last_heart_beat_time = 2017-12-27 16:26:24
		last_source_update = 1970-01-01 08:00:00
		last_sync_update = 1970-01-01 08:00:00
		last_synced_timestamp = 1970-01-01 08:00:00 
[root@localhost logs]# 
复制代码

  • 输出的结果和我们预想的storage集群是一样一样的，tracker_server 有2个， group有2个。group1的ip有192.168.12.33和192.168.12.44，group2的ip有192.168.12.55和192.168.12.66.

  • 使用cd /usr/bin && ls |grep fdfs来查看fdfs所有的命令。

###Warning

请看下一篇。

weixin_34336292
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
高可用之FastDFS集群的安装、配置、使用.docx
11-07
高可用之FastDFS集群的安装、配置、使用
docker安装fastfds，并配置多组
qq_35440570的博客
06-17 1195
前言：这玩意整了大半天，网上的教程全特么的cv或者寥寥几句配置，太坑，现在整理下过程方便以后需要的时候复用 第一步docker拉取镜像 第二步创建tracker容器 docker run -id --name tracker --restart=always --net host -v /etc/localtime:/etc/localtime -v /data/tracker:/fastdfs/tracker/data delron/fastdfs tracker 第三.....
分布式文件系统 FastDFS 5.0.5 & Linux CentOS 7 安装配置
whs99的博客
10-26 553
FastDFS 分布式文件系统集群与应用
FastDFS学习笔记（二）FastDFS安装（单机模式）
11-05 634
1、安装文件下载 作者的GitHub地址：https://github.com/happyfish100 fastdfs-5.11.zip libfastcommon-master.zip 把下载的文件复制到centOS上，我的存放目录是：/usr/local/fastdfs 先安装类库 一定要先安装，否则后面或报错 yum -y install zlib zlib-de...
fastdfs 多组_FastDFS 一个tracker配置多个Storage Group
weixin_30453651的博客
12-29 3974
一个tracker配置多个Storage Group步骤如下：1、修改相应storage的storage_group2.conf配置文件，以下三个参数需注意：group_name=group2port=23001base_path=/data/fastdfs_group2store_path0=/data/fastdfs_group22、修改storage的mod_fastdfs.confgrou...
fastdfs 原理与过程
热门推荐
FREEDOM
07-08 5万+
前言： 每次上传文件后都会返回一个地址，用户需要自己保存此地址。 为了支持大容量，存储节点（服务器）采用了分卷（或分组）的组织方式。存储系统由一个或多个卷组成，卷与卷之间的文件是相互独立的，所有卷的文件容量累加就是整个存储系统中的文件容量。一个卷可以由一台或多台存储服务器组成，一个卷下的存储服务器中的文件都是相同的，卷中的多台存储服务器起到了冗余备份和负载均衡的作用。
转载：FastDFS的配置、部署与API使用解读（6）FastDFS配置详解之Storage配置
leonidasFlames的专栏
12-07 829
本文转载自：诗商·柳惊鸿CSDN博客，链接为：http://blog.csdn.net/poechant/article/details/7213536 转载目的仅仅为方便博主自己学习。 1 基本配置 disabled #func：该配置文件是否生效 #valu： ## true：无效 ## false：生效 disabled=false group_name #func；本st
FastDFS的配置、部署与API使用解读（5）FastDFS配置详解之Tracker配置
11-21 113
《Poechant的FastDFS的配置、部署与API使用教程》 FastDFS的配置、部署与API使用解读——（1）入门使用教程 FastDFS的配置、部署与API使用解读——（2）Java API：根据InputStream、文件名、文件长度上传文件 FastDFS的配置、部署与API使用解读——（3）Java API：根据InputStream、文件名、文件长度，采用IO流...
Fastdfs数据迁移方案
无名小生
05-08 3503
方案背景描述 环境迁移，需要迁移旧环境的fastdfs集群的数据到新环境,由于之前数据迁移仅仅是针对mysql和mongodb,对fastdfs数据的迁移了解甚少，本文档主要是针对fastdfs数据迁移和恢复的几种方式以及具体操作流程做详细阐述。 方案实现的目标 实现fastdfs集群数据完整迁移，保证在新环境正常使用，以及保证fastdfs集群高可用。 方案说明 Fstdfs整体架构 Fastdfs数据迁移 数据迁移是指旧的fastdfs可以继续正常运行的情况下，..
Java高级架构之FastDFS分布式文件集群详解
08-26
主要介绍了Java高级架构之FastDFS分布式文件集群详解，小编觉得挺不错的，现在分享给大家，也给大家做个参考。一起跟随小编过来看看吧
FastDFS集群与Http访问部署详解配置文件.rar
03-20
《FastDFS集群与Http访问部署详解》博客附件。 博客地址：https://blog.csdn.net/Supreme_Sir/article/details/115033593
FastDFS安装和配置整合Nginx-1.13.3的方法
09-30
主要介绍了FastDFS安装和配置整合Nginx-1.13.3的方法,需要的朋友可以参考下
FastDFS集群的配置文件
05-29
FastDFS集群的配置文件，详情请参见博文：http://blog.csdn.net/l1028386804/article/details/72803681
FastDFS tracker leader机制介绍
Huazie
07-13 424
FastDFS tracker leader机制介绍
FastDFS文件上传原理和负载均衡方法
Lion_Long的博客
11-11 2772
文件上传原理：选择tracker server、选择存储的group及其负载均衡算法、选择storage server及其负载均衡算法、选择storage path及其负载均衡算法、生成Fileid、选择两级目录、生成文件名。以及下载文件逻辑
FastDFS中fdfs_trackerd和fdfs_storaged的启动、重启、终止命令
Shaun_X
03-29 1万+
我们要是使用终止命令或者使用 kill -9 fdfs进程id 来终结fdfs_storaged服务的，然后用上面的启动命令是启动不了的，因为log日志问题
fastdfs分布式服务器搭建(高可用集群)
zhangpan_soft的博客
07-27 1万+
这里在虚拟机上搭建的,真正服务器搭建同理,废话少说,开始正文 首先准备一台母机(192.168.150.10),此母机上不搭建东西,只是为了后续虚拟机的克隆,我的是centos7.x 准备基本环境 检查c/c++ 环境 yum -y install gcc gcc-c++ 检查zip/unzip yum -y install zip unzip 检查vim(因为fastdfs会用到vim,...
FR-TSN4206获得“时间敏感网络产业链名录计划”测试认证证书，TSN交换机助力智能工业发展
最新发布
fiberroad的博客
04-30 523
TSN技术，即时间敏感网络技术，已成为智能工业、自动驾驶等领域的核心。它通过时钟同步、数据调度等功能，确保低延迟、高可靠性的数据传输。为推动TSN技术在我国的发展，工业互联网产业联盟联合多家单位启动了“时间敏感网络产业链名录计划”。光路科技的FR-TSN4206交换机成功通过该计划认证
fastdfs集群管理
10-18
4. 负载均衡管理：FastDFS支持负载均衡功能，可以将文件上传和下载请求均衡地分配到不同的Storage服务器上，提高系统的性能和可扩展性。在FastDFS集群中，可以通过设置负载均衡策略来控制请求的分配方式。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值