Re: Cache.put latencies high
All nodes are in same az. 1-2 ms ping times.
Sent from my iPhone
> On Jan 17, 2016, at 10:52 PM, Jörn Franke wrote:
>
> Are you using AWS ? What is the ping time between the nodes?
>
>> On 18 Jan 2016, at 06:48, Babu Prasad wrote:
>>
>> I did simple sequential puts to the cache. The latencies kept spiking
>> intermittently to 30ms or higher.
>> The test took about 30 minutes to load 1M records. I am using the s3 ip
>> finder for discovery.
>> I would expect 1-2 ms at max putting to a cache per request, but 30 ms seems
>> a little higher.
>> Are there best practices I should follow to tune the server and the client
>> for better latency?
>>
>> Sent from my iPhone
>>
>>> On Jan 12, 2016, at 11:59 PM, Dmitriy Setrakyan
>>> wrote:
>>>
>>> This is usually a problem with one-threaded benchmarks.
>>>
>>> 1. You should add a warm up step, i.e. have your system work for about a
>>> minute before starting measuring.
>>>
>>> 2. You should decide whether your application will be single-threaded or
>>> multi-threaded. If it is multi-threaded, then your test should also be
>>> multi-threaded.
>>>
>>> 3. And finally you should verify that network works well in your
>>> environment. Do you have 10G ethernet?
>>>
>>> D.
>>>
On Tue, Jan 12, 2016 at 8:27 PM, babu prasad wrote:
Hi,
I have configured 2 ignite servers with a heap size of 8G each.
Running with backups=1 and primary_sync mode.
Ignite servers are being used as a write behind cache for my Aurora
database.
I am trying to run a load test with 3 clients talking to the remote cache
in the 2 ignite servers.
All the hosts are in the same availability zone.
My clients do a simple put and I calculate time taken for put on the
client side.
long startTime = System.currentTimeMillis();
cache.put(k, c1);
long elapsedTime = System.currentTimeMillis() - startTime;
System.out.println("Total elapsed timein milliseconds: " + elapsedTime);
Here is the latency from the last few requests:
Total elapsed timein milliseconds: 31
Total elapsed timein milliseconds: 29
Total elapsed timein milliseconds: 26
Total elapsed timein milliseconds: 28
Total elapsed timein milliseconds: 28
Total elapsed timein milliseconds: 27
Total elapsed timein milliseconds: 27
Total elapsed timein milliseconds: 29
Total elapsed timein milliseconds: 26
Total elapsed timein milliseconds: 26
Total elapsed timein milliseconds: 27
Total elapsed timein milliseconds: 27
Total elapsed timein milliseconds: 28
Total elapsed timein milliseconds: 28
Total elapsed timein milliseconds: 27
Total elapsed timein milliseconds: 26
Total elapsed timein milliseconds: 27
Total elapsed timein milliseconds: 28
Total elapsed timein milliseconds: 27
Total elapsed timein milliseconds: 26
Total elapsed timein milliseconds: 26
Total elapsed timein milliseconds: 29
Total elapsed timein milliseconds: 26
Total elapsed timein milliseconds: 27
Total elapsed timein milliseconds: 26
Total elapsed timein milliseconds: 27
Total elapsed timein milliseconds: 29
Total elapsed timein milliseconds: 27
Total elapsed timein milliseconds: 28
Total elapsed timein milliseconds: 26
Total elapsed timein milliseconds: 27
Total elapsed timein milliseconds: 27
Total elapsed timein milliseconds: 27
Total elapsed timein milliseconds: 29
Not sure what is going on here. I am pretty sure I am doing something
wrong here.
Thanks!
>>>
Re: Cache.put latencies high
Are you using AWS ? What is the ping time between the nodes?
> On 18 Jan 2016, at 06:48, Babu Prasad wrote:
>
> I did simple sequential puts to the cache. The latencies kept spiking
> intermittently to 30ms or higher.
> The test took about 30 minutes to load 1M records. I am using the s3 ip
> finder for discovery.
> I would expect 1-2 ms at max putting to a cache per request, but 30 ms seems
> a little higher.
> Are there best practices I should follow to tune the server and the client
> for better latency?
>
> Sent from my iPhone
>
>> On Jan 12, 2016, at 11:59 PM, Dmitriy Setrakyan
>> wrote:
>>
>> This is usually a problem with one-threaded benchmarks.
>>
>> 1. You should add a warm up step, i.e. have your system work for about a
>> minute before starting measuring.
>>
>> 2. You should decide whether your application will be single-threaded or
>> multi-threaded. If it is multi-threaded, then your test should also be
>> multi-threaded.
>>
>> 3. And finally you should verify that network works well in your
>> environment. Do you have 10G ethernet?
>>
>> D.
>>
>>> On Tue, Jan 12, 2016 at 8:27 PM, babu prasad wrote:
>>> Hi,
>>>
>>> I have configured 2 ignite servers with a heap size of 8G each.
>>> Running with backups=1 and primary_sync mode.
>>>
>>> Ignite servers are being used as a write behind cache for my Aurora
>>> database.
>>>
>>> I am trying to run a load test with 3 clients talking to the remote cache
>>> in the 2 ignite servers.
>>> All the hosts are in the same availability zone.
>>>
>>> My clients do a simple put and I calculate time taken for put on the client
>>> side.
>>>
>>> long startTime = System.currentTimeMillis();
>>> cache.put(k, c1);
>>> long elapsedTime = System.currentTimeMillis() - startTime;
>>> System.out.println("Total elapsed timein milliseconds: " + elapsedTime);
>>>
>>> Here is the latency from the last few requests:
>>> Total elapsed timein milliseconds: 31
>>> Total elapsed timein milliseconds: 29
>>> Total elapsed timein milliseconds: 26
>>> Total elapsed timein milliseconds: 28
>>> Total elapsed timein milliseconds: 28
>>> Total elapsed timein milliseconds: 27
>>> Total elapsed timein milliseconds: 27
>>> Total elapsed timein milliseconds: 29
>>> Total elapsed timein milliseconds: 26
>>> Total elapsed timein milliseconds: 26
>>> Total elapsed timein milliseconds: 27
>>> Total elapsed timein milliseconds: 27
>>> Total elapsed timein milliseconds: 28
>>> Total elapsed timein milliseconds: 28
>>> Total elapsed timein milliseconds: 27
>>> Total elapsed timein milliseconds: 26
>>> Total elapsed timein milliseconds: 27
>>> Total elapsed timein milliseconds: 28
>>> Total elapsed timein milliseconds: 27
>>> Total elapsed timein milliseconds: 26
>>> Total elapsed timein milliseconds: 26
>>> Total elapsed timein milliseconds: 29
>>> Total elapsed timein milliseconds: 26
>>> Total elapsed timein milliseconds: 27
>>> Total elapsed timein milliseconds: 26
>>> Total elapsed timein milliseconds: 27
>>> Total elapsed timein milliseconds: 29
>>> Total elapsed timein milliseconds: 27
>>> Total elapsed timein milliseconds: 28
>>> Total elapsed timein milliseconds: 26
>>> Total elapsed timein milliseconds: 27
>>> Total elapsed timein milliseconds: 27
>>> Total elapsed timein milliseconds: 27
>>> Total elapsed timein milliseconds: 29
>>>
>>> Not sure what is going on here. I am pretty sure I am doing something wrong
>>> here.
>>>
>>>
>>> Thanks!
>>
Re: Alternate way of using DBH2ServerStartup ??
Ravi,
You may use MySql, but in this case you will need to change data sources in
examples.
In examples data sources configured to use H2 database data source.
So you need:
1) modify pom.xml - add dependency to MySql jdbc driver
2) modify examples code - replace H2 data sources with MySql data sources
3) start MySql, create tables and insert data using MySql tools
4) start examples
Hope this help.
On Mon, Jan 18, 2016 at 12:22 PM, Ravi wrote:
> /**
> * Start H2 database TCP server in order to access sample in-memory
> database
> from other processes.
> */
> public class DbH2ServerStartup {
> /** Create table script. */
> private static final String CREATE_PERSON_TABLE =
> "create table if not exists PERSON(id bigint not null, first_name
> varchar(50), last_name varchar(50), PRIMARY KEY(id));";
>
> /** Sample data script. */
> private static final String POPULATE_PERSON_TABLE =
> "delete from PERSON;\n" +
> "insert into PERSON(id, first_name, last_name) values(1,
> 'Johannes',
> 'Kepler');\n" +
> "insert into PERSON(id, first_name, last_name) values(2, 'Galileo',
> 'Galilei');\n" +
> "insert into PERSON(id, first_name, last_name) values(3, 'Henry',
> 'More');\n" +
> "insert into PERSON(id, first_name, last_name) values(4, 'Polish',
> 'Brethren');\n" +
> "insert into PERSON(id, first_name, last_name) values(5, 'Robert',
> 'Boyle');\n" +
> "insert into PERSON(id, first_name, last_name) values(6, 'Wilhelm',
> 'Leibniz');";
>
> /**
> * Populate sample database.
> *
> * @throws SQLException if
> */
> public static void populateDatabase() throws SQLException {
> // Try to connect to database TCP server.
> JdbcConnectionPool dataSrc =
> JdbcConnectionPool.create("jdbc:mysql://172.17.125.19/security_sample",
> "coeuser", "CoeUser@2014");
>
> // Create Person table in database.
> RunScript.execute(dataSrc.getConnection(), new
> StringReader(CREATE_PERSON_TABLE));
>
> // Populates Person table with sample data in database.
> RunScript.execute(dataSrc.getConnection(), new
> StringReader(POPULATE_PERSON_TABLE));
> }
>
> /**
> * Start H2 database TCP server.
> *
> * @param args Command line arguments, none required.
> * @throws IgniteException If start H2 database TCP server failed.
> */
> public static void main(String[] args) throws IgniteException {
> try {
> // Start H2 database TCP server in order to access sample
> in-memory database from other processes.
> Server.createTcpServer("-tcpDaemon").start();
>
> populateDatabase();
>
> // Try to connect to database TCP server.
> JdbcConnectionPool dataSrc =
> JdbcConnectionPool.create("jdbc:mysql://172.17.125.19/security_sample",
> "coeuser", "CoeUser@2014");
>
> // Create Person table in database.
> RunScript.execute(dataSrc.getConnection(), new
> StringReader(CREATE_PERSON_TABLE));
>
> // Populates Person table with sample data in database.
> RunScript.execute(dataSrc.getConnection(), new
> StringReader(POPULATE_PERSON_TABLE));
> }
> catch (SQLException e) {
> throw new IgniteException("Failed to start database TCP
> server",
> e);
> }
>
> try {
> do {
> System.out.println("Type 'q' and press 'Enter' to stop H2
> TCP server...");
> }
> while ('q' != System.in.read());
> }
> catch (IOException ignored) {
> // No-op.
> }
> }
> }
>
>
> DbH2ServerStartup class is compulsory need to start the server of TCP/Ip
> needed to query the examples. But if i wat to query the example form mysql
> databse without starting the DBH2 server. How can i do this?
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Alternate-way-of-using-DBH2ServerStartup-tp2599.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com
Re: Cache.put latencies high
I did simple sequential puts to the cache. The latencies kept spiking
intermittently to 30ms or higher.
The test took about 30 minutes to load 1M records. I am using the s3 ip finder
for discovery.
I would expect 1-2 ms at max putting to a cache per request, but 30 ms seems a
little higher.
Are there best practices I should follow to tune the server and the client for
better latency?
Sent from my iPhone
> On Jan 12, 2016, at 11:59 PM, Dmitriy Setrakyan wrote:
>
> This is usually a problem with one-threaded benchmarks.
>
> 1. You should add a warm up step, i.e. have your system work for about a
> minute before starting measuring.
>
> 2. You should decide whether your application will be single-threaded or
> multi-threaded. If it is multi-threaded, then your test should also be
> multi-threaded.
>
> 3. And finally you should verify that network works well in your environment.
> Do you have 10G ethernet?
>
> D.
>
>> On Tue, Jan 12, 2016 at 8:27 PM, babu prasad wrote:
>> Hi,
>>
>> I have configured 2 ignite servers with a heap size of 8G each.
>> Running with backups=1 and primary_sync mode.
>>
>> Ignite servers are being used as a write behind cache for my Aurora database.
>>
>> I am trying to run a load test with 3 clients talking to the remote cache in
>> the 2 ignite servers.
>> All the hosts are in the same availability zone.
>>
>> My clients do a simple put and I calculate time taken for put on the client
>> side.
>>
>> long startTime = System.currentTimeMillis();
>> cache.put(k, c1);
>> long elapsedTime = System.currentTimeMillis() - startTime;
>> System.out.println("Total elapsed timein milliseconds: " + elapsedTime);
>>
>> Here is the latency from the last few requests:
>> Total elapsed timein milliseconds: 31
>> Total elapsed timein milliseconds: 29
>> Total elapsed timein milliseconds: 26
>> Total elapsed timein milliseconds: 28
>> Total elapsed timein milliseconds: 28
>> Total elapsed timein milliseconds: 27
>> Total elapsed timein milliseconds: 27
>> Total elapsed timein milliseconds: 29
>> Total elapsed timein milliseconds: 26
>> Total elapsed timein milliseconds: 26
>> Total elapsed timein milliseconds: 27
>> Total elapsed timein milliseconds: 27
>> Total elapsed timein milliseconds: 28
>> Total elapsed timein milliseconds: 28
>> Total elapsed timein milliseconds: 27
>> Total elapsed timein milliseconds: 26
>> Total elapsed timein milliseconds: 27
>> Total elapsed timein milliseconds: 28
>> Total elapsed timein milliseconds: 27
>> Total elapsed timein milliseconds: 26
>> Total elapsed timein milliseconds: 26
>> Total elapsed timein milliseconds: 29
>> Total elapsed timein milliseconds: 26
>> Total elapsed timein milliseconds: 27
>> Total elapsed timein milliseconds: 26
>> Total elapsed timein milliseconds: 27
>> Total elapsed timein milliseconds: 29
>> Total elapsed timein milliseconds: 27
>> Total elapsed timein milliseconds: 28
>> Total elapsed timein milliseconds: 26
>> Total elapsed timein milliseconds: 27
>> Total elapsed timein milliseconds: 27
>> Total elapsed timein milliseconds: 27
>> Total elapsed timein milliseconds: 29
>>
>> Not sure what is going on here. I am pretty sure I am doing something wrong
>> here.
>>
>>
>> Thanks!
>
issue with 2-node ignite server cluster
I have setup 2 ignite server nodes running on Ubantu 14.X with Java 8, have created a grid and also discovery is set to TcpDiscoveryVmIpFinder and have one more system running on Windows with Java 8 in a client mode. I have modified default ignite config on both the servers to include discoverySpi, gridName... Starting 2-node cluster works fine initially. But when I connect Windows client, one of the server stops after a few minutes and other node display "Failed to send message node may have left the grid" -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/issue-with-2-node-ignite-server-cluster-tp2600.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Alternate way of using DBH2ServerStartup ??
/**
* Start H2 database TCP server in order to access sample in-memory database
from other processes.
*/
public class DbH2ServerStartup {
/** Create table script. */
private static final String CREATE_PERSON_TABLE =
"create table if not exists PERSON(id bigint not null, first_name
varchar(50), last_name varchar(50), PRIMARY KEY(id));";
/** Sample data script. */
private static final String POPULATE_PERSON_TABLE =
"delete from PERSON;\n" +
"insert into PERSON(id, first_name, last_name) values(1, 'Johannes',
'Kepler');\n" +
"insert into PERSON(id, first_name, last_name) values(2, 'Galileo',
'Galilei');\n" +
"insert into PERSON(id, first_name, last_name) values(3, 'Henry',
'More');\n" +
"insert into PERSON(id, first_name, last_name) values(4, 'Polish',
'Brethren');\n" +
"insert into PERSON(id, first_name, last_name) values(5, 'Robert',
'Boyle');\n" +
"insert into PERSON(id, first_name, last_name) values(6, 'Wilhelm',
'Leibniz');";
/**
* Populate sample database.
*
* @throws SQLException if
*/
public static void populateDatabase() throws SQLException {
// Try to connect to database TCP server.
JdbcConnectionPool dataSrc =
JdbcConnectionPool.create("jdbc:mysql://172.17.125.19/security_sample",
"coeuser", "CoeUser@2014");
// Create Person table in database.
RunScript.execute(dataSrc.getConnection(), new
StringReader(CREATE_PERSON_TABLE));
// Populates Person table with sample data in database.
RunScript.execute(dataSrc.getConnection(), new
StringReader(POPULATE_PERSON_TABLE));
}
/**
* Start H2 database TCP server.
*
* @param args Command line arguments, none required.
* @throws IgniteException If start H2 database TCP server failed.
*/
public static void main(String[] args) throws IgniteException {
try {
// Start H2 database TCP server in order to access sample
in-memory database from other processes.
Server.createTcpServer("-tcpDaemon").start();
populateDatabase();
// Try to connect to database TCP server.
JdbcConnectionPool dataSrc =
JdbcConnectionPool.create("jdbc:mysql://172.17.125.19/security_sample",
"coeuser", "CoeUser@2014");
// Create Person table in database.
RunScript.execute(dataSrc.getConnection(), new
StringReader(CREATE_PERSON_TABLE));
// Populates Person table with sample data in database.
RunScript.execute(dataSrc.getConnection(), new
StringReader(POPULATE_PERSON_TABLE));
}
catch (SQLException e) {
throw new IgniteException("Failed to start database TCP server",
e);
}
try {
do {
System.out.println("Type 'q' and press 'Enter' to stop H2
TCP server...");
}
while ('q' != System.in.read());
}
catch (IOException ignored) {
// No-op.
}
}
}
DbH2ServerStartup class is compulsory need to start the server of TCP/Ip
needed to query the examples. But if i wat to query the example form mysql
databse without starting the DBH2 server. How can i do this?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Alternate-way-of-using-DBH2ServerStartup-tp2599.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Help with Ignite-Zeppelin
I was using Amazon EMR. Looks like there 1.4 jars.
Copied over the 1.5 jars, created a new ignite-jdbc.xml and updated the
jdbc url to use the new jdbc url.
Did the trick!
On Sun, Jan 17, 2016 at 3:50 PM, babu prasad wrote:
> Hi,
>
> I have been trying to setup Zeppelin to talk to Apache Ignite, but no
> success.
>
> I have my ignite servers running on remote nodes.
> I keep getting this error.
>
> I followed this documentation to set it up -
> http://apacheignite.gridgain.org/v1.1/docs/data-analysis-with-apache-zeppelin
>
>
> ERROR [2016-01-17 23:44:24,598] ({pool-2-thread-2}
> IgniteSqlInterpreter.java[open]:100) - Can't open connection:
> java.sql.SQLException: Failed to establish connection.
> at
> org.apache.ignite.internal.jdbc.JdbcConnection.isValid(JdbcConnection.java:447)
> at
> org.apache.ignite.internal.jdbc.JdbcConnection.(JdbcConnection.java:123)
> at
> org.apache.ignite.IgniteJdbcDriver.connect(IgniteJdbcDriver.java:347)
> at java.sql.DriverManager.getConnection(DriverManager.java:571)
> at java.sql.DriverManager.getConnection(DriverManager.java:233)
> at
> org.apache.zeppelin.ignite.IgniteSqlInterpreter.open(IgniteSqlInterpreter.java:95)
> at
> org.apache.zeppelin.interpreter.ClassloaderInterpreter.open(ClassloaderInterpreter.java:74)
> at
> org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:68)
> at
> org.apache.zeppelin.interpreter.LazyOpenInterpreter.interpret(LazyOpenInterpreter.java:92)
> at
> org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:276)
> at org.apache.zeppelin.scheduler.Job.run(Job.java:170)
> at
> org.apache.zeppelin.scheduler.FIFOScheduler$1.run(FIFOScheduler.java:118)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class
> org.apache.ignite.internal.client.GridClientDisconnectedException: Latest
> topology update failed.
> at
> org.apache.ignite.internal.client.impl.connection.GridClientTopology.nodes(GridClientTopology.java:335)
> at
> org.apache.ignite.internal.client.impl.GridClientAbstractProjection.projectionNodes(GridClientAbstractProjection.java:312)
> at
> org.apache.ignite.internal.client.impl.GridClientAbstractProjection.balancedNode(GridClientAbstractProjection.java:352)
> at
> org.apache.ignite.internal.client.impl.GridClientAbstractProjection.withReconnectHandling(GridClientAbstractProjection.java:109)
> at
> org.apache.ignite.internal.client.impl.GridClientComputeImpl.executeAsync(GridClientComputeImpl.java:132)
> at
> org.apache.ignite.internal.jdbc.JdbcConnection.isValid(JdbcConnection.java:444)
> ... 18 more
> Caused by: class
> org.apache.ignite.internal.client.GridServerUnreachableException: Failed to
> connect to any of the servers in list: [/127.0.0.1:40075]
> at
> org.apache.ignite.internal.client.impl.connection.GridClientConnectionManagerAdapter.connect(GridClientConnectionManagerAdapter.java:414)
> at
> org.apache.ignite.internal.client.impl.connection.GridClientConnectionManagerAdapter.init(GridClientConnectionManagerAdapter.java:226)
> at
> org.apache.ignite.internal.client.impl.GridClientImpl.tryInitTopology(GridClientImpl.java:498)
> at
> org.apache.ignite.internal.client.impl.GridClientImpl.(GridClientImpl.java:194)
> at
> org.apache.ignite.internal.client.GridClientFactory.start(GridClientFactory.java:58)
> at
> org.apache.ignite.internal.jdbc.JdbcConnection.(JdbcConnection.java:117)
> ... 17 more
> Caused by: java.net.ConnectException: Connection refused
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
> at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:117)
> at
> org.apache.ignite.internal.client.impl.connection.GridClientNioTcpConnection.(GridClientNioTcpConnection.java:217)
> at
> org.apache.ignite.internal.client.impl.connection.GridClientConnectionManagerAdapter.connect(GridClientConnectionManagerAdapter.java:463)
> at
> org.apache.ignite.internal.client.impl.connection.GridClientConnectionManagerAdapter.connect(GridClientConnectionManagerAdapter.java:399)
>
>
>
Help with Ignite-Zeppelin
Hi,
I have been trying to setup Zeppelin to talk to Apache Ignite, but no
success.
I have my ignite servers running on remote nodes.
I keep getting this error.
I followed this documentation to set it up -
http://apacheignite.gridgain.org/v1.1/docs/data-analysis-with-apache-zeppelin
ERROR [2016-01-17 23:44:24,598] ({pool-2-thread-2}
IgniteSqlInterpreter.java[open]:100) - Can't open connection:
java.sql.SQLException: Failed to establish connection.
at
org.apache.ignite.internal.jdbc.JdbcConnection.isValid(JdbcConnection.java:447)
at
org.apache.ignite.internal.jdbc.JdbcConnection.(JdbcConnection.java:123)
at org.apache.ignite.IgniteJdbcDriver.connect(IgniteJdbcDriver.java:347)
at java.sql.DriverManager.getConnection(DriverManager.java:571)
at java.sql.DriverManager.getConnection(DriverManager.java:233)
at
org.apache.zeppelin.ignite.IgniteSqlInterpreter.open(IgniteSqlInterpreter.java:95)
at
org.apache.zeppelin.interpreter.ClassloaderInterpreter.open(ClassloaderInterpreter.java:74)
at
org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:68)
at
org.apache.zeppelin.interpreter.LazyOpenInterpreter.interpret(LazyOpenInterpreter.java:92)
at
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:276)
at org.apache.zeppelin.scheduler.Job.run(Job.java:170)
at
org.apache.zeppelin.scheduler.FIFOScheduler$1.run(FIFOScheduler.java:118)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: class
org.apache.ignite.internal.client.GridClientDisconnectedException: Latest
topology update failed.
at
org.apache.ignite.internal.client.impl.connection.GridClientTopology.nodes(GridClientTopology.java:335)
at
org.apache.ignite.internal.client.impl.GridClientAbstractProjection.projectionNodes(GridClientAbstractProjection.java:312)
at
org.apache.ignite.internal.client.impl.GridClientAbstractProjection.balancedNode(GridClientAbstractProjection.java:352)
at
org.apache.ignite.internal.client.impl.GridClientAbstractProjection.withReconnectHandling(GridClientAbstractProjection.java:109)
at
org.apache.ignite.internal.client.impl.GridClientComputeImpl.executeAsync(GridClientComputeImpl.java:132)
at
org.apache.ignite.internal.jdbc.JdbcConnection.isValid(JdbcConnection.java:444)
... 18 more
Caused by: class
org.apache.ignite.internal.client.GridServerUnreachableException: Failed to
connect to any of the servers in list: [/127.0.0.1:40075]
at
org.apache.ignite.internal.client.impl.connection.GridClientConnectionManagerAdapter.connect(GridClientConnectionManagerAdapter.java:414)
at
org.apache.ignite.internal.client.impl.connection.GridClientConnectionManagerAdapter.init(GridClientConnectionManagerAdapter.java:226)
at
org.apache.ignite.internal.client.impl.GridClientImpl.tryInitTopology(GridClientImpl.java:498)
at
org.apache.ignite.internal.client.impl.GridClientImpl.(GridClientImpl.java:194)
at
org.apache.ignite.internal.client.GridClientFactory.start(GridClientFactory.java:58)
at
org.apache.ignite.internal.jdbc.JdbcConnection.(JdbcConnection.java:117)
... 17 more
Caused by: java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:117)
at
org.apache.ignite.internal.client.impl.connection.GridClientNioTcpConnection.(GridClientNioTcpConnection.java:217)
at
org.apache.ignite.internal.client.impl.connection.GridClientConnectionManagerAdapter.connect(GridClientConnectionManagerAdapter.java:463)
at
org.apache.ignite.internal.client.impl.connection.GridClientConnectionManagerAdapter.connect(GridClientConnectionManagerAdapter.java:399)
Apache Ignite client on AWS Lambda
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!
