一、链路聚合

1、什么是链路聚合?

网卡的链路聚合就是将多块网卡连接起来,当-块网卡损坏,网络依旧可以正常运行,可以有效的防止因为网卡损坏带来的损失,同时也可以提高网络访问速度。

2、链路聚合方式:

  • bond:最多可以添加两块网卡
  • team:最多可以添加八块网卡
  • bond的常用的2种模式:
    • bond0(balance-rr)

      • bond0用于负载轮询(2个网单独都是100MB, 聚合为1个网络传输带宽为200MB)
    • bond1(active-backup)

      • bond1用于高可用,其中一条线若断线,其他线路将会自动备援
  • team可以实现以下模式的聚合链路:

    • broadcast ——广播容错
    • roundrobin ——负载轮询
    • activebackup ——主备(必考)
    • loadbalance ——负载均衡
    • lacp ——需要交换机支持lacp协议

3、bond的七种模式

这七种模式分别是:

802.3ad     balance-alb     balance-tlb     broadcast      active-backup       balance-rr      balance-xor

  • mode=0    round-robin轮询策略(Round-robin policy)
  • mode=1    active-backup主备策略(Active-backup policy)
  • mode=2    load balancing (xor)异或策略(XOR policy)
  • mode=3    fault-tolerance (broadcast)广播策略(Broadcast policy)
  • mode=4    lacp IEEE 802.3ad 动态链路聚合(IEEE 802.3ad Dynamic link aggregation)
  • mode=5    transmit load balancing适配器传输负载均衡(Adaptive transmit load balancing)
  • mode=6    adaptive load balancing适配器负载均衡(Adaptive load balancing)

二、链路聚合配置

1、查看所以网卡设备信息

[root@localhost ~]# nmcli de
DEVICE TYPE STATE CONNECTION
eth0 ethernet connected eth0
eth1 ethernet disconnected --
eth2 ethernet disconnected --
lo loopback unmanaged --
//绑定物理网卡,事先必须断开物理网卡的连接

2、网卡链路聚合方式一:bond —— blance-rr模式

  • 第一步:创建bond0

[root@localhost ~]# nmcli connection add type bond con-name bond0 ifname bond0 mode balance-rr ipv4.method manual ipv4.addresses 192.168.174.150/24 ipv4.gateway 192.168.174.2 ipv4.dns 8.8.8.8
Connection 'bond0' (b038c7fb-e1f8-4436-b6d6-8ab6f6177cd4) successfully added.
[root@localhost ~]# ip addr show bond0
5: bond0: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 6a:82:e0:bc:f4:e9 brd ff:ff:ff:ff:ff:ff
inet 192.168.174.150/24 brd 192.168.174.255 scope global noprefixroute bond0
valid_lft forever preferred_lft forever //查看bond0网络接口状态
[root@localhost ~]# nmcli connection show
NAME UUID TYPE DEVICE
bond0 b038c7fb-e1f8-4436-b6d6-8ab6f6177cd4 bond bond0
eth0 f7036e05-ee1b-4ceb-94cc-0845ace9f4c1 ethernet eth0
Wired connection 1 a761ff76-b76c-307e-939b-cbe2ecc41bc7 ethernet --
Wired connection 2 f70e7fbb-52d0-3cb3-bc6c-7e937553ac06 ethernet --
  • 第二步:添加两块物理网卡连接到bond0

[root@localhost ~]# nmcli connection add type bond-slave con-name slave1 ifname eth1 master bond0
Connection 'slave1' (a188a30f-4aea-43ff-82b2-b9cd6ebf076a) successfully added.
[root@localhost ~]# nmcli connection add type bond-slave con-name slave2 ifname eth2 master bond0
Connection 'slave2' (38072c0c-ca0b-4cc8-b762-15d277b74f26) successfully added. //查看bond-slave查看网络接口状态
[root@localhost ~]# nmcli connection
NAME UUID TYPE DEVICE
bond0 b038c7fb-e1f8-4436-b6d6-8ab6f6177cd4 bond bond0
eth0 f7036e05-ee1b-4ceb-94cc-0845ace9f4c1 ethernet eth0
slave1 a188a30f-4aea-43ff-82b2-b9cd6ebf076a ethernet --
slave2 38072c0c-ca0b-4cc8-b762-15d277b74f26 ethernet --
Wired connection 1 a761ff76-b76c-307e-939b-cbe2ecc41bc7 ethernet --
Wired connection 2 f70e7fbb-52d0-3cb3-bc6c-7e937553ac06 ethernet --   
  • 第四步:激活网卡设备

[root@localhost ~]# nmcli connection up slave1
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/6)
[root@localhost ~]# nmcli connection up slave2
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/7)  
  • 第五步:查看bond的配置信息

[root@localhost ~]# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: load balancing (round-robin)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0 Slave Interface: eth1
MII Status: up
Speed: 10000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:0c:29:fa:c0:fa
Slave queue ID: 0 Slave Interface: eth2
MII Status: up
Speed: 10000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:0c:29:fa:c0:04
Slave queue ID: 0
  • 第六步:关闭eth0,检测bond0是否正常

[root@localhost ~]# nmcli device disconnect eth0
  • 第七步:查看网卡信息

[root@localhost ~]# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:0c:29:fa:c0:f0 brd ff:ff:ff:ff:ff:ff
inet 192.168.174.139/24 brd 192.168.174.255 scope global noprefixroute eth0
valid_lft forever preferred_lft forever
inet6 fe80::a101:bf00:d10e:9788/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
link/ether 00:0c:29:fa:c0:fa brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
link/ether 00:0c:29:fa:c0:fa brd ff:ff:ff:ff:ff:ff
5: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:0c:29:fa:c0:fa brd ff:ff:ff:ff:ff:ff
inet 192.168.174.140/24 brd 192.168.174.255 scope global dynamic noprefixroute bond0
valid_lft 1542sec preferred_lft 1542sec
inet 192.168.174.150/24 brd 192.168.174.255 scope global secondary noprefixroute bond0
valid_lft forever preferred_lft forever
inet6 fe80::97b0:2962:6eab:49fc/64 scope link noprefixroute
valid_lft forever preferred_lft forever

3、网卡链路聚合方式一:bond —— activebackup模式

  • 第一步:创建bond1

[root@localhost ~]# nmcli connection add type bond con-name bond1 ifname bond1 mode active-backup ipv4.method manual ipv4.addresses 192.168.174.160/24 ipv4.gateway 192.168.174.2 ipv4.dns 8.8.8.8
Connection 'bond1' (79fb7f29-4da5-46eb-8915-0d14b20d7e16) successfully added.
[root@localhost ~]# ip addr show bond1
6: bond1: <NO-CARRIER,BROADCAST,MULTICAST,MASTER,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 3e:5e:4f:a1:31:cd brd ff:ff:ff:ff:ff:ff
inet 192.168.174.160/24 brd 192.168.174.255 scope global noprefixroute bond1
valid_lft forever preferred_lft forever / /查看bond1网卡连接状态
[root@localhost ~]# nmcli connection show
NAME UUID TYPE DEVICE
eth0 f7036e05-ee1b-4ceb-94cc-0845ace9f4c1 ethernet eth0
bond1 79fb7f29-4da5-46eb-8915-0d14b20d7e16 bond bond1
Wired connection 1 a761ff76-b76c-307e-939b-cbe2ecc41bc7 ethernet --
Wired connection 2 f70e7fbb-52d0-3cb3-bc6c-7e937553ac06 ethernet --
  • 第二步:添加物理网卡连接到bond1 

[root@localhost ~]# nmcli connection add type bond-slave con-name slave1 ifname eth1 master bond1
Connection 'slave1' (fdb0b4af-604c-4a56-b3ba-0c72d7172807) successfully added.
[root@localhost ~]# nmcli connection add type bond-slave con-name slave2 ifname eth2 master bond1
Connection 'slave2' (80abf4ac-348a-4f8a-8df8-4f1dc45db4c1) successfully added.
  • 第三步:查看bond的配置信息

[root@localhost ~]# cat /proc/net/bonding/bond1
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth1
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0 Slave Interface: eth1
MII Status: up
Speed: 10000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:0c:29:fa:c0:fa
Slave queue ID: 0 Slave Interface: eth2
MII Status: up
Speed: 10000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:0c:29:fa:c0:04
Slave queue ID: 0
  • 测试

 //停掉eth1,查看配置文件状态
[root@localhost ~]# nmcli device disconnect eth1
成功断开设备 "eth1"。
[root@localhost ~]# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth2
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0 Slave Interface: eth2
MII Status: up
Speed: 10000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:0c:29:cd:6a:2f
Slave queue ID: 0 //停掉eth2,查看配置文件状态
[root@localhost ~]# nmcli device connect eth1
成功用 "eth154935406-3bcd-4d24-b58c-4e9f86c2999b" 激活了设备 ""。
[root@localhost ~]# nmcli device disconnect eth2
成功断开设备 "eth2"。
[root@localhost ~]# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth1
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0 Slave Interface: eth1
MII Status: up
Speed: 10000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:0c:29:cd:6a:25
Slave queue ID: 0

4、网卡链路聚合方式二:team —— roundrobin模式

  • 第一步:查看网卡设备信息

[root@localhost ~]# nmcli device
DEVICE TYPE STATE CONNECTION
eth0 ethernet connected eth0
eth1 ethernet disconnected --
eth2 ethernet disconnected --
lo loopback unmanaged --
//创建之前,必须断开网卡的连接
  • 第二步:创建team0

[root@localhost ~]# nmcli connection add type team con-name team0 ifname team0 config '{"runner":{"name":"roundrobin"}}' ipv4.method manual ipv4.addresses 192.168.174.150/24 ipv4.gateway 192.168.174.2 ipv4.dns 8.8.8.8
Connection 'team0' (b2a9d127-0ef4-479a-89c0-77137db2d825) successfully added. //查看team0网卡设备的状态
[root@localhost ~]# nmcli device
DEVICE TYPE STATE CONNECTION
eth0 ethernet connected eth0
team0 team connected team0
eth1 ethernet disconnected --
eth2 ethernet disconnected --
lo loopback unmanaged --
  • 第三步:添加物理网卡连接到team0

[root@localhost ~]# nmcli connection add type team-slave con-name slave1 ifname eth1 master team0
Connection 'slave1' (e88752fb-bad8-4e30-8374-c087e34fc9b9) successfully added.
[root@localhost ~]# nmcli connection add type team-slave con-name slave2 ifname eth2 master team0
Connection 'slave2' (fe58bc8d-97e4-4390-8490-8d898fcb7c8b) successfully added.
  • 第三步:查看网卡连接信息

[root@localhost ~]# nmcli connection
NAME UUID TYPE DEVICE
eth0 f7036e05-ee1b-4ceb-94cc-0845ace9f4c1 ethernet eth0
team0 b2a9d127-0ef4-479a-89c0-77137db2d825 team team0
slave1 7b2d11d2-a939-4cb4-a751-73cfe52f6872 ethernet --
slave2 05a4815e-5a22-40ca-a917-ee25a6286c6e ethernet --
Wired connection 1 a761ff76-b76c-307e-939b-cbe2ecc41bc7 ethernet --
Wired connection 2 f70e7fbb-52d0-3cb3-bc6c-7e937553ac06 ethernet --
  • 第四步:激活所以网卡连接 

[root@localhost ~]# nmcli connection up slave1
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/13)
[root@localhost ~]# nmcli connection up slave2
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/14)
[root@localhost ~]# nmcli connection up team0
Connection successfully activated (master waiting for slaves) (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/15)  
  • 查看网卡IP信息

[root@localhost ~]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:0c:29:fa:c0:f0 brd ff:ff:ff:ff:ff:ff
inet 192.168.174.139/24 brd 192.168.174.255 scope global noprefixroute eth0
valid_lft forever preferred_lft forever
inet6 fe80::a101:bf00:d10e:9788/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master team0 state UP group default qlen 1000
link/ether 00:0c:29:fa:c0:fa brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master team0 state UP group default qlen 1000
link/ether 00:0c:29:fa:c0:fa brd ff:ff:ff:ff:ff:ff
10: team0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:0c:29:fa:c0:fa brd ff:ff:ff:ff:ff:ff
inet 192.168.174.150/24 brd 192.168.174.255 scope global noprefixroute team0
valid_lft forever preferred_lft forever
inet6 fe80::7277:ccf3:77f3:262f/64 scope link noprefixroute
valid_lft forever preferred_lft forever
  • 第五步:检测team0状态

[root@localhost ~]# teamdctl team0 state
setup:
runner: roundrobin
ports:
eth1
link watches:
link summary: up
instance[link_watch_0]:
name: ethtool
link: up
down count: 0
eth2
link watches:
link summary: up
instance[link_watch_0]:
name: ethtool
link: up
down count: 0

5、网卡链路聚合方式二:team —— activebackup模式

  • 第一步:创建team1

[root@localhost ~]# nmcli connection add type team con-name team1 ifname team1 config '{"runner":{"name":"activebackup"}}' ipv4.method manual ipv4.addresses 192.168.174.190/24 ipv4.gateway 192.168.174.2 ipv4.dns 8.8.8.8
Connection 'team1' (f315f9cb-8b13-4372-8163-ec41a30c44af) successfully added. //查看team1网卡状态
[root@localhost ~]# nmcli device
DEVICE TYPE STATE CONNECTION
eth0 ethernet connected eth0
team1 team connected team1
eth1 ethernet disconnected --
eth2 ethernet disconnected --
lo loopback unmanaged --
[root@localhost ~]# nmcli connection
NAME UUID TYPE DEVICE
eth0 f7036e05-ee1b-4ceb-94cc-0845ace9f4c1 ethernet eth0
team1 f315f9cb-8b13-4372-8163-ec41a30c44af team team1
Wired connection 1 a761ff76-b76c-307e-939b-cbe2ecc41bc7 ethernet --
Wired connection 2 f70e7fbb-52d0-3cb3-bc6c-7e937553ac06 ethernet --
  • 第二步:连接物理网卡到team1

[root@localhost ~]# nmcli connection add type team-slave con-name slave1 ifname eth1 master team1
Connection 'slave1' (063127d0-88d2-41bf-988c-9c79a31f9b32) successfully added.
[root@localhost ~]# nmcli connection add type team-slave con-name slave2 ifname eth2 master team1
Connection 'slave2' (ecc6d36f-5d92-44b7-979b-b835b8b7facc) successfully added.
  • 查看网卡设备信息

[root@localhost ~]# nmcli device
DEVICE TYPE STATE CONNECTION
eth0 ethernet connected eth0
team1 team connected team1
eth1 ethernet connected slave1
eth2 ethernet connected slave2
lo loopback unmanaged -- [root@localhost ~]# nmcli connection
NAME UUID TYPE DEVICE
eth0 f7036e05-ee1b-4ceb-94cc-0845ace9f4c1 ethernet eth0
team1 f315f9cb-8b13-4372-8163-ec41a30c44af team team1
slave1 063127d0-88d2-41bf-988c-9c79a31f9b32 ethernet eth1
slave2 ecc6d36f-5d92-44b7-979b-b835b8b7facc ethernet eth2
Wired connection 1 a761ff76-b76c-307e-939b-cbe2ecc41bc7 ethernet --
Wired connection 2 f70e7fbb-52d0-3cb3-bc6c-7e937553ac06 ethernet --   
  • 第六步:查看team1状态

[root@localhost ~]# teamdctl team1 state
setup:
runner: activebackup
ports:
eth1
link watches:
link summary: up
instance[link_watch_0]:
name: ethtool
link: up
down count: 0
eth2
link watches:
link summary: up
instance[link_watch_0]:
name: ethtool
link: up
down count: 0
runner:
active port: eth1

6、动态修改team模式  

  • 导出配置文件

[root@localhost ~]# teamdctl team1 config dump > /root/team.conf  (dump:下载)
[root@localhost ~]# ls
anaconda-ks.cfg team.conf
  • 修改team.conf里面的内容

[root@localhost ~]# vim team.conf
{
"device": "team1",
"mcast_rejoin": {
"count": 1
},
"notify_peers": {
"count": 1
},
"ports": {
"eth1": {
"link_watch": {
"name": "ethtool"
}
},
"eth2": {
"link_watch": {
"name": "ethtool"
}
}
},
"runner": {
"name": "roundrobin" //将acticebackup换成roundrobin
}
}
  • 以最新修改的配置选项修改team1属性

[root@localhost ~]# nmcli connection modify team1 team.config /root/team.conf
  • 重启team1网卡

[root@localhost ~]# nmcli connection down team1;nmcli connection up team1
Connection 'team1' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/21)
Connection successfully activated (master waiting for slaves) (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/24)
  • 查看team1配置信息

[root@localhost ~]# teamdctl team1 state
setup:
runner: roundrobin //改完后就回发生改变
ports:
eth1
link watches:
link summary: up
instance[link_watch_0]:
name: ethtool
link: up
down count: 0
eth2
link watches:
link summary: up
instance[link_watch_0]:
name: ethtool
link: up
down count: 0

Linux_网络进阶管理的更多相关文章

  1. Linux_网络基础管理

    一.网卡的命名 1.传统网卡命名 eth0.eth1.eth2.eth3......... wlan0.wlan1.waln2.wlan3......... 2.RHEL7命名机制 systemd对网 ...

  2. Liunx网络技术管理及进程管理

    Linux网络技术管理及进程管理(week2_day4)   OSI七层模型和TCP/IP四层模型 OSI七层模型:OSI(Open System Interconnection)开放系统互连参考模型 ...

  3. Linux网络属性管理

    Linux网络属性管理 局域网:以太网,令牌环网 Ethernet: CSMA/CD 冲突域 广播域 MAC:Media Access Control 48bits: 24bits: 24bits: ...

  4. 基于UML网络教学管理平台模型的搭建

    一.基本信息 标题:基于UML网络教学管理平台模型的搭建 时间:2013 出版源:网络安全技术与应用 领域分类:UML:网络教学管理平台:模型 二.研究背景 问题定义:网络教学管理平台模型的搭建 难点 ...

  5. Linux 网络属性管理

    Linux网络基础管理-1:IPv4 地址分类:  点分十进制:0.0.0.0-255.255.255.255  A类: 0 0000000 - 0 1111111: 1-127 网络数:126, 1 ...

  6. linux入门系列11--Centos7网络服务管理

    通过前面文章的学习已经掌握了Linux系统配置管理的知识,本文讲解Centos7网络配置知识. Linux要对外提供服务,需要保证网络通信正常,因此需要正确配置网络参数.本文将讲解如何使用Networ ...

  7. linux进阶之网络技术管理

    本节内容 1.      网络七层模型 物理层 数据链路层 网络层 传输层 会话层 表示层 应用层 2.  TCP/UDP (1)TCP面向连接,可靠传输,消耗系统资源比较多,传输速度较慢,但是数据传 ...

  8. Linux网络共享管理(ssh,nfs,samba)

    OpenSSH服务器: ssh协议:提供安全的ssh环境用于远程管理,默认端口:22: 服务名称:sshd openssh-server包的安装文件: 使用ssh客户端程序: 连接目标主机: ssh ...

  9. Linux网络技术管理及进程管理(week2_day4)--技术流ken

    OSI七层模型和TCP/IP四层模型 OSI七层模型:OSI(Open System Interconnection)开放系统互连参考模型是国际标准化组织(ISO)制定的一个用于计算机或通信系统间互联 ...

随机推荐

  1. [Fundamental of Power Electronics]-PART I-6.变换器电路-6.3 变压器隔离

    6.3 变压器隔离 在许多应用场合中,期望将变压器结合到开关变换器中,从而在变换器的输入输出之间形成直流隔离.例如,在离线(off-line)应用中(变换器输入连接到交流公用系统),根据监管部门要求, ...

  2. 201871010130-周学铭 实验二 个人项目—D{0-1}问题项目报告

    项目 内容 课程班级博客链接 18级卓越班 这个作业要求链接 实验二 软件工程个人项目 我的课程学习目标 掌握软件项目个人开发流程.掌握Github发布软件项目的操作方法. 这个作业在哪些方面帮助我实 ...

  3. 利用查询条件对象,在Asp.net Web API中实现对业务数据的分页查询处理

    在Asp.net Web API中,对业务数据的分页查询处理是一个非常常见的接口,我们需要在查询条件对象中,定义好相应业务的查询参数,排序信息,请求记录数和每页大小信息等内容,根据这些查询信息,我们在 ...

  4. 6. linux 专业词汇

    什么是交换分区? 交换分区是一个特殊的分区,他的作用相当于windows下的虚拟内存,这个分区的大小一般设置为物理内存的两倍. 什么是Grub? Grub是一个系统引导工具,通过它可以加载内核,从而引 ...

  5. The Blocks Problem UVA - 101

      Many areas of Computer Science use simple, abstract domains for both analytical and empirical stud ...

  6. k8s endpoints k8s未配置选择器的service

    service 其实是一个TCP/UDP 代理 不仅可以代理Pod也可以代理其他的非Pod资源,例如外网的数据库,或者其他的资源 创建未配置选择器的service, service 的对外端口是500 ...

  7. SpringCloud(四)GateWay网关

    GateWay网关 概述简介 Gateway是在 Spring生态系统之上构建的AP网关服务,基于 Spring5, Spring Boot2和 Project Reactor等技术. Gateway ...

  8. 077 Kuchiguse

    The Japanese language is notorious for its sentence ending particles. Personal preference of such pa ...

  9. 【MySQL】Mysql(InnoDB引擎) 索引的数据结构为什么选择B+Tree

    1.B+ Tree的层数较少 B类树的一个很鲜明的特点就是数的层数比较少,而每层的节点非常多,树的每个叶子节点到根节点的距离都是相同的: 2.   减少磁盘IO: 树的每一个节点都是一个数据也,这样每 ...

  10. 从苏宁电器到卡巴斯基(后传)第05篇:聊聊我对WannaCry产生的感慨

    这几天看到网上对WannaCry勒索病毒讨论得沸沸扬扬,不免有些感触. 其实该病毒的这次爆发,完全可以类比N年前"熊猫烧香"爆发的情况.也就是国内杀软纷纷歇菜,让本来就没什么技术含 ...