Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Hbase Region Server showing shared memory segment error

avatar
Super Collaborator

2017-12-19 02:40:55,536 ERROR [ShortCircuitCache_SlotReleaser] shortcircuit.ShortCircuitCache: ShortCircuitCache(0x79bb282e): failed to release short-circuit shared memory slot Slot(slotIdx=6, shm=DfsClientShm(4c3535b7ecb532cd3bb275306d5b86d5)) by sending ReleaseShortCircuitAccessRequestProto to /var/lib/hadoop-hdfs/dn_socket. Closing shared memory segment. java.io.IOException: ERROR_INVALID: there is no shared memory segment registered with shmId 4c3535b7ecb532cd3bb275306d5b86d5

2 REPLIES 2

avatar
Super Collaborator

ShortCircuitCache(0x8671076): failed to release short-circuit shared memory slot Slot(slotIdx=74, shm=DfsClientShm(ad7f9d8145e3cb1e1ea3e42955eacfb5)) by sending ReleaseShortCircuitAccessRequestProto to /var/lib/hadoop-hdfs/dn_socket. Closing shared memory segment.

java.io.IOException: ERROR_INVALID: there is no shared memory segment registered with shmId ad7f9d8145e3cb1e1ea3e42955eacfb5
	at org.apache.hadoop.hdfs.shortcircuit.ShortCircuitCache$SlotReleaser.run(ShortCircuitCache.java:208)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

avatar
New Contributor

We got the similar error.. However we figured out the issue was with Linux server socket communication. Once we restart Hbase Region server , service started fine. Problem with these type of issues as we lost Data locality on that region server due to restarting Hbase Region server service.