IS NULL on Numeric Query SQL Fields

[the_palakkaran]

Hi,

int uniqueId;
int actNo;
String actId;
String somethingElse;

Now when I load values to the cache, if actNo is null in DB, then it will be
*loaded as 0* (zero being initial value)

So if I execute the below query as SQLFieldsQuery on cache, no rows would be
returned:
select somethingElse from Account where actNo * is null * and actId = ?;
(arguments will be passed as object array)

In hibernate we had the provision to mention parameter type so that it would
understand this scenario? Does ignite provide a way to resolve this ?

Thanks in advance.




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

Locking mechanism difference between sequential get() and getAll()

[kotamrajuyashasvi]

Hi

I'm using a Transactional cache in my project with pessimistic
repeatable_read mode. In my logic I have an ordered set of keys which need
to be locked. I can lock in two ways.

1. Iterate through the ordered set and call get() on each key.
2. use getAll() passing the ordered set of keys.

Functionality wise will there be any difference between the above two
methods ?
Other than that what are all the differences between the two ?



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

Re: Continuous query - Exactly once based event across multiple nodes..

[JP]

Vkulichenko,
 I want to update in multiple databases based on event triggered in the
ignite cache.



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

BinaryObjectBuilder - setField - Boolean Type - Problem

[Jonathan mayer]

Hi there, I am testing different Data Types and have come up against a problem 
with Boolean.
I have created the following table from within DBeaver:-
CREATE TABLE TEST (   F_ID varchar PRIMARY KEY,   F_INT INTEGER,   F_BOOLEAN 
BOOLEAN) WITH "CACHE_NAME=TEST, key_type=java.lang.String, value_type=TEST";

I am try to create Data via an IgniteDataStreamer.
snippet:
BinaryObjectBuilder binaryObjectBuilder = ignite.binary().builder("TEST");

binaryObjectBuilder.setField("F_BOOLEAN", true);
etc...
BinaryObject bo = binaryObjectBuilder.build();

String/Integer Types are working fine.
Getting the error message :
Wrong value has been set [typeName=TEST, fieldName=F_BOOLEAN, fieldType=Object, 
assignedValueType=boolean]

Any help would be appreciated
Jonathan

slow restart of ignite (with persistence enabled)

[Randall Harmon]

What is the recommended way to signal Ignite to shutdown cleanly, so that
WAL file doesn't have to be replayed (?) when Ignite restarts?  We are
loading a large set of data from multiple tables, and we are also
restarting ignite occasionally (new JARs for job running as ignite
service).

During this restart, even a single node cluster won't serve cmd=metadata on
its api port until the WAL scanning(?) process is complete.

(we've experience a similar situation with in-memory storage and clustered
operation, but one thing at a time...)

During the restart, iostat shows mostly lots of small reads:

> sdb 422.00 4140.00 0.00 4140 0

with occasional tiny writes:

> sdb 462.00 4512.00 128.00 4512 128


I'm looking for a way to have Ignite shut down cleanly, or another
configuration option so that normal restart (SIGINT/SIGTERM) does not cause
a long restart scenario.   Here's one case that shows 19 minutes of pause
during a restart.  I've seen it take 40 to 60 minutes too (when 2 or 3
times as much data has been loaded through it over the course of weeks).

@40005aeca93c09d3481c 14:40:50.160 [ker-#42] WARN
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager
- Logging at INFO level without checking if INFO level is enabled: Found
last checkpoint marker [cpId=bcffa2cb-803c-4378-bf52-74b7dedf6285,
pos=FileWALPointer [idx=658, fileOff=45873219, len=281]]

@40005aecadb123dbc964 14:59:51.600 [rker-#3] WARN
org.apache.ignite.internal.processors.cluster.GridClusterStateProcessor -
Logging at INFO level without checking if INFO level is enabled: Received
state change finish message: true

Any help suggested so I can restart Ignite when I need to, and have it
start responding in a reasonable amount of time?



















Thanks,
R

unsubscribe

[M Mansur Ashraf]

Re: Node failure handling semantics

[vkulichenko]

Nick,

If B is unhealthy, C will not be able to send a heartbeat message to it.
After a timeout, C will consider B as failed and will connect to A. Along
with this connection it will send a NODE_FAILED message that will go through
all the nodes.

Once B is back again, it will try to send a message to A, but will get a
response that it was already removed from topology (A knows about this as it
got information from C). This will trigger local NODE_SEGMENTED event on B.

-Val



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

Re: Continuous query - Exactly once based event across multiple nodes..

[vkulichenko]

JP,

Can you please describe the business case behind this? What are you trying
to achieve on application level? What guarantees are needed and why?

-Val



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

Setting JvmDllPath in Ignite 2.3.0

[dwtrosii1]

When setting the JvmDllPath in Ignite 2.3.0 in a configuration and starting
an ignite instance passing in that configuration, it does not seem to
register. The exception that is occurring is "Cannot load jvm.dll. Please
specify IgniteConfiguration.JvmDllPath or JAVA_HOME." I reviewed the source
code and it seems that a new ignite configuration is being created from the
source ignite configuration, in which the JvmDllPath property is not being
copied in the new configuration. 



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

Re: question about server

[Ilya Kasnacheev]

Hello!

I think that Ignite should work on 1-core server with 512M RAM and system
boot disk. The usefulness of such node is a different concern.

Regards,

-- 
Ilya Kasnacheev

2018-05-07 14:16 GMT+03:00 матвей козловский :

> Hello, i want to deploy apache ignite on Microsoft Azure, what are the
> minimum requirements for the server? specific: number of processors, RAM,
> disk size. Thank you in advance.
>

Re: Auto sync caches with database

[Ilya Kasnacheev]

Hello!

There is such feature in Apache Ignite, but it works in a different
direction: it can propagate reads to caches to a 3rd party database, and
propagate cache changes to 3rd party database.

See https://apacheignite.readme.io/docs/3rd-party-store

Implementing in in other direction is much harder because common APIs (such
as JDBC) are pull-based (explicit querying) and not push-based or
notify-based or listen-based. So generally you have no way to know when a
row in DB was changed.

Regards,

-- 
Ilya Kasnacheev

2018-05-07 15:27 GMT+03:00 begineer :

> Hi,
> I have been working with apache ignite 1.9 for quite sometime now and one
> common problem which I faced is adding new records to cache from external
> systems. Ignite currently don't provide auto sync capability with database.
> So I have to write logic to insert entries to cache whenever new data added
> to database tables by other application.
>
> Is there a plan to support such a feature in near future. I know Hazlecast
> provides this feature already.
>
> e.g. maintaining trades cache for trades from webserver. So I have trades
> table which saves uploads. To process them I keep all of them in cache.
> Whenever new upload comes in, it is added to cache using cache.put(). Would
> be awesome if this upload is picked up from table automatically.
>
> It will make life much more simple.
>
> Regards,
> Surinder
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Auto sync caches with database

[begineer]

Hi,
I have been working with apache ignite 1.9 for quite sometime now and one
common problem which I faced is adding new records to cache from external
systems. Ignite currently don't provide auto sync capability with database.
So I have to write logic to insert entries to cache whenever new data added
to database tables by other application.

Is there a plan to support such a feature in near future. I know Hazlecast
provides this feature already.

e.g. maintaining trades cache for trades from webserver. So I have trades
table which saves uploads. To process them I keep all of them in cache.
Whenever new upload comes in, it is added to cache using cache.put(). Would
be awesome if this upload is picked up from table automatically.

It will make life much more simple.

Regards,
Surinder



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

Re: Which ports does ignite cluster need to run normally?

[Olexandr K]

Hi Val, Ignite team

Reviewed all opened Ignite ports after your comments.
Everything is clear except loopback-related ports.

Here is what I see in Resource Monitor (Windows Server 2012 R2)
(prunsrv.exe is common-daemon java service wrapper running JVM 1.8 inside)

I don't understand what port 62219 is used for.
I exprimented with Ignite restarts and see that this port is chosen
dynamically.
Also, if we have port 62219 opened, we also observe number of loopback
connections starting from port 6
What are all these loopback connections used for?
Can we disable this or at least configure to use static ports?



Listening ports

Image PID  AddressPortProtocol
Firewall Status
prunsrv.exe2220IPv4 unspecified62219TCP  Allowed,
restricted - ???
prunsrv.exe2220IPv4 unspecified47500TCP  Allowed,
restricted - Ignite discovery
prunsrv.exe2220IPv4 unspecified47100TCP  Allowed,
restricted - Ignite communication
prunsrv.exe2220IPv4 unspecified11211TCP  Allowed,
restricted - HTTP internal
prunsrv.exe2220IPv4 unspecified10800TCP Allowed,
restricted - ODBC
prunsrv.exe2220IPv4 unspecified9020TCP   Allowed,
restricted - JMX

TCP Connections

ImagePIDLocal AddressLocal PortRemote AddressRemote
PortPacket Loss (%)Latency (ms)
prunsrv.exe2220server1_host47500   visor_host575500
10
prunsrv.exe2220server1_host50607server2_host47100
01
prunsrv.exe2220server1_host62275server2_host47500
01

prunsrv.exe2220IPv4 loopback62230IPv4 loopback62231
00
prunsrv.exe2220IPv4 loopback62251IPv4 loopback62250
--
prunsrv.exe2220IPv4 loopback62250IPv4 loopback62251
--
prunsrv.exe2220IPv4 loopback62249IPv4 loopback62248
--



On Thu, Apr 26, 2018 at 8:42 PM, vkulichenko 
wrote:

> Hi,
>
> The configuration is fine and it does eliminate ranges so that node always
> binds to 47500. The only drawback is that if 47500 is not available for
> whatever reason, node would not start.
>
> -Val
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Continuous query - Exactly once based event across multiple nodes..

[JP]

Thanks... This solution worked but problem is, it creating multiple remote
filter instance..




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

Services not initializing in persistence enabled cluster nodes

[JP]

Hi, 
I am using Ignite 2.4 and trying to deploy services as node singleton in
cluster.

Steps:
1. Start node 1 with persistence enabled
2. Make cluster active
3. Initialize service with node singleton
4. Start Node 2.
5. Inserted data from Node 2.
 Issue 1:   
  Expected result: Service should auto deploy in node 2
  Actual result: Service not deployed in node 2

 Here in node 2, service is not auto deployed. **May i know what's the
problem here?**
Issue 2:
   Steps:
   1. As above steps
   2. Stopped Node 1
   3. Insert data from Node 2

 After this facing following Exception: Failed to map keys for cache
(all partition nodes left the grid).


Below lines are the ignite configuration,
public IgniteConfiguration getConfig() {

IgniteConfiguration cfg = new IgniteConfiguration();

TcpDiscoverySpi discoverySpi = new TcpDiscoverySpi();

TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder();

List list = new ArrayList();
list.add("192.168.1.57");
list.add("192.168.1.57:47500..47509");

ipFinder.setAddresses(list);
discoverySpi.setIpFinder(ipFinder);
cfg.setDiscoverySpi(discoverySpi);
DataStorageConfiguration storageCfg = new 
DataStorageConfiguration();


storageCfg.getDefaultDataRegionConfiguration().setPersistenceEnabled(true);

cfg.setDataStorageConfiguration(storageCfg);


return cfg;
}




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

RE: Hi... can we squeeze this into 2.5 ...https://issues.apache.org/jira/browse/IGNITE-8439

[Stanislav Lukyanov]

// Bcc’ed user-list and added dev-list.

2.5 scope is already frozen, and I assume this isn’t a kind of issue that would 
be added at this point.

Andrey Gura, could you please comment on that?

Thanks,
Stan

From: Paul Anderson
Sent: 7 мая 2018 г. 10:33
To: user@ignite.apache.org
Subject: Hi... can we squeeze this into 2.5 
...https://issues.apache.org/jira/browse/IGNITE-8439

please :)

Hi... can we squeeze this into 2.5 ... https://issues.apache.org/jira/browse/IGNITE-8439

[Paul Anderson]

please :)

Continuous query - Exactly once based event across multiple nodes..

[JP]

Using continuous query,

How to achieve event trigger for cache exactly only once per key even if
continuous query is listening in multiple nodes or multiple listener.
example:
1. Scenario 1:
 Node A: Start Continuous query 
 Node B: Start Continuous query 
 Node C: Insert or Update or Delete record ex: number from 1 to 100

Expected Output should be as below
 Node A - 1 ,2,3,4,550
 Node B - 51, 52, 53, 54, ... 100
 Above output is the expected output. Here, event per key should be
triggered exactly once across nodes.

Actual Output should be as below
 Node A - 1 ,2,3,4,5,100
 Node B - 1, 2, 3, 4,5 ... 100
 
If this is not possible in Continuous query, then is there any way to
achieve this.

2. Scenario 2:
To achieve expected output,
 I am using singleton service per Cluster.
Ex: Cluster A
  - Singleton service with Continuous query for cache
Here problem is, service is running in only one instance.
How to achieve above output with multiple instance of service?




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