Apache Ignite client on AWS Lambda

[babu prasad <ba...@gmail.com>]

Hi,

I almost got Ignite client running on AWS Lambda.
But then, I hit this error,

Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
bind time server socket within specified port range
[locHost=ip-10-0-73-203.ec2.internal/10.0.73.203, startPort=31100,
endPort=31199]
	at org.apache.ignite.internal.processors.clock.GridClockServer.start(GridClockServer.java:101)
	at org.apache.ignite.internal.processors.clock.GridClockSyncProcessor.start(GridClockSyncProcessor.java:96)
	at org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1523)
	... 9 more

This may not be an ignite issue at all, but wanted to check if there are
any workarounds and what it is trying to do here?

Thanks!

Re: Apache Ignite client on AWS Lambda

[Denis Magda <dm...@gridgain.com>]

Hi,

This happens because it's either not allowed to open an UDP socket on your
machine or the port is already in use.

To get more details on what's happening please enable debug level logs for
org.apache.ignite.internal.processors.clock.GridClockServer. You can use and
modify {ignite}/config/log4j.xml for that.

If the reason is in the fact that all the ports are already in use then use
IgniteConfiguration.setTimeServerPortBase() to overcome the issue.
But most likely the reason is in the network configuration of the machine.

Regards,
Denis



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-client-on-AWS-Lambda-tp2596p2608.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.