How to compile 2.7 release cpp binaries on ubuntu 16.04

[jackluo923]

What is the specific SSL library version dependency to successfully compile
the cpp binaries under Ubuntu 16.04. This particular dependency isn't
mentioned anywhere in the DEVNotes.txt or other documentations. 

It seems like 1.0.2g-1ubuntu4.15 is incompatible on Ubuntu 16.04 with
ignite's source code. 

build error message: 
make[3]: Entering directory
'/tmp/apache-ignite-installation/apache-ignite-2.7.0-bin/platforms/cpp/thin-client'
 
  CXX  src/impl/ssl/secure_socket_client.lo 
In file included from ./src/impl/ssl/ssl_bindings.h:21:0, 
 from src/impl/ssl/secure_socket_client.cpp:27: 
./src/impl/ssl/ssl_bindings.h:135:28: error: expression list treated as
compound expression in initializer [-fpermissive] 
 inline int SSL_library_init() 
^ 
In file included from src/impl/ssl/secure_socket_client.cpp:27:0: 
./src/impl/ssl/ssl_bindings.h:136:17: error: expected ‘,’ or ‘;’ before ‘{’
token 
 { 
 ^ 
In file included from ./src/impl/ssl/ssl_bindings.h:21:0, 
 from src/impl/ssl/secure_socket_client.cpp:27: 
./src/impl/ssl/ssl_bindings.h:144:29: error: variable or field
‘OPENSSL_init_ssl’ declared void 
 inline void SSL_load_error_strings() 
 ^ 
src/impl/ssl/secure_socket_client.cpp: In static member function ‘static
void* ignite::impl::thin::ssl::SecureSocketClient::MakeContext(const
string&, const string&, const string&)’: 
src/impl/ssl/secure_socket_client.cpp:199:35: error:
‘ignite::impl::thin::ssl::OPENSSL_init_ssl’ cannot be used as a function 
 (void)SSL_library_init(); 
   ^ 
src/impl/ssl/secure_socket_client.cpp:201:29: error:
‘ignite::impl::thin::ssl::OPENSSL_init_ssl’ cannot be used as a function 
 SSL_load_error_strings(); 
 ^ 
src/impl/ssl/secure_socket_client.cpp:222:44: error: ‘SSL_CTRL_OPTIONS’ was
not declared in this scope 
 ssl::SSL_CTX_ctrl(ctx, SSL_CTRL_OPTIONS, flags, NULL); 
^~~~ 
src/impl/ssl/secure_socket_client.cpp:222:44: note: suggested alternative:
‘SSL_CTRL_CHAIN’ 
 ssl::SSL_CTX_ctrl(ctx, SSL_CTRL_OPTIONS, flags, NULL); 
^~~~ 
SSL_CTRL_CHAIN 
Makefile:617: recipe for target 'src/impl/ssl/secure_socket_client.lo'
failed 
make[3]: *** [src/impl/ssl/secure_socket_client.lo] Error 1 
make[3]: Leaving directory
'/tmp/apache-ignite-installation/apache-ignite-2.7.0-bin/platforms/cpp/thin-client'
 



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Java server with .net client limitations

[Ilya Kasnacheev]

Hello!

Yes, you can invoke Java services from .net:
https://apacheignite-net.readme.io/docs/calling-java-services

I'm not sure about vice versa, but if it is supported they could notify
your service from Java when there is data update.

Regards,
-- 
Ilya Kasnacheev


пн, 11 мар. 2019 г. в 21:22, IgniteDotnetUser :

> Not sure I understand the ignite services approach. We can invoke something
> from .net on Java servers? Would it give the ability to listen on data
> modifications? Can u pls share some url or documentation on this?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Stream continuous Data from Sql Server to ignite

[Ilya Kasnacheev]

Hello!

Can you please frame it as a small project on Github? I promise to take a
look then.

Regards,
-- 
Ilya Kasnacheev


пн, 11 мар. 2019 г. в 15:55, austin solomon :

> Thanks Ilya,
> I tried implementing your example in below manner but the overridden
> loadCache() is never called.
>
> public class CacheJdbct1Store extends CacheStoreAdapter {
>
> /** Data source. */
> public static final DataSource DATA_SRC =
>
>
> JdbcConnectionPool.create("jdbc:sqlserver://localhost:8067;databaseName=TestDB","**","**");
>
> /** Spring JDBC template. */
> private JdbcTemplate jdbcTemplate;
>
> /**
>  * Constructor.
>  *
>  * @throws IgniteException If failed.
>  */
> public CacheJdbct1Store() throws IgniteException {
> jdbcTemplate = new JdbcTemplate(DATA_SRC);
> }
>
> /** {@inheritDoc} */
> @Override public t1 load(Integer key) {
> System.out.println(">>> Store load [key=" + key + ']');
>
> try {
> return jdbcTemplate.queryForObject("select * from t1", new
> RowMapper() {
> public t1 mapRow(ResultSet rs, int rowNum) throws
> SQLException {
> return new t1(rs.getString(2),
>
> rs.getInt(3),rs.getLong(4),rs.getInt(5),rs.getTimestamp(6),rs.getTimestamp(7));
> }
> }, key);
> }
> catch (EmptyResultDataAccessException ignored) {
> return null;
> }
> }
>
> /** {@inheritDoc} */
> public void write(Cache.Entry entry) {
>  //To Be Implemented
> }
>
> /** {@inheritDoc} */
> @Override public void delete(Object key) {
> System.out.println(">>> Store delete [key=" + key + ']');
> //To Be Implemented
> }
>
> /** {@inheritDoc} */
> @Override public void loadCache(final IgniteBiInClosure
> clo, Object... args) {
> if (args == null || args.length == 0 || args[0] == null)
> throw new CacheLoaderException("Expected entry count parameter
> is not provided.");
>
> int entryCnt = (Integer)args[0];
>
> final AtomicInteger cnt = new AtomicInteger();
>
> jdbcTemplate.query("select * from t1", new RowCallbackHandler() {
> @Override public void processRow(ResultSet rs) throws
> SQLException {
> t1 bic = new t1(rs.getString(1),
>
> rs.getInt(2),rs.getLong(3),rs.getInt(4),rs.getTimestamp(5),rs.getTimestamp(6));
>
> clo.apply(rs.getInt(0), bic);
>
> cnt.incrementAndGet();
> }
> }, entryCnt);
>
> System.out.println(">>> Loaded " + cnt + " values into cache.");
> }
> }
>
>
> Main CLASS:
> Ignite ignite = Ignition.start("JDBCLoadCluster-client.xml");
> IgniteCache cache = ignite.getOrCreateCache("t1");
> cache.loadCache(null);
> System.out.println("Cache load complete");
>
> Please correct me what I am missing in this to load delta data.
>
> Thanks,
> Austin
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Ignite Java server with .net client limitations

[IgniteDotnetUser]

Not sure I understand the ignite services approach. We can invoke something
from .net on Java servers? Would it give the ability to listen on data
modifications? Can u pls share some url or documentation on this?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: adding new primitive type columns to the existing tables (table has data) in Cassandra causes Ignite to raise an exception in Ignite 2.7.0 or 2.8.0 daily build when loading the data from Cassandra

[xmw45688]

The issue was created in Ignite Jira
(https://issues.apache.org/jira/browse/IGNITE-11523).  I don't think that we
need a reproducer.  Instead I point out the implementation logic in the java
class, and the reasons. The previous implementation (2.6) was correct, and
the expected behavior. 




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Java server with .net client limitations

[Ilya Kasnacheev]

Hello!

You can ask your Java backend side to implement Ignite Services with some
defined API, and you can call those services from .Net thick client much
like any native API.

Please consider this approach.

Regards,
-- 
Ilya Kasnacheev


пн, 11 мар. 2019 г. в 20:26, IgniteDotnetUser :

> We have a team that takes care of server part and they work on Java. They
> are
> planning on switching to ignite. We use .net for UI data display. So we are
> kind of stuck with Java on server and .net for UI.
>
> On UI, users generally put some dynamic filters and get the data and the
> grid displaying the data is “live” (It listens to any changes and updates
> the grid accordingly).
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Exception on node startup: Attempted to release write lock while not holding it

[Dmitry Lazurkin]

Thank you, this is https://issues.apache.org/jira/browse/IGNITE-9303

On 3/6/19 7:11 PM, Dmitry Lazurkin wrote:
> Thank you for reply, Ilya.
>
>> Have you tried to start this on Nightly Build? Can you try that?
>
> No, on 2.7.0#20181130-sha1:256ae401. I will try Nightly Build.
>
>> If it still would not work, can you share your DB+wal files?
> I think yes, but it's 15 GB.
>
> On 3/6/19 6:59 PM, Ilya Kasnacheev wrote:
>> Hello!
>>
>> Have you tried to start this on Nightly Build? Can you try that?
>>
>> If it still would not work, can you share your DB+wal files?
>>
>> Regards,
>> -- 
>> Ilya Kasnacheev
>>
>>
>> вт, 5 мар. 2019 г. в 20:37, Dmitry Lazurkin > >:
>>
>> Ignite version: 2.7.0#20181130-sha1:256ae401
>>
>>
>

Re: Ignite Java server with .net client limitations

[IgniteDotnetUser]

We have a team that takes care of server part and they work on Java. They are
planning on switching to ignite. We use .net for UI data display. So we are
kind of stuck with Java on server and .net for UI. 

On UI, users generally put some dynamic filters and get the data and the
grid displaying the data is “live” (It listens to any changes and updates
the grid accordingly). 





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Java server with .net client limitations

[Pavel Tupitsyn]

> You can do that on a Linux server using Mono

Mono is not officially supported, and I won't recommend it.
Use .NET Core instead to run Ignite.NET on Linux.

>  some pre-defined filters in ignite which just accept some parameters and
are understood by both Java and .net

We actually had something like this in mind.
A predicate builder of some sort that produces and expression tree which
can be executed by Java server node.
This will allow predicates from any language and client.
But this never got implemented.

Can you please describe your use case in more detail? Why is it a problem
to run Ignite.NET server nodes? They don't have any limitations.

On Mon, Mar 11, 2019 at 7:40 PM Stephen Darlington <
stephen.darling...@gridgain.com> wrote:

> I’m not sure what resolution you have in mind? The fundamental problem is
> that the JVM can’t run .net code and vice versa.
>
> Ignite solves that with a .net server that integrates with the usual Java
> server. The other alternative would be to have a Java client.
>
> Regards,
> Stephen
>
> > On 11 Mar 2019, at 16:09, IgniteDotnetUser 
> wrote:
> >
> > Thank you for the reply. Having .net with mono would call for a lot of
> work
> > on our side.
> >
> > Just wondering, if there were some pre-defined filters in ignite which
> just
> > accept some parameters and are understood by both Java and .net, that
> would
> > probably help?
> >
> > Also, is this going to be a limitation with ignite for mixed-platform
> > implementations or is this going to be resolved soon?
> >
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
>
>

Re: Ignite Java server with .net client limitations

[Stephen Darlington]

I’m not sure what resolution you have in mind? The fundamental problem is that 
the JVM can’t run .net code and vice versa.

Ignite solves that with a .net server that integrates with the usual Java 
server. The other alternative would be to have a Java client.

Regards,
Stephen

> On 11 Mar 2019, at 16:09, IgniteDotnetUser  wrote:
> 
> Thank you for the reply. Having .net with mono would call for a lot of work
> on our side.
> 
> Just wondering, if there were some pre-defined filters in ignite which just
> accept some parameters and are understood by both Java and .net, that would
> probably help?
> 
> Also, is this going to be a limitation with ignite for mixed-platform
> implementations or is this going to be resolved soon?
> 
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Java server with .net client limitations

[IgniteDotnetUser]

Thank you for the reply. Having .net with mono would call for a lot of work
on our side.

Just wondering, if there were some pre-defined filters in ignite which just
accept some parameters and are understood by both Java and .net, that would
probably help?

Also, is this going to be a limitation with ignite for mixed-platform
implementations or is this going to be resolved soon?




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Java server with .net client limitations

[Stephen Darlington]

Invoke and the continuous query filters both mean sending code from the client 
to the server. The Java server does not, of course, understand the CLR.

If you want to run .net code on your server, you need to run the ignite.net 
server. You can do that on a Linux server using Mono.

Regards,
Stephen

> On 11 Mar 2019, at 15:22, IgniteDotnetUser  wrote:
> 
> I am trying a POC with ignite. I have a Java ignite server and want to use
> ignite.net on the client side on the UI. I have come across a few major
> limitations and want to make sure I am not missing something w.r.t these:
> 
> Thin clients:
> 1) thinclients do not support continuous queries. 
> 
> Thick clients:
> 1) there is no way to have a Java ignite server with .net thick client if we
> want to use continuous query with filter.
> 2) cache invokes are not possible.
> 
> My usecase is pretty simple. I want to be able to request filtered data from
> Java ignite server and be able to listen to updates on it.
> 
> Please let me know if I am missing something and if the above are possible.
> 
> If not, can you please share if they are planned for a future release. If
> you can share the release date as well, that would be great.
> 
> Is there any workaround in the mean time that can be used?
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite Java server with .net client limitations

[IgniteDotnetUser]

I am trying a POC with ignite. I have a Java ignite server and want to use
ignite.net on the client side on the UI. I have come across a few major
limitations and want to make sure I am not missing something w.r.t these:

Thin clients:
1) thinclients do not support continuous queries. 

Thick clients:
1) there is no way to have a Java ignite server with .net thick client if we
want to use continuous query with filter.
2) cache invokes are not possible.

My usecase is pretty simple. I want to be able to request filtered data from
Java ignite server and be able to listen to updates on it.

Please let me know if I am missing something and if the above are possible.

If not, can you please share if they are planned for a future release. If
you can share the release date as well, that would be great.

Is there any workaround in the mean time that can be used?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Stream continuous Data from Sql Server to ignite

[austin solomon]

Thanks Ilya,
I tried implementing your example in below manner but the overridden
loadCache() is never called.

public class CacheJdbct1Store extends CacheStoreAdapter {

/** Data source. */
public static final DataSource DATA_SRC =
   
JdbcConnectionPool.create("jdbc:sqlserver://localhost:8067;databaseName=TestDB","**","**");

/** Spring JDBC template. */
private JdbcTemplate jdbcTemplate;

/**
 * Constructor.
 *
 * @throws IgniteException If failed.
 */
public CacheJdbct1Store() throws IgniteException {
jdbcTemplate = new JdbcTemplate(DATA_SRC);
}

/** {@inheritDoc} */
@Override public t1 load(Integer key) {
System.out.println(">>> Store load [key=" + key + ']');

try {
return jdbcTemplate.queryForObject("select * from t1", new
RowMapper() {
public t1 mapRow(ResultSet rs, int rowNum) throws
SQLException {
return new t1(rs.getString(2),
rs.getInt(3),rs.getLong(4),rs.getInt(5),rs.getTimestamp(6),rs.getTimestamp(7));
}
}, key);
}
catch (EmptyResultDataAccessException ignored) {
return null;
}
}

/** {@inheritDoc} */
public void write(Cache.Entry entry) {
 //To Be Implemented
}

/** {@inheritDoc} */
@Override public void delete(Object key) {
System.out.println(">>> Store delete [key=" + key + ']');
//To Be Implemented
}

/** {@inheritDoc} */
@Override public void loadCache(final IgniteBiInClosure
clo, Object... args) {
if (args == null || args.length == 0 || args[0] == null)
throw new CacheLoaderException("Expected entry count parameter
is not provided.");

int entryCnt = (Integer)args[0];

final AtomicInteger cnt = new AtomicInteger();

jdbcTemplate.query("select * from t1", new RowCallbackHandler() {
@Override public void processRow(ResultSet rs) throws
SQLException {
t1 bic = new t1(rs.getString(1),
rs.getInt(2),rs.getLong(3),rs.getInt(4),rs.getTimestamp(5),rs.getTimestamp(6));

clo.apply(rs.getInt(0), bic);

cnt.incrementAndGet();
}
}, entryCnt);

System.out.println(">>> Loaded " + cnt + " values into cache.");
}
}


Main CLASS:
Ignite ignite = Ignition.start("JDBCLoadCluster-client.xml");
IgniteCache cache = ignite.getOrCreateCache("t1");
cache.loadCache(null);
System.out.println("Cache load complete"); 

Please correct me what I am missing in this to load delta data.

Thanks,
Austin



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

QueryEntities not returning all the fields available in cache - 2.6 version

[Kamlesh.Joshi]

Hi Igniters,

Am trying to retrieve Cache metadata i.e. its field name and 
data type. But facing one weird issue, the metadata is returning valid response 
for some caches and invalid for some. Am giving my cache configuration for 
reference. The cluster is up and running for some time now, and we have not 
altered/added any fields to any specific cache (aware about one existing issue 
if you alter cache then its metadata is not updated and can't be retrieved from 
QueryEntities). Any help or pointers on this would be appreciated :
e.g. for below cache its returning only one field i.e. associateId. However, it 
is supposed to return both the fields mentioned in 'fields' property below.

















mappingId




















Thanks and Regards,
Kamlesh Joshi

"Confidentiality Warning: This message and any attachments are intended only 
for the use of the intended recipient(s). 
are confidential and may be privileged. If you are not the intended recipient. 
you are hereby notified that any 
review. re-transmission. conversion to hard copy. copying. circulation or other 
use of this message and any attachments is 
strictly prohibited. If you are not the intended recipient. please notify the 
sender immediately by return email. 
and delete this message and any attachments from your system.

Virus Warning: Although the company has taken reasonable precautions to ensure 
no viruses are present in this email. 
The company cannot accept responsibility for any loss or damage arising from 
the use of this email or attachment."

Re: cache is moved to a read-only state

[Ilya Kasnacheev]

Hello!

You can't change config, since cache is started its config cannot be
changed.

Can you share logs from all nodes?

Regards,
-- 
Ilya Kasnacheev


пн, 11 мар. 2019 г. в 13:11, Aat :

> No - All my servers was available.
> I change cache config.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: cache is moved to a read-only state

[Aat]

No - All my servers was available.
I change cache config.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failed to start grid: com/google/common/base/Preconditions

[Ilya Kasnacheev]

Hello!

Can you state what's on your classpath? As far as my understanding goes we
don't even ship Ignite-Hadoop in our main redistributable.

Regards,
-- 
Ilya Kasnacheev


пн, 11 мар. 2019 г. в 12:08, Mehdi Seydali :

> ignite-hadoop was in lib path of ignite but i aslo copied other optional
> folder module to lib folder and i have encounter another error just like
> below:
> [12:34:14]__  
> [12:34:14]   /  _/ ___/ |/ /  _/_  __/ __/
> [12:34:14]  _/ // (7 7// /  / / / _/
> [12:34:14] /___/\___/_/|_/___/ /_/ /___/
> [12:34:14]
> [12:34:14] ver. 2.6.0#20180710-sha1:669feacc
> [12:34:14] 2018 Copyright(C) Apache Software Foundation
> [12:34:14]
> [12:34:14] Ignite documentation: http://ignite.apache.org
> [12:34:14]
> [12:34:14] Quiet mode.
> [12:34:14]   ^-- Logging to file
> '/usr/local/apache-ignite-fabric-2.6.0-bin/work/log/ignite-96498dcf.log'
> [12:34:14]   ^-- Logging by 'Log4JLogger [quiet=true,
> config=/usr/local/apache-ignite-fabric-2.6.0-bin/config/ignite-log4j.xml]'
> [12:34:14]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false
> or "-v" to ignite.{sh|bat}
> [12:34:14]
> [12:34:14] OS: Linux 4.15.0-46-generic amd64
> [12:34:14] VM information: Java(TM) SE Runtime Environment
> 1.8.0_192-ea-b04 Oracle Corporation Java HotSpot(TM) 64-Bit Server VM
> 25.192-b04
> [12:34:14] Configured plugins:
> [12:34:14]   ^-- Ignite Native I/O Plugin [Direct I/O]
> [12:34:14]   ^-- Copyright(C) Apache Software Foundation
> [12:34:14]
> [12:34:14] Configured failure handler: [hnd=StopNodeOrHaltFailureHandler
> [tryStop=false, timeout=0]]
> [12:34:14] Message queue limit is set to 0 which may lead to potential
> OOMEs when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due
> to message queues growth on sender and receiver sides.
> [12:34:14] Security status [authentication=off, tls/ssl=off]
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/usr/local/apache-ignite-fabric-2.6.0-bin/libs/ignite-rest-http/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/usr/local/apache-ignite-fabric-2.6.0-bin/libs/ignite-yarn/ignite-yarn-2.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/usr/local/apache-ignite-fabric-2.6.0-bin/libs/ignite-zookeeper/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> [2019-03-11 12:34:15,475][ERROR][main][IgniteKernal] Exception during
> start processors, node will be stopped and close connections
> java.lang.NoClassDefFoundError: com/ctc/wstx/io/InputBootstrapper
> at
> org.apache.ignite.internal.processors.hadoop.impl.HadoopUtils.safeCreateConfiguration(HadoopUtils.java:334)
> at
> org.apache.ignite.internal.processors.hadoop.impl.delegate.HadoopBasicFileSystemFactoryDelegate.start(HadoopBasicFileSystemFactoryDelegate.java:129)
> at
> org.apache.ignite.internal.processors.hadoop.impl.delegate.HadoopCachingFileSystemFactoryDelegate.start(HadoopCachingFileSystemFactoryDelegate.java:58)
> at
> org.apache.ignite.internal.processors.hadoop.impl.delegate.HadoopIgfsSecondaryFileSystemDelegateImpl.start(HadoopIgfsSecondaryFileSystemDelegateImpl.java:413)
> at
> org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem.start(IgniteHadoopIgfsSecondaryFileSystem.java:276)
> at
> org.apache.ignite.internal.processors.igfs.IgfsImpl.(IgfsImpl.java:185)
> at
> org.apache.ignite.internal.processors.igfs.IgfsContext.(IgfsContext.java:102)
> at
> org.apache.ignite.internal.processors.igfs.IgfsProcessor.start(IgfsProcessor.java:116)
> at
> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1739)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:990)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2014)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1723)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1151)
> at
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1069)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:955)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:854)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:724)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:693)
> at org.apache.ignite.Ignition.start(Ignition.java:352)
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:301)
> Caused by: java.lang.ClassNotFoundException:
> com.ctc.wstx.io.InputBootstrapper
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   

Re: Failed to start grid: com/google/common/base/Preconditions

[Mehdi Seydali]

ignite-hadoop was in lib path of ignite but i aslo copied other optional
folder module to lib folder and i have encounter another error just like
below:
[12:34:14]__  
[12:34:14]   /  _/ ___/ |/ /  _/_  __/ __/
[12:34:14]  _/ // (7 7// /  / / / _/
[12:34:14] /___/\___/_/|_/___/ /_/ /___/
[12:34:14]
[12:34:14] ver. 2.6.0#20180710-sha1:669feacc
[12:34:14] 2018 Copyright(C) Apache Software Foundation
[12:34:14]
[12:34:14] Ignite documentation: http://ignite.apache.org
[12:34:14]
[12:34:14] Quiet mode.
[12:34:14]   ^-- Logging to file
'/usr/local/apache-ignite-fabric-2.6.0-bin/work/log/ignite-96498dcf.log'
[12:34:14]   ^-- Logging by 'Log4JLogger [quiet=true,
config=/usr/local/apache-ignite-fabric-2.6.0-bin/config/ignite-log4j.xml]'
[12:34:14]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false
or "-v" to ignite.{sh|bat}
[12:34:14]
[12:34:14] OS: Linux 4.15.0-46-generic amd64
[12:34:14] VM information: Java(TM) SE Runtime Environment 1.8.0_192-ea-b04
Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.192-b04
[12:34:14] Configured plugins:
[12:34:14]   ^-- Ignite Native I/O Plugin [Direct I/O]
[12:34:14]   ^-- Copyright(C) Apache Software Foundation
[12:34:14]
[12:34:14] Configured failure handler: [hnd=StopNodeOrHaltFailureHandler
[tryStop=false, timeout=0]]
[12:34:14] Message queue limit is set to 0 which may lead to potential
OOMEs when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due
to message queues growth on sender and receiver sides.
[12:34:14] Security status [authentication=off, tls/ssl=off]
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/usr/local/apache-ignite-fabric-2.6.0-bin/libs/ignite-rest-http/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/usr/local/apache-ignite-fabric-2.6.0-bin/libs/ignite-yarn/ignite-yarn-2.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/usr/local/apache-ignite-fabric-2.6.0-bin/libs/ignite-zookeeper/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
[2019-03-11 12:34:15,475][ERROR][main][IgniteKernal] Exception during start
processors, node will be stopped and close connections
java.lang.NoClassDefFoundError: com/ctc/wstx/io/InputBootstrapper
at
org.apache.ignite.internal.processors.hadoop.impl.HadoopUtils.safeCreateConfiguration(HadoopUtils.java:334)
at
org.apache.ignite.internal.processors.hadoop.impl.delegate.HadoopBasicFileSystemFactoryDelegate.start(HadoopBasicFileSystemFactoryDelegate.java:129)
at
org.apache.ignite.internal.processors.hadoop.impl.delegate.HadoopCachingFileSystemFactoryDelegate.start(HadoopCachingFileSystemFactoryDelegate.java:58)
at
org.apache.ignite.internal.processors.hadoop.impl.delegate.HadoopIgfsSecondaryFileSystemDelegateImpl.start(HadoopIgfsSecondaryFileSystemDelegateImpl.java:413)
at
org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem.start(IgniteHadoopIgfsSecondaryFileSystem.java:276)
at
org.apache.ignite.internal.processors.igfs.IgfsImpl.(IgfsImpl.java:185)
at
org.apache.ignite.internal.processors.igfs.IgfsContext.(IgfsContext.java:102)
at
org.apache.ignite.internal.processors.igfs.IgfsProcessor.start(IgfsProcessor.java:116)
at
org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1739)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:990)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2014)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1723)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1151)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1069)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:955)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:854)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:724)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:693)
at org.apache.ignite.Ignition.start(Ignition.java:352)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:301)
Caused by: java.lang.ClassNotFoundException:
com.ctc.wstx.io.InputBootstrapper
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 20 more
[2019-03-11 12:34:15,478][ERROR][main][IgniteKernal] Got exception while
starting (will rollback startup routine).
java.lang.NoClassDefFoundError: com/ctc/wstx/io/InputBootstrapper
at

Re: GridTimeoutProcessor - Timeout has occurred - Too frequent messages

[userx]

Hi Ivan,

Thanks for the reply. I totally buy your point that these messages are not
bad. What I wanted to understand  basically was the role of the following
GridTimeOut objects

1) CancelableTask 
2) GridCommunicationMessageSet 
3) CacheContinuousQueryManager$BackupCleaner 

There is no documentation available in the class for the above three
classes. So was just trying to understand the role of each of them.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: GridTimeoutProcessor - Timeout has occurred - Too frequent messages

[Павлухин Иван]

Hi,

There is nothing bad with message you see. GridTimeoutProcessor is
used internally by Ignite for scheduling a task execution after a
delay. Debug message "Timeout has occurred" is logged every time
scheduling delay has ended. It is a debug message and a purpose of it
is checking that arbitrary task was executed by a timeout processor.

сб, 9 мар. 2019 г. в 08:33, userx :
>
> Hi,
>
> Any thoughts on  the same.
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/



-- 
Best regards,
Ivan Pavlukhin

Re: Can I update specific field of a binaryobject

[Ilya Kasnacheev]

Hello!

You can do cache.invoke() with a callback that will update a single field
in an object. It will be sent to a specific node in cluster and object in
question will not be transferred via network, but processed locally.

Note that UPDATE will probably only send request to node containing
relevant key if that is specified, and not broadcast it.

Regards,
-- 
Ilya Kasnacheev


пт, 8 мар. 2019 г. в 11:28, BinaryTree :

> Hi Igniters -
>
> As far as I am known, igniteCache.put(K, V) will replace the value of K
> with V, but sometimes I just would like to update a specific field of V
> instead of the whole object.
> I know that I can update the specific field via
> igniteCache.query(SqlFieldsQuery),  but how-ignite-sql-works
>  writes
> that ignite will generate SELECT queries internally before UPDATE or DELETE
> a set of records, so it may not be as good as igniteCache.put(K, V), so is
> there a way can update a specific field without QUERY?
>
>

Re: cache is moved to a read-only state

[Ilya Kasnacheev]

Hello!

As far as I can see this should happen if you lose two server nodes at the
same time. Did this happen?

Regards,
-- 
Ilya Kasnacheev


пт, 8 мар. 2019 г. в 18:46, Aat :

> visor> cache -slp -c=marketData
> Lost partitions for cache: marketData (12)
> +=+
> | Interval |Partitions|
> +=+
> | 86-816   | 86, 115, 241, 469, 632, 677, 719, 781, 791, 816, |
> | 892-1014 | 892, 1014|
> +-+
> visor>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Ignite traffic isn't even in production environment

[Ilya Kasnacheev]

Hello!

Once cache is created its configuration can't be changed, this including
number of partitions. You can only create a new one, move over data.

Regards,
-- 
Ilya Kasnacheev


пт, 8 мар. 2019 г. в 05:27, Justin Ji :

> Ilya -
>
> Thank for your reply, you have helped me many times, thank you again.
>
> Q: What's the difference between chart 1 and chart 2?
> A: Please ignore chart 2?
>
> Another question,  is there a convenient way to increase the partition
> number without losing the data?
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: adding new primitive type columns to the existing tables (table has data) in Cassandra causes Ignite to raise an exception in Ignite 2.7.0 or 2.8.0 daily build when loading the data from Cassandra

[Ilya Kasnacheev]

Hello!

It would be nice if you created a ticket against Apache Ignite JIRA
regarding this behavior. It would be extra nice if you pdovide a reproducer.

Regards,
-- 
Ilya Kasnacheev


пн, 11 мар. 2019 г. в 09:04, xmw45688 :

> Hi All,
>
> Adding new primitive type columns to the existing tables (table has data)
> in
> Cassandra causes Ignite to raise an exception (see below) in Ignite 2.7.0
> or
> 2.8.0 nightly build when loading the data from Cassandra into Ignite Cache
> store.   This works before Ignite 2.6, and even
> apache-ignite-fabric-2.7.0.20180918 nightly build.  The assumption seems
> not
> correct because both Ignite and Cassandra are (key, value) store.
>
> In fact, SQLLINE tool, we don't need to insert into primitive value, see
> the
> example blow
> CREATE TABLE aa (col1 int PRIMARY KEY, col2 double );
> INSERT INTO aa(col1) VALUES (1);
> SELECT * FROM aa;
>
> 0: jdbc:ignite:thin://localhost> select * from aa;
> +++
> |  COL1  |  COL2  |
> +++
> | 1  | null   |
> +++
> 1 row selected (0.052 seconds)
> 0: jdbc:ignite:thin://localhost>
>
>
> [2019-03-11
>
> 09:44:34,352][ERROR][cassandra-cache-loader-#61%ignite-procurant-purchase-order-cluster%][CassandraCacheStore]
> Failed to build Ignite value object from provided Cassandra row
> java.lang.IllegalArgumentException: Can't cast null value from Cassandra
> table column 'suppliertotamt' to double value used in domain object model
> at
>
> org.apache.ignite.cache.store.cassandra.common.PropertyMappingHelper.getCassandraColumnValue(PropertyMappingHelper.java:169)
> at
>
> org.apache.ignite.cache.store.cassandra.persistence.PojoField.setValueFromRow(PojoField.java:205)
> at
>
> org.apache.ignite.cache.store.cassandra.persistence.PersistenceController.buildObject(PersistenceController.java:405)
> at
>
> org.apache.ignite.cache.store.cassandra.persistence.PersistenceController.buildValueObject(PersistenceController.java:227)
> at
>
> org.apache.ignite.cache.store.cassandra.session.LoadCacheCustomQueryWorker$1.process(LoadCacheCustomQueryWorker.java:107)
> at
>
> org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.execute(CassandraSessionImpl.java:402)
> at
>
> org.apache.ignite.cache.store.cassandra.session.LoadCacheCustomQueryWorker.call(LoadCacheCustomQueryWorker.java:81)
> at
>
> org.apache.ignite.cache.store.cassandra.session.LoadCacheCustomQueryWorker.call(LoadCacheCustomQueryWorker.java:35)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> [2019-03-11
>
> 09:44:34,360][ERROR][cassandra-cache-loader-#61%ignite-procurant-purchase-order-cluster%][CassandraCacheStore]
> Failed to execute Cassandra loadCache operation
> class org.apache.ignite.IgniteException: Failed to execute Cassandra
> loadCache operation
> at
>
> org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.execute(CassandraSessionImpl.java:415)
> at
>
> org.apache.ignite.cache.store.cassandra.session.LoadCacheCustomQueryWorker.call(LoadCacheCustomQueryWorker.java:81)
> at
>
> org.apache.ignite.cache.store.cassandra.session.LoadCacheCustomQueryWorker.call(LoadCacheCustomQueryWorker.java:35)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: class org.apache.ignite.IgniteException: Failed to build Ignite
> value object from provided Cassandra row
> at
>
> org.apache.ignite.cache.store.cassandra.session.LoadCacheCustomQueryWorker$1.process(LoadCacheCustomQueryWorker.java:112)
> at
>
> org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.execute(CassandraSessionImpl.java:402)
> ... 6 more
> Caused by: java.lang.IllegalArgumentException: Can't cast null value from
> Cassandra table column 'suppliertotamt' to double value used in domain
> object model
> at
>
> org.apache.ignite.cache.store.cassandra.common.PropertyMappingHelper.getCassandraColumnValue(PropertyMappingHelper.java:169)
> at
>
> org.apache.ignite.cache.store.cassandra.persistence.PojoField.setValueFromRow(PojoField.java:205)
> at
>
> 

Re: Stream continuous Data from Sql Server to ignite

[Ilya Kasnacheev]

Hello!

https://apacheignite.readme.io/docs/data-loading#ignitecacheloadcache -
right here you have example of CacheStore parametrized with# of entries to
load (but it could just as well be delta).

Regards,
-- 
Ilya Kasnacheev


чт, 7 мар. 2019 г. в 21:06, austin solomon :

> Hi Ilya,
>
> Thanks for your response.
>
> It would be helpful if you provide me a sample example or a code snippet.
>
> What all parameters I need to pass?
>
> Thanks
> Austin
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Access a cache loaded by DataStreamer with SQL

[Ilya Kasnacheev]

Hello!

Can you perhaps post your config and code? Much easier than writing my own
boilerplate.

Regards,
-- 
Ilya Kasnacheev


пт, 8 мар. 2019 г. в 00:36, Mike Needham :

> Would it be possible for someone to provide a sample that uses the
> DataStreamer for multiple large caches and the resulting caches are
> queryable from ODBC tools like Tableau and DBeaver?  I can get one to work,
> but cannot get the cache naming to work for a second one.
>
> On Thu, Mar 7, 2019 at 7:53 AM Ilya Kasnacheev 
> wrote:
>
>> Hello!
>>
>> JDBC with SET STREAMING ON should work reasonably well. You could also
>> use CacheStore.
>>
>> With .Net I guess you will have to stick to DataStreamer & learn how to
>> integrate it with Indexing properly. Or use JDBC from .Net.
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> чт, 7 мар. 2019 г. в 16:31, Mike Needham :
>>
>>> Is that the most efficient way to load millions of rows from a database
>>> table into a cache? I guess I am not seeing how this would work for
>>> millions of rows in the source database.  That also appears to be a JAVA
>>> only solution and it would be preferable to have it be usable for .NET as
>>> well as java and hopefully python.
>>>
>>> On Thu, Mar 7, 2019 at 6:55 AM Ilya Kasnacheev <
>>> ilya.kasnach...@gmail.com> wrote:
>>>
 Hello!

 What prevents you from reading rows from DB and feeding them to JDBC
 prepared statement?

 Regards,
 --
 Ilya Kasnacheev


 чт, 7 мар. 2019 г. в 15:51, Mike Needham :

> And what if the data is already in a database table?  I do not want to
> read from the table to write to a file to load a cache.
>
> On Tue, Mar 5, 2019 at 4:06 AM Ilya Kasnacheev <
> ilya.kasnach...@gmail.com> wrote:
>
>> Hello!
>>
>> The preferred approach is to use Thin JDBC client:
>> https://apacheignite-sql.readme.io/docs/jdbc-driver
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> пн, 4 мар. 2019 г. в 19:39, Mike Needham :
>>
>>> Thanks for the links,  If SET STREAMING ON is the preferred method,
>>> how would you do this in code rather than from a file with all the 
>>> insert
>>> statements.
>>>
>>> On Mon, Mar 4, 2019 at 1:44 AM Ilya Kasnacheev <
>>> ilya.kasnach...@gmail.com> wrote:
>>>
 Hello!

 You can see at this page:
 https://apacheignite-sql.readme.io/docs/sql-and-key-value-usage

 And then substitite cache.put() with addData() and cache name will
 be SQL_PUBLIC_{table name in caps}

 There are not many examples since this is being discouraged in
 favor of SET STREAMING ON, actually:
 https://apacheignite-sql.readme.io/docs/set

 Regards,
 --
 Ilya Kasnacheev


 пт, 1 мар. 2019 г. в 22:48, Mike Needham :

> I have looked at the documentation and the code samples and
> nothing is doing what I am trying to do.  I want to be able to use the
> datastreamer to load 3 or 4 TABLES in a cache for an application that 
> we
> use.  If I create the tables using a create table syntax how do 
> attach a
> datastreamer to the different caches if the cache name is PUBLIC for 
> all of
> them?
>
> On Thu, Feb 28, 2019 at 8:13 AM Ilya Kasnacheev <
> ilya.kasnach...@gmail.com> wrote:
>
>> Hello!
>>
>> I have linked the documentation page, there are also some code
>> examples in distribution.
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> чт, 28 февр. 2019 г. в 17:10, Mike Needham :
>>
>>> Is there any examples that show the steps to do this correctly?
>>> I stumbled upon this but have no idea if it is the best way to do 
>>> this
>>>
>>> On Thu, Feb 28, 2019 at 6:27 AM Ilya Kasnacheev <
>>> ilya.kasnach...@gmail.com> wrote:
>>>
 Hello!

 There's no restriction on cache name but setting it up for the
 first time may be tricky indeed.

 Regards,
 --
 Ilya Kasnacheev


 ср, 27 февр. 2019 г. в 19:48, needbrew99 :

> OK, was able to get it working.  Apparently the cache name has
> to be PUBLIC
> and it will create a table based on the object definition that
> I have.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

>>>
>>> --
>>> *Some days it just not worth chewing through the restraints*
>>>
>>
>
> --
> *Some days it just not worth chewing through the 

Re: views in ignite

[Ilya Kasnacheev]

Hello!

Views are not supported at the moment.

Regards,
-- 
Ilya Kasnacheev


пн, 11 мар. 2019 г. в 05:43, Clay Teahouse :

> Hello All,
>
> Is it possible to define database/table views in ingite?
>
> thanks
> Clay
>

Re: Failed to start grid: com/google/common/base/Preconditions

[Ilya Kasnacheev]

Hello!

I think that you need to add ignite-hadoop from libs/optional to libs/,
probably other modules as well.

Regards,
-- 
Ilya Kasnacheev


пт, 8 мар. 2019 г. в 09:44, mehdi sey :

> hi. i want to start ignite node with a configuration name as
> example-igfs.xml. i have alter this configuration for using IGFS as cache
> layer for HDFS. but when i execute the below command  for start ignite node
> i encounter with error:
> /usr/local/apache-ignite-fabric-2.6.0-bin/bin/ignite.sh
>
> /usr/local/apache-ignite-fabric-2.6.0-bin/examples/config/filesystem/example-igfs.xml
>
> but after executing above command i will encounter below error:
> /  _/ ___/ |/ /  _/_  __/ __/
> [09:57:48]  _/ // (7 7// /  / / / _/
> [09:57:48] /___/\___/_/|_/___/ /_/ /___/
> [09:57:48]
> [09:57:48] ver. 2.6.0#20180710-sha1:669feacc
> [09:57:48] 2018 Copyright(C) Apache Software Foundation
> [09:57:48]
> [09:57:48] Ignite documentation: http://ignite.apache.org
> [09:57:48]
> [09:57:48] Quiet mode.
> [09:57:48]   ^-- Logging to file
> '/usr/local/apache-ignite-fabric-2.6.0-bin/work/log/ignite-246509e8.0.log'
> [09:57:48]   ^-- Logging by 'JavaLogger [quiet=true, config=null]'
> [09:57:48]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false
> or "-v" to ignite.{sh|bat}
> [09:57:48]
> [09:57:48] OS: Linux 4.15.0-43-generic amd64
> [09:57:48] VM information: Java(TM) SE Runtime Environment 1.8.0_192-ea-b04
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.192-b04
> [09:57:48] Configured plugins:
> [09:57:48]   ^-- None
> [09:57:48]
> [09:57:48] Configured failure handler: [hnd=StopNodeOrHaltFailureHandler
> [tryStop=false, timeout=0]]
> [09:57:48] Message queue limit is set to 0 which may lead to potential
> OOMEs
> when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to
> message queues growth on sender and receiver sides.
> [09:57:48] Security status [authentication=off, tls/ssl=off]
> [09:57:49,412][SEVERE][main][IgniteKernal] Exception during start
> processors, node will be stopped and close connections
> java.lang.NoClassDefFoundError: com/google/common/base/Preconditions
> at
>
> org.apache.hadoop.conf.Configuration$DeprecationDelta.(Configuration.java:361)
> at
>
> org.apache.hadoop.conf.Configuration$DeprecationDelta.(Configuration.java:374)
> at
> org.apache.hadoop.conf.Configuration.(Configuration.java:456)
> at
>
> org.apache.ignite.internal.processors.hadoop.impl.HadoopUtils.safeCreateConfiguration(HadoopUtils.java:334)
> at
>
> org.apache.ignite.internal.processors.hadoop.impl.delegate.HadoopBasicFileSystemFactoryDelegate.start(HadoopBasicFileSystemFactoryDelegate.java:129)
> at
>
> org.apache.ignite.internal.processors.hadoop.impl.delegate.HadoopCachingFileSystemFactoryDelegate.start(HadoopCachingFileSystemFactoryDelegate.java:58)
> at
>
> org.apache.ignite.internal.processors.hadoop.impl.delegate.HadoopIgfsSecondaryFileSystemDelegateImpl.start(HadoopIgfsSecondaryFileSystemDelegateImpl.java:413)
> at
>
> org.apache.ignite.hadoop.fs.IgniteHadoopIgfsSecondaryFileSystem.start(IgniteHadoopIgfsSecondaryFileSystem.java:276)
> at
>
> org.apache.ignite.internal.processors.igfs.IgfsImpl.(IgfsImpl.java:185)
> at
>
> org.apache.ignite.internal.processors.igfs.IgfsContext.(IgfsContext.java:102)
> at
>
> org.apache.ignite.internal.processors.igfs.IgfsProcessor.start(IgfsProcessor.java:116)
> at
>
> org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1739)
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:990)
> at
>
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2014)
> at
>
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1723)
> at
> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1151)
> at
>
> org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1069)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:955)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:854)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:724)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:693)
> at org.apache.ignite.Ignition.start(Ignition.java:352)
> at
>
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:301)
> Caused by: java.lang.ClassNotFoundException:
> com.google.common.base.Preconditions
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 23 more
> [09:57:49,414][SEVERE][main][IgniteKernal] Got exception while starting
> (will rollback startup routine).
> 

Transactions stuck after tearing down cluster

[Ariel Tubaltsev]

I have in-memory cluster of 3 nodes (2.4), replicated mode, transactional
caches.
There is a client sending transactions to the cluster.

1. I bring down all 3 server nodes.
2. Bring all of them back.
3. Client sends some transactions  - it's stuck, no visible progress

Logs show that the client is still using an old topology version -
163575049, when servers are using a new one - 5.
Are there any additional steps to take on the client side after reconnect,
waiting period?

DEBUG GridDhtColocatedCache:454 -  Client topology version mismatch,
need remap lock request [reqTopVer=AffinityTopologyVersion [topVer=5,
minorTopVer=0], locTopVer=AffinityTopologyVersion [topVer=5, minorTopVer=1],
req=GridNearLockRequest [topVer=AffinityTopologyVersion [topVer=5,
minorTopVer=0], miniId=525, dhtVers=[null],
subjId=f00f8691-8dcf-4919-aaff-3c1f25f1b757, taskNameHash=0, createTtl=-1,
accessTtl=-1, flags=3, filter=null, super=GridDistributedLockRequest
[nodeId=f00f8691-8dcf-4919-aaff-3c1f25f1b757, nearXidVer=GridCacheVersion
[topVer=163575049, order=1552095656672, nodeOrder=5], threadId=221,
futId=20fc9106961-a0d19da2-fba4-4805-89dc-ae1195ebb183, timeout=0,
isInTx=true, isInvalidate=false, isRead=false, isolation=SERIALIZABLE,
retVals=[true], txSize=0, flags=0, keysCnt=1,
super=GridDistributedBaseMessage [ver=GridCacheVersion [topVer=163575049,
order=1552095656672, nodeOrder=5], committedVers=null, rolledbackVers=null,
cnt=0, super=GridCacheIdMessage [cacheId=288276891]

Not sure if it adds anything, there is also bunch of these:
DEBUG GridDhtTxRemote:454 - Invalid transaction state transition
[invalid=PREPARED, cur=PREPARED, tx=GridDhtTxRemote
[nearNodeId=74418337-ff2d-41ea-b93d-0dc371614b68,
rmtFutId=7855bef5961-1f4f7cdf-c7b2-4141-815f-86563df4b23d,
nearXidVer=GridCacheVersion [topVer=163568372, order=1552092449386,
nodeOrder=4], storeWriteThrough=false, super=GridDistributedTxRemoteAdapter
[explicitVers=null, started=true, commitAllowed=0,
txState=IgniteTxRemoteStateImpl [readMap={}, writeMap={IgniteTxKey
[key=com.google.protobuf.ByteString$LiteralByteString [idHash=1280551205,
hash=-847442509, bytes=[101, 0, 0, 0, 0, 0, 0, 0, 10, 0, 0, 0], hash=0],
cacheId=288276891]=IgniteTxEntry
[key=com.google.protobuf.ByteString$LiteralByteString [idHash=1280551205,
hash=-847442509, bytes=[101, 0, 0, 0, 0, 0, 0, 0, 10, 0, 0, 0], hash=0],
cacheId=288276891, txKey=IgniteTxKey
[key=com.google.protobuf.ByteString$LiteralByteString [idHash=1280551205,
hash=-847442509, bytes=[101, 0, 0, 0, 0, 0, 0, 0, 10, 0, 0, 0], hash=0],
cacheId=288276891], val=[op=CREATE, 




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

adding new primitive type columns to the existing tables (table has data) in Cassandra causes Ignite to raise an exception in Ignite 2.7.0 or 2.8.0 daily build when loading the data from Cassandra int

[xmw45688]

Hi All,

Adding new primitive type columns to the existing tables (table has data) in
Cassandra causes Ignite to raise an exception (see below) in Ignite 2.7.0 or
2.8.0 nightly build when loading the data from Cassandra into Ignite Cache
store.   This works before Ignite 2.6, and even
apache-ignite-fabric-2.7.0.20180918 nightly build.  The assumption seems not
correct because both Ignite and Cassandra are (key, value) store.   

In fact, SQLLINE tool, we don't need to insert into primitive value, see the
example blow
CREATE TABLE aa (col1 int PRIMARY KEY, col2 double );
INSERT INTO aa(col1) VALUES (1);
SELECT * FROM aa;

0: jdbc:ignite:thin://localhost> select * from aa;
+++
|  COL1  |  COL2  |
+++
| 1  | null   |
+++
1 row selected (0.052 seconds)
0: jdbc:ignite:thin://localhost>


[2019-03-11
09:44:34,352][ERROR][cassandra-cache-loader-#61%ignite-procurant-purchase-order-cluster%][CassandraCacheStore]
Failed to build Ignite value object from provided Cassandra row
java.lang.IllegalArgumentException: Can't cast null value from Cassandra
table column 'suppliertotamt' to double value used in domain object model
at
org.apache.ignite.cache.store.cassandra.common.PropertyMappingHelper.getCassandraColumnValue(PropertyMappingHelper.java:169)
at
org.apache.ignite.cache.store.cassandra.persistence.PojoField.setValueFromRow(PojoField.java:205)
at
org.apache.ignite.cache.store.cassandra.persistence.PersistenceController.buildObject(PersistenceController.java:405)
at
org.apache.ignite.cache.store.cassandra.persistence.PersistenceController.buildValueObject(PersistenceController.java:227)
at
org.apache.ignite.cache.store.cassandra.session.LoadCacheCustomQueryWorker$1.process(LoadCacheCustomQueryWorker.java:107)
at
org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.execute(CassandraSessionImpl.java:402)
at
org.apache.ignite.cache.store.cassandra.session.LoadCacheCustomQueryWorker.call(LoadCacheCustomQueryWorker.java:81)
at
org.apache.ignite.cache.store.cassandra.session.LoadCacheCustomQueryWorker.call(LoadCacheCustomQueryWorker.java:35)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
[2019-03-11
09:44:34,360][ERROR][cassandra-cache-loader-#61%ignite-procurant-purchase-order-cluster%][CassandraCacheStore]
Failed to execute Cassandra loadCache operation
class org.apache.ignite.IgniteException: Failed to execute Cassandra
loadCache operation
at
org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.execute(CassandraSessionImpl.java:415)
at
org.apache.ignite.cache.store.cassandra.session.LoadCacheCustomQueryWorker.call(LoadCacheCustomQueryWorker.java:81)
at
org.apache.ignite.cache.store.cassandra.session.LoadCacheCustomQueryWorker.call(LoadCacheCustomQueryWorker.java:35)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: class org.apache.ignite.IgniteException: Failed to build Ignite
value object from provided Cassandra row
at
org.apache.ignite.cache.store.cassandra.session.LoadCacheCustomQueryWorker$1.process(LoadCacheCustomQueryWorker.java:112)
at
org.apache.ignite.cache.store.cassandra.session.CassandraSessionImpl.execute(CassandraSessionImpl.java:402)
... 6 more
Caused by: java.lang.IllegalArgumentException: Can't cast null value from
Cassandra table column 'suppliertotamt' to double value used in domain
object model
at
org.apache.ignite.cache.store.cassandra.common.PropertyMappingHelper.getCassandraColumnValue(PropertyMappingHelper.java:169)
at
org.apache.ignite.cache.store.cassandra.persistence.PojoField.setValueFromRow(PojoField.java:205)
at
org.apache.ignite.cache.store.cassandra.persistence.PersistenceController.buildObject(PersistenceController.java:405)
at
org.apache.ignite.cache.store.cassandra.persistence.PersistenceController.buildValueObject(PersistenceController.java:227)


CREATE TABLE aa (col1 int PRIMARY KEY, col2 double );
INSERT INTO aa(col1) VALUES (1);
SELECT * FROM aa;




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/