分布式协调服务-zookeeper应用-基于zookeeper api分布式锁（分布式九 一）

最新推荐文章于 2022-06-21 12:52:15 发布
最新推荐文章于 2022-06-21 12:52:15 发布
阅读量313 收藏
点赞数
分类专栏： 分布式
随意转载。
本文链接：https://blog.csdn.net/dengjili/article/details/86576595
版权

目录

为什么需要分布式锁

订单号的生产问题？所有需要引入第三者来协调产生订单的顺序，保证唯一性，即争夺共享资源，需要分布式锁
在这里插入图片描述

引入zookeeper中间件

利用zookeeper节点特效，有序性产生不会冲突的资源
在这里插入图片描述

实现逻辑设计

在这里插入图片描述

具体代码实现

maven项目引入
		<dependency>
			<groupId>org.apache.zookeeper</groupId>
			<artifactId>zookeeper</artifactId>
			<version>3.4.13</version>
		</dependency>
代码实现
public class DistributeLock {
	
	private static final String CONNECT_IP_PORT = "176.16.0.135:2181";
	private static final Logger logger = LoggerFactory.getLogger(DistributeLock.class);

	private ZooKeeper zooKeeper;
	private final int sessionTimeout = 5000;
	
	private final String ROOT_LOCKS = "/LOCKS";
	private final byte[] data = {1, 2, 3};
	private String lockId;
	
	private CountDownLatch lessNodeDeleteLatch = new CountDownLatch(1);
	
	public DistributeLock() {
		this.zooKeeper = getInstance();
	}
	
	// 【核心方法】：获取锁
	public boolean lock() {
		try {
			lockId = zooKeeper.create(ROOT_LOCKS + "/", data, ZooDefs.Ids.OPEN_ACL_UNSAFE, CreateMode.EPHEMERAL_SEQUENTIAL);
			logger.debug("2.{}:成功创建lock节点[{}], 开始竞争锁", Thread.currentThread().getName(), lockId);
			
			// 竞争共享锁
			List<String> childrens = zooKeeper.getChildren(ROOT_LOCKS, true);
			SortedSet<String> sortedSet = new TreeSet<>(childrens);
			
			// 当前LOCKS子节点最小节点
			String absolutePath = ROOT_LOCKS + "/" + sortedSet.first();
			if (lockId.equals(absolutePath)) {
				logger.debug("3.{}:成功获取锁，锁节点为：{}", Thread.currentThread().getName(), lockId);
				return true;
			}
			
			// 返回此 set 的部分视图，其元素严格小于 toElement。
			SortedSet<String> lessLockIdSet = sortedSet.headSet(lockId.substring(lockId.lastIndexOf("/") + 1));
			if (!lessLockIdSet.isEmpty()) {
				String last = lessLockIdSet.last();
				String lessAbsolutePath = ROOT_LOCKS + "/" + last;
				zooKeeper.exists(lessAbsolutePath, new LockWatcher(lessNodeDeleteLatch));
				logger.debug("4.{}:未获取锁，监听比当前锁更小的节点：{}", Thread.currentThread().getName(), lessAbsolutePath);
				
				lessNodeDeleteLatch.await(sessionTimeout, TimeUnit.MILLISECONDS);
				
				logger.debug("5.{}:成功获取锁，锁节点为：{}", Thread.currentThread().getName(), lockId);
			}
			
		} catch (KeeperException e) {
			e.printStackTrace();
		} catch (InterruptedException e) {
			e.printStackTrace();
		}
		
		return false;
	}
	
	// 【核心方法】：释放锁
	public boolean unlock() {
		logger.debug("6.{}:开始释放锁，锁节点为：{}", Thread.currentThread().getName(), lockId);
		try {
			zooKeeper.delete(lockId, -1);
			logger.debug("7.{}:释放锁成功，锁节点为：{}", Thread.currentThread().getName(), lockId);
		} catch (InterruptedException e) {
			e.printStackTrace();
		} catch (KeeperException e) {
			e.printStackTrace();
		}
		return false;
	}

	private ZooKeeper getInstance() {
		ZooKeeper zooKeeper = null;	
		CountDownLatch countDownLatch = new CountDownLatch(1);
		try {
			zooKeeper = new ZooKeeper(CONNECT_IP_PORT, sessionTimeout, new Watcher() {
				@Override
				public void process(WatchedEvent event) {
					logger.debug("连接zookeeper成功：{}", event.getState());
					countDownLatch.countDown();
				}
			});
			countDownLatch.await();
			logger.debug("1.创建zooKeeper对象成功：{}", zooKeeper.getState());
		} catch (IOException e) {
		} catch (InterruptedException e) {
		}
    	return zooKeeper;
	}
	
	public static void main(String[] args) {
		
		CountDownLatch runLatch = new CountDownLatch(10);
		for (int i = 0; i < 10 ; i++) {
			new Thread(()->{
				DistributeLock distributeLock = null;
				try {
					distributeLock = new DistributeLock();
					runLatch.countDown();
					// 所有进程都等着，都准备好了一起开始抢
					runLatch.await();
					
					distributeLock.lock();
					TimeUnit.MILLISECONDS.sleep(new Random().nextInt(500));
				} catch (Exception e) {
					e.printStackTrace();
				} finally {
					if (distributeLock != null) {
						distributeLock.unlock();
					}
				}
			}).start();;
		}
	}
}

删除监听事件

public class LockWatcher implements Watcher {
	
	private CountDownLatch latch;
	
	public LockWatcher(CountDownLatch latch) {
		this.latch = latch;
	}

	@Override
	public void process(WatchedEvent event) {
		if (event.getType() == EventType.NodeDeleted) {
			latch.countDown();
		}
	}
}
测试结果
连接zookeeper成功：SyncConnected
Session establishment complete on server 176.16.0.135/176.16.0.135:2181, sessionid = 0x1000002273d0003, negotiated timeout = 5000
连接zookeeper成功：SyncConnected
1.创建zooKeeper对象成功：CONNECTED
1.创建zooKeeper对象成功：CONNECTED
连接zookeeper成功：SyncConnected
1.创建zooKeeper对象成功：CONNECTED
Session establishment complete on server 176.16.0.135/176.16.0.135:2181, sessionid = 0x1000002273d0004, negotiated timeout = 5000
连接zookeeper成功：SyncConnected
1.创建zooKeeper对象成功：CONNECTED
Session establishment complete on server 176.16.0.135/176.16.0.135:2181, sessionid = 0x1000002273d0005, negotiated timeout = 5000
连接zookeeper成功：SyncConnected
1.创建zooKeeper对象成功：CONNECTED
Session establishment complete on server 176.16.0.135/176.16.0.135:2181, sessionid = 0x1000002273d0006, negotiated timeout = 5000
连接zookeeper成功：SyncConnected
1.创建zooKeeper对象成功：CONNECTED
Session establishment complete on server 176.16.0.135/176.16.0.135:2181, sessionid = 0x1000002273d0007, negotiated timeout = 5000
连接zookeeper成功：SyncConnected
1.创建zooKeeper对象成功：CONNECTED
Session establishment complete on server 176.16.0.135/176.16.0.135:2181, sessionid = 0x1000002273d0008, negotiated timeout = 5000
连接zookeeper成功：SyncConnected
1.创建zooKeeper对象成功：CONNECTED
Session establishment complete on server 176.16.0.135/176.16.0.135:2181, sessionid = 0x1000002273d0009, negotiated timeout = 5000
连接zookeeper成功：SyncConnected
1.创建zooKeeper对象成功：CONNECTED
Session establishment complete on server 176.16.0.135/176.16.0.135:2181, sessionid = 0x1000002273d000a, negotiated timeout = 5000
连接zookeeper成功：SyncConnected
1.创建zooKeeper对象成功：CONNECTED
Reading reply sessionid:0x1000002273d000a, packet:: clientPath:null serverPath:null finished:false header:: 1,1  replyHeader:: 1,28386,0  request:: '/LOCKS/,#123,v{s{31,s{'world,'anyone}}},3  response:: '/LOCKS/0000000012 
Reading reply sessionid:0x1000002273d0001, packet:: clientPath:null serverPath:null finished:false header:: 1,1  replyHeader:: 1,28387,0  request:: '/LOCKS/,#123,v{s{31,s{'world,'anyone}}},3  response:: '/LOCKS/0000000013 
Reading reply sessionid:0x1000002273d0005, packet:: clientPath:null serverPath:null finished:false header:: 1,1  replyHeader:: 1,28385,0  request:: '/LOCKS/,#123,v{s{31,s{'world,'anyone}}},3  response:: '/LOCKS/0000000011 
Reading reply sessionid:0x1000002273d0008, packet:: clientPath:null serverPath:null finished:false header:: 1,1  replyHeader:: 1,28388,0  request:: '/LOCKS/,#123,v{s{31,s{'world,'anyone}}},3  response:: '/LOCKS/0000000014 
Reading reply sessionid:0x1000002273d0002, packet:: clientPath:null serverPath:null finished:false header:: 1,1  replyHeader:: 1,28384,0  request:: '/LOCKS/,#123,v{s{31,s{'world,'anyone}}},3  response:: '/LOCKS/0000000010 
2.Thread-1:成功创建lock节点[/LOCKS/0000000012], 开始竞争锁
2.Thread-7:成功创建lock节点[/LOCKS/0000000011], 开始竞争锁
2.Thread-3:成功创建lock节点[/LOCKS/0000000014], 开始竞争锁
2.Thread-4:成功创建lock节点[/LOCKS/0000000010], 开始竞争锁
2.Thread-8:成功创建lock节点[/LOCKS/0000000013], 开始竞争锁
Reading reply sessionid:0x1000002273d0007, packet:: clientPath:null serverPath:null finished:false header:: 1,1  replyHeader:: 1,28390,0  request:: '/LOCKS/,#123,v{s{31,s{'world,'anyone}}},3  response:: '/LOCKS/0000000016 
Reading reply sessionid:0x1000002273d0009, packet:: clientPath:null serverPath:null finished:false header:: 1,1  replyHeader:: 1,28389,0  request:: '/LOCKS/,#123,v{s{31,s{'world,'anyone}}},3  response:: '/LOCKS/0000000015 
2.Thread-6:成功创建lock节点[/LOCKS/0000000016], 开始竞争锁
2.Thread-2:成功创建lock节点[/LOCKS/0000000015], 开始竞争锁
Reading reply sessionid:0x1000002273d0004, packet:: clientPath:null serverPath:null finished:false header:: 1,1  replyHeader:: 1,28391,0  request:: '/LOCKS/,#123,v{s{31,s{'world,'anyone}}},3  response:: '/LOCKS/0000000017 
Reading reply sessionid:0x1000002273d0003, packet:: clientPath:null serverPath:null finished:false header:: 1,1  replyHeader:: 1,28392,0  request:: '/LOCKS/,#123,v{s{31,s{'world,'anyone}}},3  response:: '/LOCKS/0000000018 
2.Thread-0:成功创建lock节点[/LOCKS/0000000017], 开始竞争锁
2.Thread-5:成功创建lock节点[/LOCKS/0000000018], 开始竞争锁
Reading reply sessionid:0x1000002273d0006, packet:: clientPath:null serverPath:null finished:false header:: 1,1  replyHeader:: 1,28393,0  request:: '/LOCKS/,#123,v{s{31,s{'world,'anyone}}},3  response:: '/LOCKS/0000000019 
2.Thread-9:成功创建lock节点[/LOCKS/0000000019], 开始竞争锁
Reading reply sessionid:0x1000002273d0001, packet:: clientPath:null serverPath:null finished:false header:: 2,8  replyHeader:: 2,28393,0  request:: '/LOCKS,T  response:: v{'0000000012,'0000000011,'0000000014,'0000000013,'0000000016,'0000000015,'0000000018,'0000000017,'0000000019,'0000000010} 
Reading reply sessionid:0x1000002273d000a, packet:: clientPath:null serverPath:null finished:false header:: 2,8  replyHeader:: 2,28393,0  request:: '/LOCKS,T  response:: v{'0000000012,'0000000011,'0000000014,'0000000013,'0000000016,'0000000015,'0000000018,'0000000017,'0000000019,'0000000010} 
Reading reply sessionid:0x1000002273d0007, packet:: clientPath:null serverPath:null finished:false header:: 2,8  replyHeader:: 2,28393,0  request:: '/LOCKS,T  response:: v{'0000000012,'0000000011,'0000000014,'0000000013,'0000000016,'0000000015,'0000000018,'0000000017,'0000000019,'0000000010} 
Reading reply sessionid:0x1000002273d0002, packet:: clientPath:null serverPath:null finished:false header:: 2,8  replyHeader:: 2,28393,0  request:: '/LOCKS,T  response:: v{'0000000012,'0000000011,'0000000014,'0000000013,'0000000016,'0000000015,'0000000018,'0000000017,'0000000019,'0000000010} 
3.Thread-4:成功获取锁，锁节点为：/LOCKS/0000000010
Reading reply sessionid:0x1000002273d0009, packet:: clientPath:null serverPath:null finished:false header:: 2,8  replyHeader:: 2,28393,0  request:: '/LOCKS,T  response:: v{'0000000012,'0000000011,'0000000014,'0000000013,'0000000016,'0000000015,'0000000018,'0000000017,'0000000019,'0000000010} 
Reading reply sessionid:0x1000002273d0005, packet:: clientPath:null serverPath:null finished:false header:: 2,8  replyHeader:: 2,28393,0  request:: '/LOCKS,T  response:: v{'0000000012,'0000000011,'0000000014,'0000000013,'0000000016,'0000000015,'0000000018,'0000000017,'0000000019,'0000000010} 
Reading reply sessionid:0x1000002273d0008, packet:: clientPath:null serverPath:null finished:false header:: 2,8  replyHeader:: 2,28393,0  request:: '/LOCKS,T  response:: v{'0000000012,'0000000011,'0000000014,'0000000013,'0000000016,'0000000015,'0000000018,'0000000017,'0000000019,'0000000010} 
Reading reply sessionid:0x1000002273d0004, packet:: clientPath:null serverPath:null finished:false header:: 2,8  replyHeader:: 2,28393,0  request:: '/LOCKS,T  response:: v{'0000000012,'0000000011,'0000000014,'0000000013,'0000000016,'0000000015,'0000000018,'0000000017,'0000000019,'0000000010} 
Reading reply sessionid:0x1000002273d0003, packet:: clientPath:null serverPath:null finished:false header:: 2,8  replyHeader:: 2,28393,0  request:: '/LOCKS,T  response:: v{'0000000012,'0000000011,'0000000014,'0000000013,'0000000016,'0000000015,'0000000018,'0000000017,'0000000019,'0000000010} 
Reading reply sessionid:0x1000002273d0006, packet:: clientPath:null serverPath:null finished:false header:: 2,8  replyHeader:: 2,28393,0  request:: '/LOCKS,T  response:: v{'0000000012,'0000000011,'0000000014,'0000000013,'0000000016,'0000000015,'0000000018,'0000000017,'0000000019,'0000000010} 
Reading reply sessionid:0x1000002273d000a, packet:: clientPath:null serverPath:null finished:false header:: 3,3  replyHeader:: 3,28393,0  request:: '/LOCKS/0000000011,T  response:: s{28385,28385,1548055011348,1548055011348,0,0,0,72057603286171653,3,0,28385} 
Reading reply sessionid:0x1000002273d0009, packet:: clientPath:null serverPath:null finished:false header:: 3,3  replyHeader:: 3,28393,0  request:: '/LOCKS/0000000014,T  response:: s{28388,28388,1548055011349,1548055011349,0,0,0,72057603286171656,3,0,28388} 
4.Thread-1:未获取锁，监听比当前锁更小的节点：/LOCKS/0000000011
Reading reply sessionid:0x1000002273d0001, packet:: clientPath:null serverPath:null finished:false header:: 3,3  replyHeader:: 3,28393,0  request:: '/LOCKS/0000000012,T  response:: s{28386,28386,1548055011348,1548055011348,0,0,0,72057603286171658,3,0,28386} 
4.Thread-2:未获取锁，监听比当前锁更小的节点：/LOCKS/0000000014
4.Thread-8:未获取锁，监听比当前锁更小的节点：/LOCKS/0000000012
Reading reply sessionid:0x1000002273d0005, packet:: clientPath:null serverPath:null finished:false header:: 3,3  replyHeader:: 3,28393,0  request:: '/LOCKS/0000000010,T  response:: s{28384,28384,1548055011255,1548055011255,0,0,0,72057603286171650,3,0,28384} 
4.Thread-7:未获取锁，监听比当前锁更小的节点：/LOCKS/0000000010
Reading reply sessionid:0x1000002273d0007, packet:: clientPath:null serverPath:null finished:false header:: 3,3  replyHeader:: 3,28393,0  request:: '/LOCKS/0000000015,T  response:: s{28389,28389,1548055011349,1548055011349,0,0,0,72057603286171657,3,0,28389} 
Reading reply sessionid:0x1000002273d0003, packet:: clientPath:null serverPath:null finished:false header:: 3,3  replyHeader:: 3,28393,0  request:: '/LOCKS/0000000017,T  response:: s{28391,28391,1548055011349,1548055011349,0,0,0,72057603286171652,3,0,28391} 
Reading reply sessionid:0x1000002273d0004, packet:: clientPath:null serverPath:null finished:false header:: 3,3  replyHeader:: 3,28393,0  request:: '/LOCKS/0000000016,T  response:: s{28390,28390,1548055011349,1548055011349,0,0,0,72057603286171655,3,0,28390} 
Reading reply sessionid:0x1000002273d0008, packet:: clientPath:null serverPath:null finished:false header:: 3,3  replyHeader:: 3,28393,0  request:: '/LOCKS/0000000013,T  response:: s{28387,28387,1548055011349,1548055011349,0,0,0,72057603286171649,3,0,28387} 
4.Thread-6:未获取锁，监听比当前锁更小的节点：/LOCKS/0000000015
4.Thread-5:未获取锁，监听比当前锁更小的节点：/LOCKS/0000000017
4.Thread-3:未获取锁，监听比当前锁更小的节点：/LOCKS/0000000013
4.Thread-0:未获取锁，监听比当前锁更小的节点：/LOCKS/0000000016
Reading reply sessionid:0x1000002273d0006, packet:: clientPath:null serverPath:null finished:false header:: 3,3  replyHeader:: 3,28393,0  request:: '/LOCKS/0000000018,T  response:: s{28392,28392,1548055011349,1548055011349,0,0,0,72057603286171651,3,0,28392} 
4.Thread-9:未获取锁，监听比当前锁更小的节点：/LOCKS/0000000018
6.Thread-4:开始释放锁，锁节点为：/LOCKS/0000000010
Got notification sessionid:0x1000002273d0005
Got notification sessionid:0x1000002273d000a
Got WatchedEvent state:SyncConnected type:NodeChildrenChanged path:/LOCKS for sessionid 0x1000002273d000a
Got WatchedEvent state:SyncConnected type:NodeDeleted path:/LOCKS/0000000010 for sessionid 0x1000002273d0005
连接zookeeper成功：SyncConnected
5.Thread-7:成功获取锁，锁节点为：/LOCKS/0000000011
Got notification sessionid:0x1000002273d0005
Got WatchedEvent state:SyncConnected type:NodeChildrenChanged path:/LOCKS for sessionid 0x1000002273d0005
Got notification sessionid:0x1000002273d0004
连接zookeeper成功：SyncConnected
Got WatchedEvent state:SyncConnected type:NodeChildrenChanged path:/LOCKS for sessionid 0x1000002273d0004
连接zookeeper成功：SyncConnected
Got notification sessionid:0x1000002273d0007
Got notification sessionid:0x1000002273d0002
Got WatchedEvent state:SyncConnected type:NodeChildrenChanged path:/LOCKS for sessionid 0x1000002273d0002
Got WatchedEvent state:SyncConnected type:NodeChildrenChanged path:/LOCKS for sessionid 0x1000002273d0007
连接zookeeper成功：SyncConnected
连接zookeeper成功：SyncConnected
Got notification sessionid:0x1000002273d0009
Got notification sessionid:0x1000002273d0001
Got WatchedEvent state:SyncConnected type:NodeChildrenChanged path:/LOCKS for sessionid 0x1000002273d0001
Got WatchedEvent state:SyncConnected type:NodeChildrenChanged path:/LOCKS for sessionid 0x1000002273d0009
连接zookeeper成功：SyncConnected
连接zookeeper成功：SyncConnected
Got notification sessionid:0x1000002273d0008
Got notification sessionid:0x1000002273d0006
Got WatchedEvent state:SyncConnected type:NodeChildrenChanged path:/LOCKS for sessionid 0x1000002273d0006
Got notification sessionid:0x1000002273d0003
Got WatchedEvent state:SyncConnected type:NodeChildrenChanged path:/LOCKS for sessionid 0x1000002273d0008
连接zookeeper成功：SyncConnected
Got WatchedEvent state:SyncConnected type:NodeChildrenChanged path:/LOCKS for sessionid 0x1000002273d0003
连接zookeeper成功：SyncConnected
连接zookeeper成功：SyncConnected
Reading reply sessionid:0x1000002273d0002, packet:: clientPath:null serverPath:null finished:false header:: 3,2  replyHeader:: 3,28394,0  request:: '/LOCKS/0000000010,-1  response:: null
7.Thread-4:释放锁成功，锁节点为：/LOCKS/0000000010
6.Thread-7:开始释放锁，锁节点为：/LOCKS/0000000011
Got notification sessionid:0x1000002273d000a
Got WatchedEvent state:SyncConnected type:NodeDeleted path:/LOCKS/0000000011 for sessionid 0x1000002273d000a
Reading reply sessionid:0x1000002273d0005, packet:: clientPath:null serverPath:null finished:false header:: 4,2  replyHeader:: 4,28395,0  request:: '/LOCKS/0000000011,-1  response:: null
7.Thread-7:释放锁成功，锁节点为：/LOCKS/0000000011
5.Thread-1:成功获取锁，锁节点为：/LOCKS/0000000012
6.Thread-1:开始释放锁，锁节点为：/LOCKS/0000000012
Got notification sessionid:0x1000002273d0001
Got WatchedEvent state:SyncConnected type:NodeDeleted path:/LOCKS/0000000012 for sessionid 0x1000002273d0001
5.Thread-8:成功获取锁，锁节点为：/LOCKS/0000000013
Reading reply sessionid:0x1000002273d000a, packet:: clientPath:null serverPath:null finished:false header:: 4,2  replyHeader:: 4,28396,0  request:: '/LOCKS/0000000012,-1  response:: null
7.Thread-1:释放锁成功，锁节点为：/LOCKS/0000000012
6.Thread-8:开始释放锁，锁节点为：/LOCKS/0000000013
Got notification sessionid:0x1000002273d0008
Got WatchedEvent state:SyncConnected type:NodeDeleted path:/LOCKS/0000000013 for sessionid 0x1000002273d0008
5.Thread-3:成功获取锁，锁节点为：/LOCKS/0000000014
Reading reply sessionid:0x1000002273d0001, packet:: clientPath:null serverPath:null finished:false header:: 4,2  replyHeader:: 4,28397,0  request:: '/LOCKS/0000000013,-1  response:: null
7.Thread-8:释放锁成功，锁节点为：/LOCKS/0000000013
6.Thread-3:开始释放锁，锁节点为：/LOCKS/0000000014
Got notification sessionid:0x1000002273d0009
Got WatchedEvent state:SyncConnected type:NodeDeleted path:/LOCKS/0000000014 for sessionid 0x1000002273d0009
Reading reply sessionid:0x1000002273d0008, packet:: clientPath:null serverPath:null finished:false header:: 4,2  replyHeader:: 4,28398,0  request:: '/LOCKS/0000000014,-1  response:: null
7.Thread-3:释放锁成功，锁节点为：/LOCKS/0000000014
5.Thread-2:成功获取锁，锁节点为：/LOCKS/0000000015
6.Thread-2:开始释放锁，锁节点为：/LOCKS/0000000015
Got notification sessionid:0x1000002273d0007
Got WatchedEvent state:SyncConnected type:NodeDeleted path:/LOCKS/0000000015 for sessionid 0x1000002273d0007
5.Thread-6:成功获取锁，锁节点为：/LOCKS/0000000016
Reading reply sessionid:0x1000002273d0009, packet:: clientPath:null serverPath:null finished:false header:: 4,2  replyHeader:: 4,28399,0  request:: '/LOCKS/0000000015,-1  response:: null
7.Thread-2:释放锁成功，锁节点为：/LOCKS/0000000015
Got ping response for sessionid: 0x1000002273d0009 after 10ms
Got ping response for sessionid: 0x1000002273d0007 after 5ms
6.Thread-6:开始释放锁，锁节点为：/LOCKS/0000000016
Got notification sessionid:0x1000002273d0004
Got WatchedEvent state:SyncConnected type:NodeDeleted path:/LOCKS/0000000016 for sessionid 0x1000002273d0004
Reading reply sessionid:0x1000002273d0007, packet:: clientPath:null serverPath:null finished:false header:: 4,2  replyHeader:: 4,28400,0  request:: '/LOCKS/0000000016,-1  response:: null
7.Thread-6:释放锁成功，锁节点为：/LOCKS/0000000016
5.Thread-0:成功获取锁，锁节点为：/LOCKS/0000000017
Got ping response for sessionid: 0x1000002273d0004 after 5ms
Got ping response for sessionid: 0x1000002273d0003 after 1ms
Got ping response for sessionid: 0x1000002273d0006 after 1ms
Got ping response for sessionid: 0x1000002273d0002 after 1ms
6.Thread-0:开始释放锁，锁节点为：/LOCKS/0000000017
Got notification sessionid:0x1000002273d0003
Got WatchedEvent state:SyncConnected type:NodeDeleted path:/LOCKS/0000000017 for sessionid 0x1000002273d0003
Reading reply sessionid:0x1000002273d0004, packet:: clientPath:null serverPath:null finished:false header:: 4,2  replyHeader:: 4,28401,0  request:: '/LOCKS/0000000017,-1  response:: null
7.Thread-0:释放锁成功，锁节点为：/LOCKS/0000000017
5.Thread-5:成功获取锁，锁节点为：/LOCKS/0000000018
6.Thread-5:开始释放锁，锁节点为：/LOCKS/0000000018
Got notification sessionid:0x1000002273d0006
Got WatchedEvent state:SyncConnected type:NodeDeleted path:/LOCKS/0000000018 for sessionid 0x1000002273d0006
5.Thread-9:成功获取锁，锁节点为：/LOCKS/0000000019
Reading reply sessionid:0x1000002273d0003, packet:: clientPath:null serverPath:null finished:false header:: 4,2  replyHeader:: 4,28402,0  request:: '/LOCKS/0000000018,-1  response:: null
7.Thread-5:释放锁成功，锁节点为：/LOCKS/0000000018
Got ping response for sessionid: 0x1000002273d0005 after 2ms
Got ping response for sessionid: 0x1000002273d000a after 4ms
Got ping response for sessionid: 0x1000002273d0001 after 4ms
6.Thread-9:开始释放锁，锁节点为：/LOCKS/0000000019
Reading reply sessionid:0x1000002273d0006, packet:: clientPath:null serverPath:null finished:false header:: 4,2  replyHeader:: 4,28403,0  request:: '/LOCKS/0000000019,-1  response:: null
7.Thread-9:释放锁成功，锁节点为：/LOCKS/0000000019
dengjili
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
java操作zookeeper_Java代码操作zookeeper
weixin_30128407的博客
02-13 905
以下为一个完整JAVA操作Zookeeper项目步骤：1. 项目中pom.xml中添加需要的依赖jar包信息org.apache.zookeeperzookeeper3.4.9com.101teczkclient0.102. 在resource下添加log4j.properties日志打印信息log4j.rootLogger=DEBUG,myConsolelog4j.appender.myCons...
java api操作hbase时遇到的问题
Lu_Xiao_Yue的博客
12-04 1618
使用JavaAPI，java连接Hbase hbase卡着不动了 &lt;span style="color:#ff0000"&gt;log4j:WARN No appenders could be found for logger (org.apache.hadoop.security.Groups). log4j:WARN Please initialize the log4j system...
hbase无法访问：Reading reply sessionid:0x3000484bfd0001d, packet:: clientPath:null serverPath:null finish
A coder of life
08-08 4424
hbase连接打印如下日志，不报错， 解决办法是把集群的hosts添加到本地电脑的hosts ，本地电脑hosts的地址一般为：C:\Windows\System32\drivers\etc
zookeeper输出大量debug日志原因分析
热门推荐
珺珺去哪儿
06-02 1万+
今天无意中发现线上tomcat的catalina.out文件输出大量的zookeeper debug信息，以下是日志片段： 10:30:03.973 [localhost-startStop-1-SendThread(10.168.180.94:2181)] DEBUG org.apache.zookeeper.ClientCnxn – Reading reply sessionid:0x2
如何使用Curator监听zookeeper事件变化
三劫散仙
09-26 711
掌握zookeeper事件监听机制，非常重要，可以说是跨入了进阶的门槛，只有掌握了如何监听某个节点或路径，我们才能在节点变化后，做一些我们想做的事，包括： 1，配置文件同步 2，主从切换 3，分布式队列 4，分布式锁 5，其他 散仙，在以前的文章里面有写过使用zookeeper原生的api，监听zk节点变化，那么本篇我们就来看下，如何使用curator来完成监听，代码如下： [c...
ZooKeeper应用---分布式锁
weixin_44489428的博客
03-22 4451
zookeeper通过临时有序节点结合API中的回调和监听机制实现分布式锁
分布式协调服务-ZooKeeper
m0_67390788的博客
06-21 300
加粗样式ZooKeeper官网 ZooKeeper 是一种面向分布式应用程序的分布式开源协调服务，目前属于 Apache 维护。现分布式数据一致性解决方案中可以基于 ZooKeeper特点：数据模型和分层命名空间： ZooKeeper 提供的命名空间与 Unix 文件系统的命名空间非常相似。名称是由斜杠（ / ）分隔的路径元素序列。每个节点称做一个 ZNode ，ZooKeeper 命名空间中的每个节点(ZNode)都由一个唯一路径标识。 ZooKeeper 简单数据模型：可配置 Cluster顺序访问高性
作业9：通过curator存储和读取偏移量
烙痕丷的博客
08-10 434
作业要求：以Scala代码编程，通过curator存储和读取偏移量（存储到ZK，从ZK读取）依赖包： //为方便展示，就不把版本号抽取出来了。 &lt;dependency&gt; &lt;groupId&gt;org.apache.curator&lt;/groupId&gt; &lt;artifactId&gt;curator-recipes&lt;/artifactId&...
zookeeper入门(一)
weixin_42412601的博客
05-15 288
目录简介应用场景 简介 大数据生态系统里很多组件的命名都是某种动物，例如Hadoop是????，hive是????，zookeeper就是动物园管理者，是管理大数据生态系统各组件的管理员。 zookeeper是经典的分布式数据一致性解决方案，致力于为分布式应用提供一个高性能，高可用，且具有严格顺序访问控制能力的分布式协调存储服务。 应用场景 维护配置信息 Java编程经常会遇到配置项，例如数据库的user、password等，通常配置信息会放在配置文件中，再把配置文件放在服务器上。当需要修改配置信息时，要
zookeeper使用IDEA测试API出现KeeperException$ConnectionLossException解决思路
weixin_43114582的博客
03-23 997
出现该异常主要从以下几个方面排查1.是否存在超时问题2.防火墙是否开放了对应的端口 1.是否存在超时问题 Watcher watcher = new Watcher() { public void process(WatchedEvent watchedEvent) { System.out.println("监听了" + watchedE...
基于ZooKeeper的统一配置管理实现（一）
chizhihe8199的博客
01-12 626
先来看一下配置管理实现的效果 服务端启动 Jan 12, 2017 4:18:43 PM org.apache.zookeeper.server.persistence.FileTxnLog append INFO: Creating new log file: log.4000000...
zookeeper-笔记-命令
weixin_37862824的博客
05-07 1326
一、启动zk服务 其实就是启动了zookeeper服务端，只是开启了zookeeper一个节点，后面会介绍如何开启服务端多个节点 zkServer.sh start 二、启动完了之后，就可以通过客户端查看服务端的节点情况 1、启动zookeeper客户端 zkCli.sh 2、退出客户端：quit 3、查看当前服务端树形情况：ls -R / 客户端在服务端创建永久节点：create /app1 创建临时节点：create -e /lock 监听lock节点的状态：stat -w /lock 如果节点过期
一个正常的zookeeper日志
okkeqin的专栏
02-24 7369
2017-02-24 14:39:38.817 INFO [org.apache.zookeeper.ZooKeeper] - Client environment:java.library.path=C:\Program Files\Java\jre1.8.0_102\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:/Pr
集群外访问Hbase – access Hbase use a java client program
足迹
05-25 4709
<br /><br />集群外访问Hbase – access Hbase use a java client program<br /> <br />集群环境：<br />Master - <br />10.123.122.151          test-Master<br /> <br />Slave   - <br />10.123.122.163          test-DATA01<br />10.123.122.162          test-DATA02<br />10.123.
Zookeeper案例之分布式全局唯一ID生成
weixiaohuai的博客
01-21 2003
目录 一、概述 二、案例实现 一、概述 在单体架构中，我们通常使用数据库字段自带的自增auto_increment属性来自动为每一条记录生成唯一的ID，但是当我们采用分布式系统后，特别是分库分表后，就无法再依靠数据库的auto_increment属性来唯一标识一条记录，这就需要采用其他方法来生成全局唯一ID。 在zookeeper中，它提供了一种以创建临时有序节点来获取到全局唯一ID，它能保证在整个分布式系统中的全局唯一性。 下面我们通过一个简单的案例来说明如何利用zookeeper生成全局唯一
开发日志 2017年8月31日
在咖啡里溺水的鱼
08-31 2054
今日任务解决Java客户端连接Hbase的问题日志2017年8月31日10:27:09使用Ambari下载的hbase-site.xml作为配置文件运行测试类 @Test public void test2() { try { Configuration conf = HBaseConfiguration.create();
使用MyEclipse开发HBase应用程序
wuruiaoxue的专栏
11-30 2446
当第三方访问HBase的时候，首选需要访问ZooKeeper,因为HBase的重要信息保存在ZooKeeper当中。我们知道，ZooKeeper集群的信息由$$HBASE_HOME/conf/hbase-site.xml文件指定。因此需要通过classpath来指定HBase配置文件的位置，即$HBASE_HOME/conf的位置。 使用HBase客户端进行编程的时候，下文制定的JAR包对于程序来说
分布式专题-04分布式协调服务之Zookeeper实践及原理分析
Zookeeper是一个开放源码的分布式协调服务，其主要用于处理分布式应用程序中的一些复杂的任务，比如排队、选举、通知等。它的设计目标是提供一个高性能、高可用、高可靠的分布式协调服务框架。 Zookeeper的核心原理...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值