springboot+zookeeper實現分布式鎖的示例代碼

更新時間：2022年03月21日 16:11:23 作者：冬雪是你

本文主要介紹了springboot+zookeeper實現分布式鎖的示例代碼，文中根據實例編碼詳細介紹的十分詳盡，具有一定的參考價值，感興趣的小伙伴們可以參考一下

依賴

<dependency>
   <groupId>org.apache.zookeeper</groupId>
   <artifactId>zookeeper</artifactId>
   <version>3.4.10</version>
</dependency>
<!-- zookeeper 客戶端 -->
<dependency>
   <groupId>org.apache.curator</groupId>
   <artifactId>curator-framework</artifactId>
   <version>2.12.0</version>
</dependency>
<dependency>
   <groupId>org.apache.curator</groupId>
   <artifactId>curator-recipes</artifactId>
   <version>2.12.0</version>
</dependency>
<!-- lombok -->
<dependency>
   <groupId>org.projectlombok</groupId>
   <artifactId>lombok</artifactId>
   <version>1.18.16</version>
   <scope>provided</scope>
</dependency>

本地封裝

這個工具類主要封裝CuratorFramework這個client(連接Zookeeper)

@Slf4j
public class CuratorClientUtil {
    private String zookeeperServer;

    @Getter
    private CuratorFramework client;

    public CuratorClientUtil(String zookeeperServer) {
        this.zookeeperServer = zookeeperServer;
    }

  	// 創(chuàng)建CuratorFrameworkFactory并且啟動
    public void init() {
       // 重試策略,等待1s,最大重試3次
        RetryPolicy retryPolicy = new ExponentialBackoffRetry(1000,3);
        this.client = CuratorFrameworkFactory.builder()
                .connectString(zookeeperServer)
                .sessionTimeoutMs(5000)
                .connectionTimeoutMs(5000)
                .retryPolicy(retryPolicy)
                .build();
        this.client.start();
    }

   // 容器關閉,CuratorFrameworkFactory關閉
    public void destroy() {
        try {
            if (Objects.nonNull(getClient())) {
                getClient().close();
            }
        } catch (Exception e) {
            log.info("CuratorFramework close error=>{}", e.getMessage());
        }
    }
}

配置

@Configuration
public class CuratorConfigration {
    @Value("${zookeeper.server}")
    private String zookeeperServer;
    // 注入時,指定initMethod和destroyMethod
    @Bean(initMethod = "init", destroyMethod = "destroy")
    public CuratorClientUtil curatorClientUtil() {
        CuratorClientUtil clientUtil = new CuratorClientUtil(zookeeperServer);
        return clientUtil;
    }
}

測試代碼

模擬不同客戶端的請求

@Slf4j
@RestController
@RequestMapping("/test")
public class TestController {
    // 注入client工具類
    @Autowired
    private CuratorClientUtil curatorClientUtil;
    // 在zookeeper的/rootLock節(jié)點下創(chuàng)建鎖對應的臨時有序節(jié)點
    private String rootLock = "/rootLock";

    @GetMapping("/testLock")
    public Object testLock() throws Exception {
        // 獲取當前線程的名字，方便觀察那些線程在獲取鎖
        String threadName = Thread.currentThread().getName();
        InterProcessMutex mutex = new InterProcessMutex(curatorClientUtil.getClient(), rootLock);
        try {
            log.info("{}---獲取鎖start", threadName);
            // 嘗試獲取鎖，最長等待3s，超時放棄獲取
            boolean lockFlag = mutex.acquire(3000, TimeUnit.SECONDS);
            // 獲取鎖成功，進行業(yè)務處理
            if (lockFlag) {
                log.info("{}---獲取鎖success", threadName);
                // 模擬業(yè)務處理，時間為3s
                Thread.sleep(3000);
            } else {
                log.info("{}---獲取鎖fail", threadName);
            }
        } catch (Exception e) {
            log.info("{}---獲取鎖異常", threadName);
        } finally {
            // 業(yè)務處理完成，釋放鎖，喚醒比當前線程創(chuàng)建的節(jié)點序號大(最靠近)的線程獲取鎖
            mutex.release();
            log.info("{}---鎖release", threadName);
        }
        return "線程:" + threadName + "執(zhí)行完成";
    }
}

JMeter測試

我們使用JMeter模擬100個客戶端同時并發(fā)的訪問 localhost:8081/test/testLock，相當于100個客戶端爭搶分布式鎖，結果如圖右上角所示，100個請求花了5分6s，每個線程獲取到鎖后業(yè)務處理3s，100個線程理想時間為300s(Thread.sleep(3000))，所以運行時間符合。

[外鏈圖片轉存失敗,源站可能有防盜鏈機制,建議將圖片保存下來直接上傳(img-AiBDB0tM-1647660941538)(/Users/maxuedong/Library/Containers/com.tencent.qq/Data/Library/Application Support/QQ/Users/2860850965/QQ/Temp.db/63AC764F-1C38-4422-9A01-776403B51E5F.png)]