Re: Statistics Monitoring Integrations

[Co1l]

You can collect statistics through remote JMX. Use IGNITE_JMX_PORT
environment variable to set port.
Seems like DataDog able to connect to remote Mbeans server.  There are
should be 3rd party plugins for NewRelic.



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

Re: Possible issue with Web Console

[Alexey Kuznetsov]

Hi!

Could you describe how you are starting Web Console?
Also, from what DB you are importing tables?
Could you attach a SQL script that we can try to reproduce?

Import should work in open source Web Console.


On Tue, Aug 14, 2018 at 2:01 AM sv  wrote:

> Web Console, Configure -> Import from Database, select some tables,
> Download
> project:
> The downloaded .zip file does not contain any of the Model java classes for
> the tables, and the XML file does not contain any queryEntities definitions
> for any of the tables.  When I click on "Project Structure" before the
> download, I clearly see all the Model classes in there, and when I look at
> the 'Model' part of the UI, it shows all the fields that go into the
> queryEntities section, but the export contains none of those.  What's more,
> is that AFTER the export, all the Model classes disappear from the 'Project
> Structure'.
>
> I have tried:
> - Web Agent 2.5 (Ignite cluster 2.5)
> - Web Agent 2.6 (Ignite cluster 2.5)
> The behaviour is identical in both cases.
>
> I have also tried GridGain console (which is currently 2.4.4), and it works
> perfectly.
>
> Is this an issue with open source Web Console vs the GridGain version?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
> --
> Alexey Kuznetsov
> 
>

C++ client Exception occurred: Unexpected header during deserialization: 9

[wengyao04]

Hi we are using c++ client, our key and data are ignite BinaryType
After we populate data, we try to use SqlQuery to get some data back however
we get

Exception occurred: Unexpected header during deserialization: 9

Does anyone have any clue for this exception ? Thanks



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

C++ client Exception occurred: Unexpected header during deserialization: 9

[wengyao04]

Hi we are using c++ client, our key and data are ignite BinaryType
After we populate data, we try to use SqlQuery to get some data back however
we get

Exception occurred: Unexpected header during deserialization: 9

Does anyone have any clue for this exception ? Thanks



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

Re: Free Network Segmentation (aka split brain) plugin available

[luqmanahmad]

Thanks Dmitry. I have also added the initial version of TcpIpSegmentation -
Still not sure about it but hopefully it should fill the purpose - So far I
have tested it with postgres, sql server and tomcat 



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

Re: Effect of WriteSynchronizationMode on write operations inside a transaction in Apache Ignite

[Kia Rahmani]

The main reason I want to add backups is to allow very fast reads (assuming
backup reads are allowed). 
Do you know of any way of keeping (stale) copies locally (next to the
clients) in order to save network latency in read operations, without
affecting write latency?





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

Re: Effect of WriteSynchronizationMode on write operations inside a transaction in Apache Ignite

[Kia Rahmani]

Thanks for the prompt reply!

Here is my client code:
https://www.codepile.net/pile/ywYXOvJX

In the experiment, the client resides in Singapore and 2 servers are located
at Singapore (same machine as the client) and Ohio. The primary copy is
maintained at Ohio and the backup is kept in Singapore next to the client. 
(The main reason of doing this is to be able to achieve performance by
keeping a backup copy next to the clients, however I am not able to see
this, because although the reads become much faster (assuming backup reads
are allowed) the writes now become slower (compared to a single server and
copy setup)

Thanks!



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

Possible issue with Web Console

[sv]

Web Console, Configure -> Import from Database, select some tables, Download
project:
The downloaded .zip file does not contain any of the Model java classes for
the tables, and the XML file does not contain any queryEntities definitions
for any of the tables.  When I click on "Project Structure" before the
download, I clearly see all the Model classes in there, and when I look at
the 'Model' part of the UI, it shows all the fields that go into the
queryEntities section, but the export contains none of those.  What's more,
is that AFTER the export, all the Model classes disappear from the 'Project
Structure'.  

I have tried:
- Web Agent 2.5 (Ignite cluster 2.5)
- Web Agent 2.6 (Ignite cluster 2.5)
The behaviour is identical in both cases.

I have also tried GridGain console (which is currently 2.4.4), and it works
perfectly.

Is this an issue with open source Web Console vs the GridGain version?  



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

Re: Effect of WriteSynchronizationMode on write operations inside a transaction in Apache Ignite

[akurbanov]

Hello,

Can you share your benchmark?




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

Re: WebConsole does not see cluster

[KJQ]

So, I finally got this working.

I ended up:
- Copying the rest-http module into my main Ignite node (the only one who's
IP i am using for discovery right now).

- I shell into the running "ignite" instance and run the web agent from
there (not outside the containers)

Questions:

- I see in "caches" my cache.  Should I see my configurations in
configurations as well or is that only for created ones?

- Where do I need the agent and rest api?  It seems like having it in the
one node will suffice.  Do I need to have both on every node?



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

Effect of WriteSynchronizationMode on write operations inside a transaction in Apache Ignite

[Kia Rahmani]

Hi Folks,

WriteSynchronizationMode allows users to pick from 3 different
synchronization modes (FULL_SYNC, FULL_ASYNC, PRIMARY_SYNC) when performing
writes on a distributed setting.

Based on my understanding, when writing to the cache (whether inside or
outside of a transaction) the user-perceived latency must be the same in the
following two scenarios if the WriteSynchronizationMode is set to
PRIMARY_SYNC:

1)one-node cluster where only 1 primary copy of the data exits in a remote
server.
2) two-node cluster where 1 primary copy of the data resides on the remote
server and a backup copy 
exists in the adjacent server.

In other words, the write latency should not be affected by the number of
backup copies in PRIMARY_SYNC.

However, in my current experiments (performing 2 writes inside a
transaction), I am facing different latencies for the above settings (3RTT
for scenario #1 and 4RTT for scenario #2 ). 

Can someone please explain why this is happening how I can fix it? 



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

Map C# class to Cassandra persistence settings

[crenique]

Hello, 
I am integrating Cassandra to ignite.NET.
I followed an example, and managed to make a cache be persisted to Cassandra
with primitive data types.
https://apacheignite-mix.readme.io/v2.6/docs/examples


But is it possible to map C# key/value type classes to the Cassandra
persistence settings ?







This is our C# ignite cache key/value type classes.

--- Cache key type ---
public class StateDataKey : IBinarizable
{
[QuerySqlField]
public string CacheKey { get; set; }

[QuerySqlField]
[AffinityKeyMapped]
public long AffinityKey { get; set; }

public StateDataKey() { }
public StateDataKey(string szStateKey, long lAffinityKey)
{
CacheKey = szStateKey;
AffinityKey = lAffinityKey;
}

public void WriteBinary(IBinaryWriter writer)
{
writer.WriteString(nameof(CacheKey), CacheKey);
writer.WriteLong(nameof(AffinityKey), AffinityKey);
}

public void ReadBinary(IBinaryReader reader)
{
CacheKey = reader.ReadString(nameof(CacheKey));
AffinityKey = reader.ReadLong(nameof(AffinityKey));
}

public override string ToString()
{
return string.Format("StateDataKey [Key={0}, Affinity={1}]",
CacheKey, AffinityKey);
}
}


--- Cache value type ---
public class StateData : IBinarizable
{
[QuerySqlField(IsIndexed = true)]
public DateTime LastUpdated { get; set; }
[QuerySqlField(IsIndexed = true)]
public DateTime LastPersisted { get; set; }

[QuerySqlField]
public byte[] Data { get; set; }


public StateData() { }
public StateData(byte[] btStateData)
{
LastUpdated = DateTime.UtcNow;
LastPersisted = DateTime.MinValue;

Data = btStateData;
}

public void WriteBinary(IBinaryWriter writer)
{
writer.WriteTimestamp(nameof(LastUpdated), LastUpdated);
writer.WriteTimestamp(nameof(LastPersisted), LastPersisted);
writer.WriteByteArray(nameof(Data), Data);
}

public void ReadBinary(IBinaryReader reader)
{
LastUpdated = reader.ReadTimestamp(nameof(LastUpdated)) ??
DateTime.UtcNow;
LastPersisted = reader.ReadTimestamp(nameof(LastPersisted)) ??
DateTime.UtcNow;
Data = reader.ReadByteArray(nameof(Data));
}
}




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

how ignite c++ node set baselinetopology

[wangsan]

I have a java node with persistence. Then when c++ node join.how to active
and set blt with api?



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

Re: what are the alternative for IgniteQueue for FIFO transactional, reliable, low-latency messaging

[dkarachentsev]

Hi,

I think the best way here would be to read items directly from kafka,
process and store in cache and rememeber in another cache kafka stream
offset. If node crashes, your service could start from the last point
(offset).

Thanks!
-Dmitry



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

Re: Transaction Throughput in Data Streamer

[dkarachentsev]

Hi,

It looks like the most of the time transactions in receiver are waiting for
locks. Any lock adds serialization for parallel code. And in your case I
don't think it's possible to tune throughput with settings, because ten
transactions could wait when one finish. You need to change algorithm. 

The most effective way would be to stream data with DataStreamer with
disabled allowOverride and without any transactions. You need to stream data
independently if it's possible, avoid serial code and non-local cache
reads/writes.

Thanks!
-Dmitry



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

Re: System cache's DataRegion size is configured to 40 MB.

[dkarachentsev]

Hi,

Yes, you're right, it was missed during refactoring. I've created a ticket
[1], you may fix it and contribute to Apache Ignite :)

[1] https://issues.apache.org/jira/browse/IGNITE-9259

Thanks!
-Dmitry



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

Re: Spark to Ignite Data load, Ignite node crashashing

[dkarachentsev]

Hi,

Looks like it was killed by kernel. Check logs for OOM Killer:
grep -i 'killed process' /var/log/messages

If process was killed by Linux, correct your config, you might be set too
much memory for Ignite paged memory, set to lower values [1]

If not, try to find in logs by PID, maybe it was killed due to other reason.

[1] https://apacheignite.readme.io/docs/memory-configuration

Thanks!
-Dmitry



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

Re: No response from ignite job tracker

[ilya.kasnacheev]

Hello!

You should not use curl to test 11211 port since it's not an HTTP port.

I don't think that Ignite binary client protocol supports whatever
mapreduce.jobtracker.address expects. Have you tried "local"?

Regards,



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

Re: Ignite instance with provided name doesn't exist. Did you call Ignition.start(..) to start an Ignite instance?

[Ilya Kasnacheev]

Hello!

You need to start a node in that process (client or server) to communicate
with stand-alone node.

You can only reference Ignite nodes in local Java process by name.

Regards,

-- 
Ilya Kasnacheev

2018-08-13 16:22 GMT+03:00 monstereo :

> I have started Ignite node with
> igniteConfiguration.setIgniteInstanceName("sample");
>
> now,i want to get instance of this 'sample' node
>
> here is the main app(assume that sample is node is running)
>
> public static void main(String[] args) throws IgniteCheckedException {
>
> System.out.println(Ignition.ignite("sample").toString());
>
> }
>
> But gives me the error 'Ignite instance with provided name doesn't exist.
> Did you call Ignition.start(..) to start an Ignite instance?'
>
> even if, i could see that  'Ignite node started OK (id=e27694f2, instance
> name=sample)'
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Ignite instance with provided name doesn't exist. Did you call Ignition.start(..) to start an Ignite instance?

[monstereo]

I have started Ignite node with 
igniteConfiguration.setIgniteInstanceName("sample");

now,i want to get instance of this 'sample' node

here is the main app(assume that sample is node is running)
 
public static void main(String[] args) throws IgniteCheckedException {

System.out.println(Ignition.ignite("sample").toString());

}

But gives me the error 'Ignite instance with provided name doesn't exist.
Did you call Ignition.start(..) to start an Ignite instance?'

even if, i could see that  'Ignite node started OK (id=e27694f2, instance
name=sample)' 



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

Re: Free Network Segmentation (aka split brain) plugin available

[dkarachentsev]

Hi,

Nice work, thank you! I'm sure it will be very useful. Looking forward for
your contributions in Apache Ignite project ;)

Thanks!
-Dmitry



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

Re: Partition distribution across nodes

[dkarachentsev]

Hi,

Ignite by default uses Rendezvous hashing algorithm [1] and
RendezvoudAffinityFunction is an implementation that responsible of
partition distribution [2]. This allows significantly reduce traffic on
partiton rebalancing.

[1] https://en.wikipedia.org/wiki/Rendezvous_hashing
[2]
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/affinity/rendezvous/RendezvousAffinityFunction.html

Thanks!
-Dmitry



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

Partition distribution across nodes

[Prasad Bhalerao]

Hi,
How does ignite distribute partition across available nodes?

E.g: if there are 4 nodes and 1024 partitions, then partition P1 goes to
Node N1, P2 goes to N2 , P3 goes to N3 and P4 goes to N4 and so on.


What algorithm does ignite use to distribute partitions?


Thanks,
Prasad

Re: security question - custom plugin

[dkarachentsev]

Hi,

1) You need to add jetbrains annotation in compile-time [1].
2) Imports depend on what are you using :) It's hard to say if your imports
enough. Add ignite-core to your plugin dependencies.

I don't think that there are other examples besides that blog post.

[1] https://mvnrepository.com/artifact/org.jetbrains/annotations/13.0

Thanks!
-Dmitry



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

Re: While enabling JCache, JCacheMetrics is throwing NullPointerException in getCacheManager with spring boot

[daya airody]

Hi slava,

I have uploaded my code at below link:
https://github.com/daya-airody/ignite-caching

You need uncomment below lines in application.properties before running
startup.sh.

spring.cache.jcache.config=classpath:example-cache.xml
spring.cache.cache-names=users,cannedReports

When you run startup.sh, it throws below error:

org.apache.ignite.cache.CacheExistsException: Failed to start cache (a cache
with the same name is already started): users

Please review my code and help me debug this issue.
Thanks in advance,
--daya--



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

Re: values retrieved from the cache are wrapped with JdkDynamicAopProxy while using springboot and JCache

[daya airody]

HI Ivan,

I have uploaded a simple spring application reproducing the issue at below
link:

https://github.com/daya-airody/ignite-caching

When I use ConcurrentMapCache to cache results from spring JPA native query,
I am able to retrieve it correctly. However, once I enable ignite and
JCache, I run into proxy issues. Looks like I am hitting some serialization
problem,

Please review my code and help me troubleshoot this issue.


thanks in advance,

--daya--



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

Re: When using CacheMode.LOCAL, OOM

[dkarachentsev]

Hi, 

I've opened a ticket for this [1]. It seems LOCAL cache keeps all entries
on-heap. If you use only one node - switch to PARTITIONED, if more than one
- PARTITIONED + node filter [2]

[1] https://issues.apache.org/jira/browse/IGNITE-9257
[2]
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/CacheConfiguration.html#setNodeFilter-org.apache.ignite.lang.IgnitePredicate-

Thanks!
-Dmitry



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

Re: Running Spark Job in Background

[Ilya Kasnacheev]

Hello!

You can invoke `disown' after launching process with &.

Note that & and nohup are very different, it is very strange if the result
is the same. Nohup jobs don't even use same terminal.

Regards,

-- 
Ilya Kasnacheev

2018-08-13 14:02 GMT+03:00 ApacheUser :

> Thanks Denis,
>
> When Submit Spark job which connects to Ignite cluster creates an Ignite
> Client. The Ignite Client gets disconnected whe I close the window(Linux
> Shell).
> Regular Spark jobs are running fine with & or nohup, but in Spark/Ignite
> case, the clienst ae getting killed and spark job nologer runs.
>
> is there any way I can run the spark/Ignite job continuously even ater
> closing the linux shell?
>
> thanks
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Running Spark Job in Background

[ApacheUser]

Thanks Denis,

When Submit Spark job which connects to Ignite cluster creates an Ignite
Client. The Ignite Client gets disconnected whe I close the window(Linux
Shell).
Regular Spark jobs are running fine with & or nohup, but in Spark/Ignite
case, the clienst ae getting killed and spark job nologer runs.

is there any way I can run the spark/Ignite job continuously even ater
closing the linux shell?

thanks



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

Re: taking more time while reading records.

[Denis Mekhanikov]

Shuvendu,

What is your cluster configuration?
How many nodes do you have?
Do you use persistence or 3rd party storage?
How do you read data?

Denis

пн, 13 авг. 2018 г. в 7:43, Shuvendu Das :

> Hi,
>
> We came across a situation where it is taking 10 time more time while
> reading records.
>   Our initial grid size is 390,746 (count)
>   Grid size increased to 7,297,301 (count)
>   Now it is taking 10 times more time.
>
> Regards
>
> Shuvendu
>

Re: Running Spark Job in Background

[Denis Mekhanikov]

This is not really an Ignite question. Try asking it on Spark userlist:
http://apache-spark-user-list.1001560.n3.nabble.com/

Running commands with & is a valid approach though.
You can also try using nohup .

Denis

вс, 12 авг. 2018 г. в 5:12, ApacheUser :

> Hello Ignite Team,
>
> I have Spark job thats streams live data into Ignite Cache . The  job gets
> closed as soon as I close window(Linux shell) . The other spark streaming
> jobs I run with "&" at the end of spark submit job and they run for very
> long time untill they I stop or crash due to other factors etc.
>
> Is there any way I can run Spark-Ignite job continuously?
>
> This is my spark submit:
>
> spark-submit --packages org.apache.spark:spark-sql-kafka-0-10_2.11:2.3.0
> --master spark://:7077  --executor-cores x --total-executor-cores x
> --executor-memory Xg --conf spark.driver.maxResultSize=Xg --driver-memory
> Xg
> --conf spark.default.parallelism=XX --conf
> spark.serializer=org.apache.spark.serializer.KryoSerializer   --class
> com...dataload .jar  &
>
>
> Thanks
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Failed to create index on cache

[ilya.kasnacheev]

Hello!

I suggest specifying shorter index name manually, since it looks like
automatically generated index name was too long (longer than 255 bytes).

It has no relation to number of fields, just to its name which can be any
compliant string.

Regards,



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

Re: Perfromance Issues when Grid size is more (.Net)

[ilya.kasnacheev]

Hello!

I suggest you continue discussion in
http://apache-ignite-users.70518.x6.nabble.com/Is-Cache-reads-take-long-time-with-cache-size-increase-td23326.html
instead of starting new threads.

Regards,



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

Re: Any mbean call to get all deployed services in a grid

[ilya.kasnacheev]

Hello!

I went through MBeans and MXBeans in Apache Ignite code base, found no such
calls.

Please feel free to contribute.

Regards,



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

Re: ODBC Driver compile error

[Linus Surguy]

On 13/08/2018 09:37, Ilya Kasnacheev wrote:

Hello Floris, Linus.

We have a patch for OpenSSL 1.1 compatibility, but it's not in any 
released versions.


Hi,

Thanks all, reporting back for other people if they search the archive. 
I can confirm that this was indeed my problem and on Debian removing the 
default SSL library (apt remove libssl-dev) and installing the 1.0 
version (apt install libssl1.0-dev) allowed the ODBC drive to compile 
correctly.


Linus



Regards,

--
Ilya Kasnacheev

2018-08-12 22:32 GMT+03:00 Floris Van Nee >:


Hi Linus,

I had the same error when I was trying to compile with openssl
1.1. Compiling with openssl1.0 solved the issue for me..

-Floris

From: Linus Surguy mailto:li...@magrathea-telecom.co.uk>>
Sent: Sunday, August 12, 2018 3:08 PM
To: user@ignite.apache.org 
Subject: ODBC Driver compile error [External]

Hi all,

I've been trying to compile the ODBC Driver under a fairly standard
Debian system. Ignite installed from the deb on the Ignite website,
although I've also tried the latest GIT release with the same results.

Google found another user with a similar issue back in March on this
list, but no resolution was reported back.

The make fails with the following errors listed below. Is there
particular gcc/g++/openssl version requirement which isn't obvious?

Any pointers would be appreciated,

Linus


Making all in include
make[3]: Entering directory
'/usr/share/apache-ignite/platforms/cpp/odbc/include'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory
'/usr/share/apache-ignite/platforms/cpp/odbc/include'
make[3]: Entering directory
'/usr/share/apache-ignite/platforms/cpp/odbc'
   CXX      src/ssl/secure_socket_client.lo
In file included from ./include/ignite/odbc/ssl/ssl_bindings.h:21:0,
                  from src/ssl/secure_socket_client.cpp:25:
./include/ignite/odbc/ssl/ssl_bindings.h:133:24: error:
‘ignite::odbc::ssl::OPENSSL_init_ssl’ declared as an ‘inline’ variable
              inline int SSL_library_init()
                         ^
./include/ignite/odbc/ssl/ssl_bindings.h:133:24: error: expression
list
treated as compound expression in initializer [-fpermissive]
              inline int SSL_library_init()
                         ^
In file included from src/ssl/secure_socket_client.cpp:25:0:
./include/ignite/odbc/ssl/ssl_bindings.h:134:13: error: expected
‘,’ or
‘;’ before ‘{’ token
              {
              ^
In file included from ./include/ignite/odbc/ssl/ssl_bindings.h:21:0,
                  from src/ssl/secure_socket_client.cpp:25:
./include/ignite/odbc/ssl/ssl_bindings.h:142:25: error: variable or
field ‘OPENSSL_init_ssl’ declared void
              inline void SSL_load_error_strings()
                          ^
src/ssl/secure_socket_client.cpp: In static member function ‘static
void* ignite::odbc::ssl::SecureSocketClient::MakeContext(const
string&,
const string&, const string&,
ignite::odbc::diagnostic::Diagnosable&)’:
src/ssl/secure_socket_client.cpp:206:31: error:
‘ignite::odbc::ssl::OPENSSL_init_ssl’ cannot be used as a function
                          (void)SSL_library_init();
                                ^
src/ssl/secure_socket_client.cpp:208:25: error:
‘ignite::odbc::ssl::OPENSSL_init_ssl’ cannot be used as a function
                          SSL_load_error_strings();
                          ^
src/ssl/secure_socket_client.cpp:237:40: error: ‘SSL_CTRL_OPTIONS’ was
not declared in this scope
                  ssl::SSL_CTX_ctrl(ctx, SSL_CTRL_OPTIONS, flags,
NULL);



--
Magrathea Telecommunications Ltd Tel: 0345 004 0040 +44 118 321 0321
5 Commerce Park, Theale, RG7 4AB ENGLAND. Registered Company 4260485




--
Magrathea Telecommunications Ltd Tel: 0345 004 0040 +44 118 321 0321
5 Commerce Park, Theale, RG7 4AB ENGLAND. Registered Company 4260485

security question - custom plugin

[wt]

I am looking at the
http://smartkey.co.uk/development/securing-an-apache-ignite-cluster/ example
but it doesn't dive into details and when trying to build one myself i am
unsure of the following

1) what imports are needed for the annotations is it
org.jetbrains.annotations?

2) i have the following imports, am i missing anything

import org.apache.ignite.IgniteCheckedException;
import org.apache.ignite.IgniteException;
import org.apache.ignite.cluster.ClusterNode;
import org.apache.ignite.plugin.IgnitePlugin;
import org.apache.ignite.plugin.PluginConfiguration;
import org.apache.ignite.plugin.PluginContext;
import org.apache.ignite.plugin.PluginProvider;
import org.apache.ignite.internal.processors.security.*;
import org.apache.ignite.spi.discovery.DiscoverySpiNodeAuthenticator;

import java.util.Collection;
import java.util.HashSet;
import java.util.Set;

If someone could point me to a recent working example of a security plugin
that would be amazing. I am looking at integrating authorization with
kerberos where i can create groups with specific permission and apply that
to individual caches.





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

Re: Performance degradation in embed mode

[Ilya Kasnacheev]

Hello!

In your thread dump I observe that context creation is still underway
(org.apache.catalina.mbeans.MBeanFactory.createStandardContext)

No load is passed to Apache Ignite yet.

Regards,

-- 
Ilya Kasnacheev

2018-08-11 12:09 GMT+03:00 Dmitriy :

> Hello Igniters,
>
> I'm using an spring web application with the embed Ignite cache.
> When we run in unit-tests, the insertion time into the cache is about 10
> 000
> values/seconds.
> But when the application is running on the Apache Tomcat server, the insert
> is very slow (about 5 minutes).
> The application runs on one node.
> CPU usage: 15-20%.
> threaddump.txt
> 
>
>
> So do you have any idea what the problem could be?
>
>   @PostConstruct
>   public void putAllCache() {
> Map map = new HashMap<>();
> for (long l = 0; l < 10_000L; l++) {
>   map.put(
> new CacheId(new Random().nextLong(), new Random().nextLong()),
> new DataUnit(new Random().nextLong(), new Random().nextLong(), new
> Random().nextLong())
>   );
> }
>
>
> IgniteConfiguration configuration = new IgniteConfiguration();
> String regionName = "MyRegion";
> DataRegionConfiguration dataRegionConfiguration = new
> DataRegionConfiguration();
> dataRegionConfiguration.setName(regionName);
> dataRegionConfiguration.setMaxSize(DataUnits.MEGABYTE.getBytes(1024));
> dataRegionConfiguration.setPersistenceEnabled(false);
> DataStorageConfiguration dataStorageConfiguration = new
> DataStorageConfiguration();
> dataStorageConfiguration.setDataRegionConfigurations(
>   new DataRegionConfiguration[] {dataRegionConfiguration}
> );
> configuration.setDataStorageConfiguration(dataStorageConfiguration);
>
> Ignite ignite = Ignition.getOrStart(configuration);
> String cacheName = "MyCache";
> CacheConfiguration cacheConfiguration = new
> CacheConfiguration();
> cacheConfiguration.setName(cacheName);
> cacheConfiguration.setIndexedTypes(CacheId.class, DataUnit.class);
> cacheConfiguration.setDataRegionName(regionName);
> cacheConfiguration.setBackups(1);
> cacheConfiguration.setCacheMode(CacheMode.PARTITIONED);
> cacheConfiguration.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
>
> IgniteCache cache =
> ignite.getOrCreateCache(cacheConfiguration);
>
> LOGGER.info("Start putAll.");
> cache.putAll(map);
> LOGGER.info("End putAll.");
>   }
>
> 11:28:23.456 [RMI TCP Connection(2)-127.0.0.1] TX[] INFO
> c.p.o.b.d.a.s.t.i.i.PutAllTest - Start putAll.
> 11:33:23.881 [RMI TCP Connection(2)-127.0.0.1] TX[] INFO
> c.p.o.b.d.a.s.t.i.i.PutAllTest - End putAll.
>
>
> Dmitriy
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Apache Ignite as Hibernate L2 cache

[Ilya Kasnacheev]

Hello!

There's an epic thread with a lot of examples:
http://apache-ignite-users.70518.x6.nabble.com/Hibernate-L2-cache-with-Ignite-How-td22570.html

The compatible versions, roughly, seem to be 4.2 and 5.1. Note that since
Hibernate is LGPL, you will have to build Ignite modules on your side.

Regards,

-- 
Ilya Kasnacheev

2018-08-12 14:18 GMT+03:00 dpushkar :

> Hi, Has anyone used Ignite as Hibernate Level 2 cache? If yes then what
> are the versions of Hibernate and Ignite that are compatible? If someone
> has used it already, I would appreciate if required configurations are
> posted here.
> --
> Sent from the Apache Ignite Users mailing list archive
>  at Nabble.com.
>

Re: ODBC Driver compile error

[Ilya Kasnacheev]

Hello Floris, Linus.

We have a patch for OpenSSL 1.1 compatibility, but it's not in any released
versions.

Regards,

-- 
Ilya Kasnacheev

2018-08-12 22:32 GMT+03:00 Floris Van Nee :

> Hi Linus,
>
> I had the same error when I was trying to compile with openssl 1.1.
> Compiling with openssl1.0 solved the issue for me..
>
> -Floris
> 
> From: Linus Surguy 
> Sent: Sunday, August 12, 2018 3:08 PM
> To: user@ignite.apache.org
> Subject: ODBC Driver compile error [External]
>
> Hi all,
>
> I've been trying to compile the ODBC Driver under a fairly standard
> Debian system. Ignite installed from the deb on the Ignite website,
> although I've also tried the latest GIT release with the same results.
>
> Google found another user with a similar issue back in March on this
> list, but no resolution was reported back.
>
> The make fails with the following errors listed below. Is there
> particular gcc/g++/openssl version requirement which isn't obvious?
>
> Any pointers would be appreciated,
>
> Linus
>
>
> Making all in include
> make[3]: Entering directory
> '/usr/share/apache-ignite/platforms/cpp/odbc/include'
> make[3]: Nothing to be done for 'all'.
> make[3]: Leaving directory
> '/usr/share/apache-ignite/platforms/cpp/odbc/include'
> make[3]: Entering directory '/usr/share/apache-ignite/platforms/cpp/odbc'
>CXX  src/ssl/secure_socket_client.lo
> In file included from ./include/ignite/odbc/ssl/ssl_bindings.h:21:0,
>   from src/ssl/secure_socket_client.cpp:25:
> ./include/ignite/odbc/ssl/ssl_bindings.h:133:24: error:
> ‘ignite::odbc::ssl::OPENSSL_init_ssl’ declared as an ‘inline’ variable
>   inline int SSL_library_init()
>  ^
> ./include/ignite/odbc/ssl/ssl_bindings.h:133:24: error: expression list
> treated as compound expression in initializer [-fpermissive]
>   inline int SSL_library_init()
>  ^
> In file included from src/ssl/secure_socket_client.cpp:25:0:
> ./include/ignite/odbc/ssl/ssl_bindings.h:134:13: error: expected ‘,’ or
> ‘;’ before ‘{’ token
>   {
>   ^
> In file included from ./include/ignite/odbc/ssl/ssl_bindings.h:21:0,
>   from src/ssl/secure_socket_client.cpp:25:
> ./include/ignite/odbc/ssl/ssl_bindings.h:142:25: error: variable or
> field ‘OPENSSL_init_ssl’ declared void
>   inline void SSL_load_error_strings()
>   ^
> src/ssl/secure_socket_client.cpp: In static member function ‘static
> void* ignite::odbc::ssl::SecureSocketClient::MakeContext(const string&,
> const string&, const string&, ignite::odbc::diagnostic::Diagnosable&)’:
> src/ssl/secure_socket_client.cpp:206:31: error:
> ‘ignite::odbc::ssl::OPENSSL_init_ssl’ cannot be used as a function
>   (void)SSL_library_init();
> ^
> src/ssl/secure_socket_client.cpp:208:25: error:
> ‘ignite::odbc::ssl::OPENSSL_init_ssl’ cannot be used as a function
>   SSL_load_error_strings();
>   ^
> src/ssl/secure_socket_client.cpp:237:40: error: ‘SSL_CTRL_OPTIONS’ was
> not declared in this scope
>   ssl::SSL_CTX_ctrl(ctx, SSL_CTRL_OPTIONS, flags, NULL);
>
>
>
> --
> Magrathea Telecommunications Ltd Tel: 0345 004 0040 +44 118 321 0321
> 5 Commerce Park, Theale, RG7 4AB ENGLAND. Registered Company 4260485
>

Failed to create index on cache

[prem]

Hi,

create index sql query fails with javax.cache.CacheException: Schema change 
operation failed: Too long encoded indexName. is there a limit to number of 
columns we can index.

Regards,
Prem

Re: Node with BaselineTopology cannot join mixed clusterrunningincompatibility mode

[Alex Plehanov]

You can restart the cluster. Compatibility mode flag is not stored to PDS,
it exists only in memory.

2018-08-13 9:06 GMT+03:00 arunkjn :

> Thanks Alex,
>
> How can I fix this in the current cluster without resetting the persistence
> state of entire cluster?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: SEVERE: Failed to resolve default logging config file: config/java.util.logging.properties

[Evgenii Zhuravlev]

It's a class loading problem for all-in-one jar again. In any case, you
don't need includeEventTypes at all right now, so, just delete it. To avoid
this problem you can just use your project jar separately and configure
proper classpath with all needed jars

2018-08-13 10:53 GMT+03:00 monstereo :

> Does not work again.
> Maven is really interesting thing
>
> Here i the pom.xml, after your suggestion  pom.xml
> 
>
>
> Same error was given
>
> (Note that: there was no error when I convert to jar with one-jar plugin)
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: SEVERE: Failed to resolve default logging config file: config/java.util.logging.properties

[monstereo]

Does not work again. 
Maven is really interesting thing 

Here i the pom.xml, after your suggestion  pom.xml
  


Same error was given

(Note that: there was no error when I convert to jar with one-jar plugin)



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

Re: SEVERE: Failed to resolve default logging config file: config/java.util.logging.properties

[Evgenii Zhuravlev]

Why do you use other maven plugins? Then it's problem with dependencies
again. Just use the assembly plugin and that's all:





org.apache.maven.plugins
maven-assembly-plugin
2.4.1






maven-assembly-plugin
org.apache.maven.plugins


make-executable-jar-with-dependencies
package

single




true
default_package.MainApp



jar-with-dependencies









2018-08-13 10:39 GMT+03:00 monstereo :

> No it does not work.
> I am using intellji, I run the tools > xml action > validate,
> for pom.xml and config.xml, and intellji said 'No errors found'
> but same error exists.
>
> (note that: i have also tried to change the configuration xml with default
> configuration(and add just propery=gridLogger, but same error was given)
>
>
> ezhuravlev wrote
> > Well, you just broke xml, so it can't even be parsed. I sure you can fix
> > it
> > by using any XML validator - all IDEs have this built-in.
> >
> >
> >
> > 2018-08-13 10:06 GMT+03:00 monstereo 
>
> > mehmetozanguven@
>
> > :
> >
> >> I have tried with your suggestion, but this time there is an error like
> >> this:(when I remove Property 'includeEventTypes from xml configuration,
> >> it
> >> works FINE!!)
> >> Here is the pom.xml
> >> http://apache-ignite-users.70518.x6.nabble.com/
> file/t1901/pom.xml
> >>
> >>
> >> Caused by:
> >> org.springframework.beans.factory.parsing.
> BeanDefinitionParsingException:
> >> Configuration problem: Unexpected failure during bean definition parsing
> >> Offending resource: URL [jar:file./config.xml]
> >> Bean 'ignite.cfg'; nested exception is
> >> org.springframework.beans.factory.parsing.
> BeanDefinitionParsingException:
> >> Configuration problem: Unable to locate Spring NamespaceHandler for XML
> >> schema namespace [http://www.springframework.org/schema/util]
> >> Offending resource: URL [jar:file:./config.xml]
> >> Bean 'ignite.cfg'
> >> -> Property 'includeEventTypes'
> >> at
> >> org.springframework.beans.factory.parsing.
> FailFastProblemReporter.error(
> >> FailFastProblemReporter.java:70)
> >> at
> >> org.springframework.beans.factory.parsing.ReaderContext.
> >> error(ReaderContext.java:85)
> >> at
> >> org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.
> error(
> >> BeanDefinitionParserDelegate.java:308)
> >> at
> >> org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.
> >> parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:562)
> >> at
> >> org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.
> >> parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:460)
> >> at
> >> org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.
> >> parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:429)
> >> at
> >> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentR
> >> eader.processBeanDefinition(DefaultBeanDefinitionDocumentR
> eader.java:299)
> >> at
> >> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentR
> >> eader.parseDefaultElement(DefaultBeanDefinitionDocumentReader.java:190)
> >> at
> >> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentR
> >> eader.parseBeanDefinitions(DefaultBeanDefinitionDocumentR
> eader.java:169)
> >> at
> >> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentR
> eader.
> >> doRegisterBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:142)
> >> at
> >> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentR
> >> eader.registerBeanDefinitions(DefaultBeanDefinitionDocumentR
> eader.java:94)
> >> at
> >> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.
> >> registerBeanDefinitions(XmlBeanDefinitionReader.java:508)
> >> at
> >> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.
> >> doLoadBeanDefinitions(XmlBeanDefinitionReader.java:392)
> >> at
> >> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.
> >> loadBeanDefinitions(XmlBeanDefinitionReader.java:336)
> >> at
> >> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.
> >> loadBeanDefinitions(XmlBeanDefinitionReader.java:304)
> >> at
> >> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.
> >> applicationContext(IgniteSpringHelperImpl.java:379)
> >> ... 10 more
> >>
> >>
> >>
> >>
> >> --
> >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
> >>
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: SEVERE: Failed to resolve default logging config file: config/java.util.logging.properties

[monstereo]

No it does not work.
I am using intellji, I run the tools > xml action > validate,
for pom.xml and config.xml, and intellji said 'No errors found'
but same error exists.

(note that: i have also tried to change the configuration xml with default
configuration(and add just propery=gridLogger, but same error was given)


ezhuravlev wrote
> Well, you just broke xml, so it can't even be parsed. I sure you can fix
> it
> by using any XML validator - all IDEs have this built-in.
> 
> 
> 
> 2018-08-13 10:06 GMT+03:00 monstereo 

> mehmetozanguven@

> :
> 
>> I have tried with your suggestion, but this time there is an error like
>> this:(when I remove Property 'includeEventTypes from xml configuration,
>> it
>> works FINE!!)
>> Here is the pom.xml
>> http://apache-ignite-users.70518.x6.nabble.com/file/t1901/pom.xml;
>>
>>
>> Caused by:
>> org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
>> Configuration problem: Unexpected failure during bean definition parsing
>> Offending resource: URL [jar:file./config.xml]
>> Bean 'ignite.cfg'; nested exception is
>> org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
>> Configuration problem: Unable to locate Spring NamespaceHandler for XML
>> schema namespace [http://www.springframework.org/schema/util]
>> Offending resource: URL [jar:file:./config.xml]
>> Bean 'ignite.cfg'
>> -> Property 'includeEventTypes'
>> at
>> org.springframework.beans.factory.parsing.FailFastProblemReporter.error(
>> FailFastProblemReporter.java:70)
>> at
>> org.springframework.beans.factory.parsing.ReaderContext.
>> error(ReaderContext.java:85)
>> at
>> org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.error(
>> BeanDefinitionParserDelegate.java:308)
>> at
>> org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.
>> parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:562)
>> at
>> org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.
>> parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:460)
>> at
>> org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.
>> parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:429)
>> at
>> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentR
>> eader.processBeanDefinition(DefaultBeanDefinitionDocumentReader.java:299)
>> at
>> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentR
>> eader.parseDefaultElement(DefaultBeanDefinitionDocumentReader.java:190)
>> at
>> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentR
>> eader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:169)
>> at
>> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.
>> doRegisterBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:142)
>> at
>> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentR
>> eader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:94)
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.
>> registerBeanDefinitions(XmlBeanDefinitionReader.java:508)
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.
>> doLoadBeanDefinitions(XmlBeanDefinitionReader.java:392)
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.
>> loadBeanDefinitions(XmlBeanDefinitionReader.java:336)
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.
>> loadBeanDefinitions(XmlBeanDefinitionReader.java:304)
>> at
>> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.
>> applicationContext(IgniteSpringHelperImpl.java:379)
>> ... 10 more
>>
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>





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

Re: SEVERE: Failed to resolve default logging config file: config/java.util.logging.properties

[Evgenii Zhuravlev]

Well, you just broke xml, so it can't even be parsed. I sure you can fix it
by using any XML validator - all IDEs have this built-in.



2018-08-13 10:06 GMT+03:00 monstereo :

> I have tried with your suggestion, but this time there is an error like
> this:(when I remove Property 'includeEventTypes from xml configuration, it
> works FINE!!)
> Here is the pom.xml
> 
>
>
> Caused by:
> org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
> Configuration problem: Unexpected failure during bean definition parsing
> Offending resource: URL [jar:file./config.xml]
> Bean 'ignite.cfg'; nested exception is
> org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
> Configuration problem: Unable to locate Spring NamespaceHandler for XML
> schema namespace [http://www.springframework.org/schema/util]
> Offending resource: URL [jar:file:./config.xml]
> Bean 'ignite.cfg'
> -> Property 'includeEventTypes'
> at
> org.springframework.beans.factory.parsing.FailFastProblemReporter.error(
> FailFastProblemReporter.java:70)
> at
> org.springframework.beans.factory.parsing.ReaderContext.
> error(ReaderContext.java:85)
> at
> org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.error(
> BeanDefinitionParserDelegate.java:308)
> at
> org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.
> parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:562)
> at
> org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.
> parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:460)
> at
> org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.
> parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:429)
> at
> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentR
> eader.processBeanDefinition(DefaultBeanDefinitionDocumentReader.java:299)
> at
> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentR
> eader.parseDefaultElement(DefaultBeanDefinitionDocumentReader.java:190)
> at
> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentR
> eader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:169)
> at
> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.
> doRegisterBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:142)
> at
> org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentR
> eader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:94)
> at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.
> registerBeanDefinitions(XmlBeanDefinitionReader.java:508)
> at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.
> doLoadBeanDefinitions(XmlBeanDefinitionReader.java:392)
> at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.
> loadBeanDefinitions(XmlBeanDefinitionReader.java:336)
> at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.
> loadBeanDefinitions(XmlBeanDefinitionReader.java:304)
> at
> org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.
> applicationContext(IgniteSpringHelperImpl.java:379)
> ... 10 more
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Perfromance Issues when Grid size is more (.Net)

[shuvendu]

We came across a situation where it is taking 10 time more time while
reading records.
Our initial grid size is 390,746 (count) 
Grid size increased to 7,297,301 (count)
Now it is taking 10 times more time.



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

Re: SEVERE: Failed to resolve default logging config file: config/java.util.logging.properties

[monstereo]

I have tried with your suggestion, but this time there is an error like
this:(when I remove Property 'includeEventTypes from xml configuration, it
works FINE!!)
Here is the pom.xml
  


Caused by:
org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
Configuration problem: Unexpected failure during bean definition parsing
Offending resource: URL [jar:file./config.xml]
Bean 'ignite.cfg'; nested exception is
org.springframework.beans.factory.parsing.BeanDefinitionParsingException:
Configuration problem: Unable to locate Spring NamespaceHandler for XML
schema namespace [http://www.springframework.org/schema/util]
Offending resource: URL [jar:file:./config.xml]
Bean 'ignite.cfg'
-> Property 'includeEventTypes'
at
org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:70)
at
org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:85)
at
org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.error(BeanDefinitionParserDelegate.java:308)
at
org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:562)
at
org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:460)
at
org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseBeanDefinitionElement(BeanDefinitionParserDelegate.java:429)
at
org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.processBeanDefinition(DefaultBeanDefinitionDocumentReader.java:299)
at
org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseDefaultElement(DefaultBeanDefinitionDocumentReader.java:190)
at
org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:169)
at
org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.doRegisterBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:142)
at
org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:94)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:508)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:392)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304)
at
org.apache.ignite.internal.util.spring.IgniteSpringHelperImpl.applicationContext(IgniteSpringHelperImpl.java:379)
... 10 more




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

Re: Node with BaselineTopology cannot join mixed clusterrunningincompatibility mode

[arunkjn]

Thanks Alex,

How can I fix this in the current cluster without resetting the persistence
state of entire cluster?



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

Re: Node with BaselineTopology cannot join mixed clusterrunningincompatibility mode

[arunkjn]

Hi,

I am experiencing the same issue with a ignite 2.5 cluster deployed in
kubernetes.

Scenario:

5 server nodes hosting some caches. They are deployed multiple times without
issues.
I connected a visor client to this cluster (this is the first time i used
visor ever on this cluster)
On another rolling update, the nodes fail to restart with the message -
class org.apache.ignite.IgniteException: Node with BaselineTopology cannot
join mixed cluster running in compatibility mode
at
org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor.onGridDataReceived(GridClusterStateProcessor.java:714)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$5.onExchange(GridDiscoveryManager.java:883)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1939)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeAddedMessage(ServerImpl.java:4354)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2744)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2536)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6775)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2621)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)


I can also see this in the logs -

class org.apache.ignite.IgniteCheckedException: Failed to start SPI:
TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
marsh=JdkMarshaller
[clsFilter=org.apache.ignite.internal.IgniteKernal$5@3ed03652], reconCnt=10,
reconDelay=2000, maxAckTimeout=60, forceSrvMode=false,
clientReconnectDisabled=false, internalLsnr=null]
at
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:300)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:915)
at
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1720)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1033)
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
com.mediaiq.caps.platform.choreography.data.DataNodeStartup.main(DataNodeStartup.java:43)
Caused by: class org.apache.ignite.spi.IgniteSpiException: Thread has been
interrupted.
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:938)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:373)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:1948)
at
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297)
... 13 more


I am not sure if visor was still connected while deploying, but the problem
seem to persist after disconnecting visor as well. Please advise on how to
fix this. Has this been fixed in 2.6? 

Thanks,
Arun




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