Re: Ignite with Drools

[Gianfranco Murador]

Hello Dmitriy , in this period I'm quite busy, but I'd like to continue to
develop the integration module.
If you  need space for other projects I can still host the project under my
root github.
Sorry for my absence, but I hope to have the time available after the first
half of December.
Regards, Gianfranco

2015-11-28 6:30 GMT+01:00 Dmitriy Setrakyan :

> Gianfranco,
>
> I just found this repository for Drools integration:
> https://github.com/apacheignite/drools-ignite
>
> It looks a bit abandoned. Do you have plans to pick it back up?
>
> Thanks,
> D.
>



-- 
Gianfranco Murador
Igniter and Software Engineer.

[GitHub] ignite pull request: Fixing hang in metadata update.

[agoncharuk]

GitHub user agoncharuk opened a pull request:

https://github.com/apache/ignite/pull/280

Fixing hang in metadata update.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/agoncharuk/ignite ignite-1282

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/280.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #280


commit 6ef7fb604f6e56e9ea72d3ef6d6ce199564c1c41
Author: Alexey Goncharuk 
Date:   2015-11-28T12:56:22Z

Fixing metadata update under changing topology.

commit 784ea7cf5d878e7e9bffcb06cca1be863265845a
Author: Alexey Goncharuk 
Date:   2015-11-28T13:11:35Z

Renamed portable key mapper.

commit c6e117fe63a1d1ad7a2b247c658ec479ba0ba5fc
Author: Alexey Goncharuk 
Date:   2015-11-28T13:28:22Z

IGNITE-1702 - Merged fix.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Communication exception handling

[Yakov Zhdanov]

Guys,

I see the following code
(org/apache/ignite/internal/processors/cache/distributed/dht/GridDhtTxPrepareFuture.java:1129):

try {
cctx.io().send(n, req, tx.ioPolicy());
}
catch (ClusterTopologyCheckedException e) {
fut.onNodeLeft(e);
}
catch (IgniteCheckedException e) {
if (!cctx.kernalContext().isStopping())
fut.onResult(e);
}


Which means that in case if node has just started stop procedure, all cache
operations may potentially hang. If cache.put() is called from job and node
is stopping gracefully, stop process hangs with 100% probability.

This issue does not threaten failure detection and nodes crash cases since
this is handled by separate logic.

I fixed Communication SPI to use its internal stopping flag instead of the
system wide one and this seems to fix the issue with graceful stop.

Semyon, can you please see if this may cause any other issue of the kind?

My changes are here - https://github.com/apache/ignite/pull/278

--Yakov

Re: URGENT: Can we merge OSGi for 1.5?

[Yakov Zhdanov]

Raul, great news! But I would better do 1.6 in a week or two since there
are still a lot of stuff to check - maven uploads, binary packaging,
javadocs builds, etc.

--Yakov

2015-11-27 20:15 GMT+03:00 Raul Kripalani :

> Hello,
>
> We had created the expectation of OSGi being available for 1.5.
>
> Code and documentation is ready. Reviews done by Dmitriy (Docs) and Romain
> (Code, even though he's not a committer, he is a knowledgeable user).
>
> Merging should not carry any risks for regressions, as no existing code is
> modified.
>
> Can I have your OK for merge?
>
> Regards,
>
> *Raúl Kripalani*
> PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
> Messaging Engineer
> http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
> http://blog.raulkr.net | twitter: @raulvk
>

Re: Ignite-1.5 Release

[Yakov Zhdanov]

Guys,

Small update. We are very close to submit Ignite-1.5-RC1. We currently
fixing TeamCity in ignite-1.5 branch.

--Yakov

2015-11-25 3:39 GMT+03:00 Dmitriy Setrakyan :

> On Wed, Nov 25, 2015 at 3:09 AM, Raul Kripalani  wrote:
>
> > It's integrated, i.e. it deploys on an OSGi container. And the Ignite
> part
> > works. But at soon as it delegates to Spring to parse the context XML,
> the
> > latter complains about namespace handlers not being found.
> >
> > Spring DM looks into bundles to find NS handlers. So without Spring DM
> such
> > problems are expected.
> >
> > Maybe it does work after all if we refrain from using certain namespace
> > like util. I'll have to check that tomorrow.
> >
>
> Thanks! Dropping support for Spring XML configuration in OSGI would be a
> huge loss. Would be great if you could investigate it and see what it would
> take.
>

[GitHub] ignite pull request: Fixing hang in metadata update.

[agoncharuk]

Github user agoncharuk closed the pull request at:

https://github.com/apache/ignite/pull/280


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-2024) CacheAutoStoreExample: Failed to execute compound future reducer

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-2024:


 Summary: CacheAutoStoreExample: Failed to execute compound future 
reducer
 Key: IGNITE-2024
 URL: https://issues.apache.org/jira/browse/IGNITE-2024
 Project: Ignite
  Issue Type: Bug
 Environment: OS X 10.10.2
jdk-1.8.45
Reporter: Ilya Suntsov
Assignee: Yakov Zhdanov


Steps for reproduce:
1. Build examples with profiles java8 and lgpl
2. Run DbH2ServerStartup
3. Start 2 nodes using ExampleNodeStartup
4. Run CacheAutoStoreExample
Result:
Got exceptions:
CacheAutoStoreExample:
{noformat}
[23:54:21]__   
[23:54:21]   /  _/ ___/ |/ /  _/_  __/ __/ 
[23:54:21]  _/ // (7 7// /  / / / _/   
[23:54:21] /___/\___/_/|_/___/ /_/ /___/  
[23:54:21] 
[23:54:21] ver. 1.5.1#20151128-sha1:4c014a47
[23:54:21] 2015 Copyright(C) Apache Software Foundation
[23:54:21] 
[23:54:21] Ignite documentation: http://ignite.apache.org
[23:54:21] 
[23:54:21] Quiet mode.
[23:54:21]   ^-- Logging to file 
'/Users/gridgain/Downloads/gridgain-enterprise-fabric-7.5.1/work/log/ignite-25bd3c3d.log'
[23:54:21]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
"-v" to ignite.{sh|bat}
[23:54:21] 
[23:54:21] OS: Mac OS X 10.10.3 x86_64
[23:54:21] VM information: Java(TM) SE Runtime Environment 1.8.0_45-b14 Oracle 
Corporation Java HotSpot(TM) 64-Bit Server VM 25.45-b02
[23:54:21] Initial heap size is 192MB (should be no less than 512MB, use 
-Xms512m -Xmx512m).
[23:54:22] Configured plugins:
[23:54:22]   ^-- GridGain 7.5.1#20151128-sha1:c8fb3cdd
[23:54:22]   ^-- 2015 Copyright(C) GridGain Systems
[23:54:22] 
[23:54:22] Security status [authentication=off, tls/ssl=off]
[23:54:22] Rolling updates are disabled. GridGain version update will require 
full cluster restart. Consider changing 
'GridGainConfiguration.rollingUpdatesEnabled' configuration property.
[23:54:23,737][ERROR][main][GridEntLicenseProcessor] License violation detected:
  ^-- Maximum number of nodes (3/2) is exceeded.
[23:54:23,737][ERROR][main][GridEntLicenseProcessor] Contact sa...@gridgain.com 
for further assistance. Make sure to include your license ID: 
14177F1A-5B5A-4F9C-BC55-F7335715F311
[23:54:23,737][ERROR][main][GridEntLicenseProcessor] License grace/burst period 
- left 1 hour.
[23:54:23] Performance suggestions for grid  (fix if possible)
[23:54:23] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
[23:54:23]   ^-- Disable peer class loading (set 'peerClassLoadingEnabled' to 
false)
[23:54:23]   ^-- Disable grid events (remove 'includeEventTypes' from 
configuration)
[23:54:23]   ^-- Use default binary marshaller (do not set 'marshaller' 
explicitly)
[23:54:23] 
[23:54:23] To start Console Management & Monitoring run ignitevisorcmd.{sh|bat}
[23:54:23] 
[23:54:23] Ignite node started OK (id=25bd3c3d)
[23:54:23] Topology snapshot [ver=3, servers=3, clients=0, CPUs=8, heap=8.0GB]

>>> Cache auto store example started.
[23:54:24] (err) Failed to execute compound future reducer: Compound future 
listener []class org.apache.ignite.IgniteCheckedException: 
javax.cache.CacheException: Failed to find getter in POJO class 
[class=org.apache.ignite.examples.model.Person, prop=id]
at 
org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadFromStore(GridCacheStoreManagerAdapter.java:309)
at 
org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.load(GridCacheStoreManagerAdapter.java:265)
at 
org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadAllFromStore(GridCacheStoreManagerAdapter.java:398)
at 
org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadAll(GridCacheStoreManagerAdapter.java:364)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.loadMissingFromStore(GridDhtLockFuture.java:1016)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.onComplete(GridDhtLockFuture.java:745)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.onDone(GridDhtLockFuture.java:724)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.onDone(GridDhtLockFuture.java:79)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:323)
at 
org.apache.ignite.internal.util.future.GridCompoundFuture.checkComplete(GridCompoundFuture.java:301)
at 
org.apache.ignite.internal.util.future.GridCompoundFuture.markInitialized(GridCompoundFuture.java:292)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.map(GridDhtLockFuture.java:958)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.onOwnerChanged(Gri