Welcome to the new Gigaspaces XAP forum. To recover your account, please follow these instructions.

Ask Your Question
0

Not able to deploy more then 4 partition on Linux box because of OutOfMemoryError

Hi,

GSC is not getting created because of OutOfMemoryError error while deploying more then 4 partition on space.This issue i am facing on Linux , on the other hand its able to deploy 10 partition on Windows 7.

Kindly help me to resolve this problem.

Steps i followed : i)ran gs-agent with following config. LOOKUPLOCATORS=<ip>; export LOOKUPLOCATORS NIC_ADDR=<ip>; export NIC_ADDR GSC_JAVA_OPTIONS=-Xmx60g export GSC_JAVA_OPTIONS ./gs-agent.sh

ii) deploy 5 partitions [ bin]$ ./gs.sh deploy-space -cluster total_members=5,0 space

GSC Log:

System Environment: System: OS Name: Linux OS Version: 2.6.32-358.el6.x86_64 Architecture: amd64 Number Of Processors: 24 JVM Details: Java Version: 1.7.0_09-icedtea, Oracle Corporation Java Runtime: OpenJDK Runtime Environment (build 1.7.0_09-icedtea-mockbuild_2013_01_15_04_12-b00) Java VM: OpenJDK 64-Bit Server VM 23.2-b09, Oracle Corporation Java Home: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.9.x86_64/jre JVM Memory: Max Heap Size (KB): 55924096 Current Allocated Heap Size (KB): 1923606

....... ....... ......

GSC Error Logs

2014-10-16 14:47:20,245 space [5] SEVERE [com.gigaspaces.core.common] - Failed to start [space_container10:space] space with url [/./space?total_members=10,0&cluster_schema=partitioned-sync2backup&id=10&schema=default&locators=10.189.220.11&groups=gigaspaces-10.0.1-XAPPremium-ga&state=started]; Caused by: java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:691) at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:943) at java.util.concurrent.ThreadPoolExecutor.ensurePrestart(ThreadPoolExecutor.java:1555) at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:333) at java.util.concurrent.ScheduledThreadPoolExecutor.scheduleAtFixedRate(ScheduledThreadPoolExecutor.java:570) at com.gigaspaces.internal.cluster.node.impl.ReplicationNode.<init>(ReplicationNode.java:174) at com.gigaspaces.internal.server.space.replication.SpaceReplicationInitializer.createReplicationNode(SpaceReplicationInitializer.java:278) at com.gigaspaces.internal.server.space.replication.SpaceReplicationInitializer.<init>(SpaceReplicationInitializer.java:124)

asked 2014-10-16 23:16:41 -0500

Hemant gravatar image
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

Have you set the ulimit -n to 32000 before running the agent? See: http://docs.gigaspaces.com/sbp/moving...

I suggest you start the same number of GSCs as number of partitions.

In production you should use elastic PU.

answered 2014-10-20 10:21:16 -0500

shay hassidim gravatar image
edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2014-10-16 23:16:41 -0500

Seen: 145 times

Last updated: Oct 20 '14