Re: GridCacheAdapter#size() has O(n) complexity

[Dmitriy Setrakyan]

Hm... why not just return the key count? Can we really have nulls in the
near cache?

On Fri, Jun 23, 2017 at 8:25 PM, Mikhail Cherkasov 
wrote:

> Hi all,
>
> GridCacheAdapter#size() has O(n) complexity and this can lead for delays
> during metric collection( https://issues.apache.org/
> jira/browse/IGNITE-5521
> ).
> It validates all elements in near cache while count them, so it takes O(n),
> but java doc requires:
>
> "Gets the number of all entries cached on this node. This method will
> return the count of all cache entries and has O(1) complexity on base
> IgniteInternalCache. It is essentially the size of cache key set and is
> semantically identical to {Cache.keySet().size().
> NOTE: this operation is not distributed and returns only the number of
> entries cached on this node."
>
>
> I see two solutions for this:
>
> 1. add special method for metrics that will have relaxed accuracy, but with
> O(1) complexity
> I implemented this solution there:
> https://github.com/gridgain/apache-ignite/commit/
> a68dd81090884d07bd737cbbf48e5f64e9cd27ec
>
> 2. or completely remove entries validation for size method.
>
> What is better solution? Thoughts?
>
> --
> Thanks,
> Mikhail.
>

Re: New version of Web Console Released

[Muthu]

Hi Alexey,

Is the latest web console available as a docker image that i can pick
up?...i see this but it seems is a month old...

https://hub.docker.com/r/apacheignite/web-console-standalone/

Regards,
Muthu

On Mon, Jun 19, 2017 at 8:04 PM, Alexey Kuznetsov 
wrote:

> Igniters!
>
> I'd like to announce that we redeployed the new version Ignite Web
> Console on GridGain infrastructure (https://console.gridgain.com) where
> you can give it a try right a way.
>
> *NOTE*:
>   1) You may need to refresh page (F5 or Ctrl+R) in order to reload Web
> Console.
>   2) You will need to download new web agent
>
> *What's new:*
>   1) Import schema from RDBMS:
> 1.1) Use unique index if no primary index defined on table.
> 1.2) Fixed bug with "PRIMARY" index on MySql.
> 1.3) Generate different datasources on import from different RDBMS.
>   2) Added ability to show notification to all Web Console user (useful to
> notify about planned WebConsole updates).
>   3) Added "Basic" configuration - to configure cluster in several clicks.
>   4) Added panel with information about "Compute".
>
> Stay tuned for updates!
>
> --
> Alexey Kuznetsov
>

Re: Optimize transaction prepare step when store is enabled IGNITE-1553

[ALEKSEY KUZNETSOV]

Yeah, it can be set "Patch available" because I need smbd to review it

пт, 23 июн. 2017 г., 21:06 Dmitry Pavlov :

> Hi Alexey,
>
> This ticket status is 'in progress'.
> Is it still in development or 'patch available' can be set?
>
> Sincerely,
> Dmitry Pavlov
>
>
>
> ср, 7 июн. 2017 г. в 17:03, ALEKSEY KUZNETSOV :
>
> > Hi, Igntrs!
> > Feel free to reviewing the ticket
> > https://issues.apache.org/jira/browse/IGNITE-1553
> > https://github.com/apache/ignite/pull/2091
> > --
> >
> > *Best Regards,*
> >
> > *Kuznetsov Aleksey*
> >
>
-- 

*Best Regards,*

*Kuznetsov Aleksey*

GridCacheAdapter#size() has O(n) complexity

[Mikhail Cherkasov]

Hi all,

GridCacheAdapter#size() has O(n) complexity and this can lead for delays
during metric collection( https://issues.apache.org/jira/browse/IGNITE-5521
).
It validates all elements in near cache while count them, so it takes O(n),
but java doc requires:

"Gets the number of all entries cached on this node. This method will
return the count of all cache entries and has O(1) complexity on base
IgniteInternalCache. It is essentially the size of cache key set and is
semantically identical to {Cache.keySet().size().
NOTE: this operation is not distributed and returns only the number of
entries cached on this node."


I see two solutions for this:

1. add special method for metrics that will have relaxed accuracy, but with
O(1) complexity
I implemented this solution there:
https://github.com/gridgain/apache-ignite/commit/a68dd81090884d07bd737cbbf48e5f64e9cd27ec

2. or completely remove entries validation for size method.

What is better solution? Thoughts?

-- 
Thanks,
Mikhail.

Re: Negative non-heap memory maximum

[Dmitry Pavlov]

Sounds reasonable to me. I've created issue for this change
https://issues.apache.org/jira/browse/IGNITE-5583

ср, 24 мая 2017 г. в 20:24, Alexey Goncharuk :

> I think it makes sense to switch non-heap memory metrics to new page memory
> semantics, this should show a clean picture in the node output and will
> also protect us from ambiguous -1 output.
>
> 2017-05-24 18:45 GMT+03:00 Dmitry Pavlov :
>
> > Igniters,
> >
> >
> >
> > On my jdk 1.8.0_131 there is negative amount of maximum non heap memory
> > returned by following code:
> >
> > ManagementFactory.getMemoryMXBean().getNonHeapMemoryUsage().getMax());
> >
> > returns -1.
> >
> >
> >
> > And this value is used in ignite metrics in
> > GridLocalMetrics.getNonHeapMemoryMaximum() which becomes negative.
> >
> >
> >
> > I have an idea to take this value from memory policy as sum of max sizes
> of
> > all memory policies, from MemoryPolicyConfiguration.getMaxSize()
> >
> >
> >
> > Would it be correct change to avoid negative values in metrics? Do you
> have
> > any comments on this? Or is it better way to use commited memory
> > getCommitted() to calculate free non heap space percent in metrics?
> >
> > Or is there any other way to obtain Max Non Heap memory size?
> >
> >
> >
> > Best Regards,
> >
> > Dmitriy Pavlov
> >
>

[jira] [Created] (IGNITE-5583) Switch non-heap memory metrics to new page memory semantics

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-5583:
--

 Summary: Switch non-heap memory metrics to new page memory 
semantics
 Key: IGNITE-5583
 URL: https://issues.apache.org/jira/browse/IGNITE-5583
 Project: Ignite
  Issue Type: Improvement
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov
Priority: Minor


On jdk 1.8.0_131 there is negative amount of maximum non heap memory returned 
by following code:
ManagementFactory.getMemoryMXBean().getNonHeapMemoryUsage().getMax());
returns -1.
 
And this value is used in ignite metrics in 
GridLocalMetrics.getNonHeapMemoryMaximum() which becomes negative.

It is required to switch non-heap memory metrics to new page memory
semantics, this should show a clean picture in the node output and will
also protect us from ambiguous -1 output.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Optimize transaction prepare step when store is enabled IGNITE-1553

[Dmitry Pavlov]

Hi Alexey,

This ticket status is 'in progress'.
Is it still in development or 'patch available' can be set?

Sincerely,
Dmitry Pavlov



ср, 7 июн. 2017 г. в 17:03, ALEKSEY KUZNETSOV :

> Hi, Igntrs!
> Feel free to reviewing the ticket
> https://issues.apache.org/jira/browse/IGNITE-1553
> https://github.com/apache/ignite/pull/2091
> --
>
> *Best Regards,*
>
> *Kuznetsov Aleksey*
>

[jira] [Created] (IGNITE-5582) CPP: Implement Compute::Broabcast() for Ignite C++

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-5582:
---

 Summary: CPP: Implement Compute::Broabcast() for Ignite C++
 Key: IGNITE-5582
 URL: https://issues.apache.org/jira/browse/IGNITE-5582
 Project: Ignite
  Issue Type: New Feature
  Components: platforms
Affects Versions: 2.0
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 2.1


Need to implement method {{Compute::Broadcast}} and {{Compute::BroadcastAsync}} 
for Ignite C++.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2187: IGNITE-5576: Added Compute::Run() for C++

[isapego]

GitHub user isapego opened a pull request:

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

IGNITE-5576: Added Compute::Run() for C++



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

$ git pull https://github.com/gridgain/apache-ignite ignite-5576

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

https://github.com/apache/ignite/pull/2187.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 #2187


commit e7311199eebbe9133f7d3cebe6f6f2a38bd67762
Author: Igor Sapego 
Date:   2017-06-22T16:13:19Z

IGNITE-5576: Added Compute::Run()

commit b6c16a5170e0f50c49096f8ba6b0e7cc33312eaa
Author: Igor Sapego 
Date:   2017-06-22T16:57:12Z

IGNITE-5576: Added tests. Fixed bug

commit 2618d312008d3961323b4b788667548c0f2b1223
Author: Igor Sapego 
Date:   2017-06-23T17:14:03Z

IGNITE-5576: Fixed config

commit efb53f9105154a32c287c02ba39c3a270ee3d2c2
Author: Igor Sapego 
Date:   2017-06-23T17:28:15Z

IGNITE-5576: Edited documentation




---
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.
---

[GitHub] ignite pull request #2177: Ignite-1.8.8.b1

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---
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.
---

[GitHub] ignite pull request #2186: Ignite-1.9.4

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

Ignite-1.9.4



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

$ git pull https://github.com/gridgain/apache-ignite ignite-1.9.4

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

https://github.com/apache/ignite/pull/2186.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 #2186


commit 9df5e94d5cf14ddd55e29b81989177a7798f7e1a
Author: dkarachentsev 
Date:   2017-02-21T12:34:59Z

IGNITE-4671 - FairAffinityFunction fails on node restart with backupFilter 
set and no backups

commit 9fcb3e74f91c8497b7b1358cdff40950cdf5c568
Author: dkarachentsev 
Date:   2017-02-28T13:05:06Z

IGNITE-4740 - Fix. Service could be deployed/undeployed twice on concurrent 
cancel and discovery event.

commit 231984d04d8391ccafb33ce995d942a9033cae44
Author: Andrey Novikov 
Date:   2017-03-01T02:49:08Z

Web console: removed legacy backend port.

(cherry picked from commit 5456caf)

commit 573624796b171b2420b87657598198f40a91f6bb
Author: Alexey Kuznetsov 
Date:   2017-03-01T15:09:40Z

Implemented support for enforce join order flag.
(cherry picked from commit a7f77d4)

commit a30183ac821507fbdaa6f0cc2c6ef25ca2677867
Author: Andrey Novikov 
Date:   2017-02-20T11:23:33Z

IGNITE-4717 Fixed hangs in VisorCacheClearTask.
(cherry picked from commit 76f3060)

commit 5f5cce4f36e6bc0a3468ba1d80fa5f3d158e927f
Author: Alexey Kuznetsov 
Date:   2017-03-01T15:09:40Z

Implemented support for enforce join order flag.
(cherry picked from commit a7f77d4)

commit 7292a5306c90d5c48c520bf9ffad388769250488
Author: Andrey Novikov 
Date:   2017-02-20T11:23:33Z

IGNITE-4717 Fixed hangs in VisorCacheClearTask.
(cherry picked from commit 76f3060)

commit 620235f3ca0fa32c1f4a4dc1a5e0bd5545f6e07e
Author: Alexey Kuznetsov 
Date:   2017-03-02T04:05:19Z

Minor cleanup.

commit 840ab997436dfad8cdbb4ad182de24bceec37962
Author: AKuznetsov 
Date:   2017-02-14T13:54:31Z

IGNITE-4436 API for collecting list of running queries and cancel them.
(cherry picked from commit 4923734)

commit bc9fcf7f6aaeba826df6a35f1a9aacb17a562337
Author: Alexey Kuznetsov 
Date:   2017-03-01T15:09:40Z

Implemented support for enforce join order flag.
(cherry picked from commit a7f77d4)

commit c2b201ed5bf4bea5dd5aa013f685fdfa02544527
Author: Evgenii Zhuravlev 
Date:   2017-03-02T07:27:13Z

IGNITE-3386 - Reentrant lock is lost when owner leaves topology

commit 3310f10b9d48d64280d0ebf2464ad892f3f31c52
Author: Alexey Goncharuk 
Date:   2017-03-02T07:37:00Z

IGNITE-3386 - Minor code style changes

commit 8362fe720779de5d3e5c7d99ec1bdb6191a38a06
Author: devozerov 
Date:   2017-03-02T14:24:59Z

Merge branch 'ignite-1.9' into ignite-1.9.1

commit 7ad8e79fa1077291c50f2f535ecccde6baee0321
Author: Evgenii Zhuravlev 
Date:   2017-03-07T11:32:28Z

ignite-4577 Add non-reachable addresses at the end of addresses list

commit 8817190e1dd31d869682df0167bb3e82fb597aad
Author: Sergi Vladykin 
Date:   2017-03-09T20:30:09Z

ignite-1.9 - SQL related fixes and improvements:
 - Sorted MERGE index
 - EXPLAIN fixes
 - Replicated subqueries fixes

Squashed commit of the following:

commit 423c2155c85ed9be8dffb3517b7331b753e1ce5c
Author: Sergi Vladykin 
Date:   Thu Mar 9 23:21:38 2017 +0300

ignite-1.9.1 - test fix

commit ff3c1f2967905b0bcac7661014656d1c080fa803
Author: Sergi Vladykin 
Date:   Thu Mar 9 11:08:34 2017 +0300

ignite-1.9.0 - replicated subqueries fix

commit bc0801a3c976f5d87cab2c414f76f69dc28b43d7
Author: Sergi Vladykin 
Date:   Wed Mar 8 16:03:40 2017 +0300

ignite-1.9.0 - fix for distributed join test

commit f1f1d96c6babaadab9e3ed1fbb3c9740c94d8209
Author: Sergi Vladykin 
Date:   Wed Mar 8 15:28:44 2017 +0300

ignite-1.9.0 - fix for distributed join test

commit a8751d535b3e025a804c441204465e94035a5247
Author: Sergi Vladykin 
Date:   Tue Feb 28 18:46:07 2017 +0300

ignite-1.9 - splitter fixes

commit 0601ce6e291eb4689d526e922b02fd9e21df5b08
Author: Sergi Vladykin 
Date:   Sun Feb 26 23:24:14 2017 +0300

ignite-1.9 - merge index test

commit 

cannot build ignite 2.1.0

[ALEKSEY KUZNETSOV]

Cannot build apache ignite 2.1.0 package. Build fails on ignite-hadoop
module :
Could not find artifact org.apache.ignite:ignite-core:jar:2.1.0-SNAPSHOT in
h2database.com (http://h2database.com/m2-repo)

http://h2database.com/m2-repo/org/apache/ignite/ignite-core/2.1.0-SNAPSHOT/ignite-core-2.1.0-SNAPSHOT.jar

-- 

*Best Regards,*

*Kuznetsov Aleksey*

[GitHub] ignite pull request #2185: IGNITE-5581

[gvvinblade]

GitHub user gvvinblade opened a pull request:

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

IGNITE-5581



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

$ git pull https://github.com/gridgain/apache-ignite ignite-gg-12168

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

https://github.com/apache/ignite/pull/2185.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 #2185


commit 2b0741039e7cc6e36871b97bab53780edfc84648
Author: Ilya Lantukh 
Date:   2017-06-13T12:38:55Z

ignite-5267 : Removed redundant test.

commit 4a86cae203ed9aed953cd6093884cf8cab4531e3
Author: Dmitriy Govorukhin 
Date:   2017-06-13T12:48:39Z

ignite-2.1.1 fix state processor, skip if daemon

commit 5c567aeb5458159bc41dbd251dfa8a65701f4861
Author: Ivan Rakov 
Date:   2017-06-13T13:06:42Z

ignite-2.1.1 moving pds tests that depend on indexing to separate suite

commit 5e9d9ebc1140f9647fc1b325ba81d0ad6c2c69f3
Author: Dmitriy Govorukhin 
Date:   2017-06-13T13:21:20Z

ignite-2.1.1 Added description to MX bean

commit 2c2a9e652b13cf60b7e878a4e20f4ab4ae014e9c
Author: Dmitriy Govorukhin 
Date:   2017-06-13T13:21:39Z

Merge remote-tracking branch 'professional/ignite-2.1.1' into ignite-2.1.1

commit 9141b3698d0ec98e512efbc78864cc06781fd8c7
Author: devozerov 
Date:   2017-06-13T13:32:28Z

IGNITE-5267: Fixed too early StoredCacheData initialization.

commit 0a00f03da78649320cb0bb3579f44d6fe037facc
Author: devozerov 
Date:   2017-06-13T13:32:58Z

Merge remote-tracking branch 'upstream/ignite-2.1.1' into ignite-2.1.1

commit 2d8c6519d36e2d7890a45b258d3b7439942dca66
Author: Dmitriy Govorukhin 
Date:   2017-06-13T13:39:13Z

ignite-2.1.1 Add joining node tests

commit c5cee32a510e5a3524ff88119acfd1963c74d8ad
Author: Dmitriy Govorukhin 
Date:   2017-06-13T13:39:30Z

Merge remote-tracking branch 'professional/ignite-2.1.1' into ignite-2.1.1

commit d369dfc4973c179861d1d2ff37fbe8c6c0543d1a
Author: Ivan Rakov 
Date:   2017-06-13T13:47:22Z

ignite-2.1.1 IgniteSpringDataTestSuite - added vm ip finder

commit ab62ce847cb73854f31f1232144f487786a6a3d1
Author: Pavel Kovalenko 
Date:   2017-06-08T21:30:41Z

IGNITE-5267 Remove entry from on-heap locks map if it was removed from 
off-heap

commit 33a9cc4cf9b32d93e34c5855d52ce208a3fd8228
Author: Pavel Kovalenko 
Date:   2017-06-08T21:33:30Z

IGNITE-5267 Deserialize binary object explicitly instead of calling cache. 
Small refactoring.

commit 95257a16aef0bc0bbacdee03503ee483ffc75bda
Author: Pavel Kovalenko 
Date:   2017-06-08T21:34:37Z

IGNITE-5267 Small test refactoring and speeding up

commit e2354cb5ea8965276c3696895c86e51315765571
Author: Pavel Kovalenko 
Date:   2017-06-08T21:37:38Z

IGNITE-5267 Fixed and simplified test

commit 41cea0bc2f887881a78436e54143313af27e7fa8
Author: Pavel Kovalenko 
Date:   2017-06-08T21:38:55Z

IGNITE-5267 Make partitionMapExchange timeout configurable

commit 8e1439782b993c8ccb974bcdbd55d4f2b28a5489
Author: Pavel Kovalenko 
Date:   2017-06-08T21:40:53Z

IGNITE-5267 Use owners instead of nodes to properly check finishing of 
partitionMapExchange

commit ef732dae02673c2ce79575b57454a573f0d1d591
Author: Pavel Kovalenko 
Date:   2017-06-08T21:42:00Z

IGNITE-5267 Provide entry key explicitly in cache queries. Fixed test.

commit 5eb40528bd6e52b4c13a4c21ecca74407b081898
Author: Pavel Kovalenko 
Date:   2017-06-08T21:42:34Z

IGNITE-5267 Explicitly fail test with known issue

commit e4f203b512cba1dc8ae82b506cadebfed3fd7f65
Author: sboikov 
Date:   2017-06-13T13:58:12Z

review

commit fd7050c72c8125ed1dd213ef781bdb9971d00413
Author: Dmitriy Govorukhin 
Date:   2017-06-13T14:02:54Z

ignite-2.1.1 Add joining node tests in suit

commit 3e509aa604ca342b3f42a73e771a5a4f678d7132
Author: Ivan Rakov 
Date:   2017-06-13T14:13:43Z

ignite-2.1.1 Fixing compilation in tests

commit dea416fa65874d4e33b37b46368f9e476a3904f4
Author: dpavlov 
Date:   2017-06-13T15:00:32Z

Merge fix: 4.ea2 into 5267: remove node is loopback check

commit b52a84e885b0f88971290200942e0bbe01252ff6
Author: sboikov 
Date:   2017-06-13T15:09:41Z

Merge remote-tracking branch 'remotes/origin/master' into ignite-2.1.1

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/internal/IgniteDiagnosticAware.java
#   

[jira] [Created] (IGNITE-5581) Local caches aren't stored

[Igor Seliverstov (JIRA)]

Igor Seliverstov created IGNITE-5581:


 Summary: Local caches aren't stored
 Key: IGNITE-5581
 URL: https://issues.apache.org/jira/browse/IGNITE-5581
 Project: Ignite
  Issue Type: Bug
  Components: persistence
Reporter: Igor Seliverstov
Assignee: Igor Seliverstov






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2184: IGNITE-5425 JDBC thin: support client info

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-5425 JDBC thin: support client info



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

$ git pull https://github.com/gridgain/apache-ignite ignite-5425

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

https://github.com/apache/ignite/pull/2184.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 #2184


commit 089065ad8c7efdc3f43249a95cb5c7747a61e648
Author: tledkov-gridgain 
Date:   2017-06-23T14:20:45Z

IGNITE-5425 JDBC thin: support client info




---
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.
---

I am a new Ignite Development Community member

[Alexey Kukushkin]

Dear Ignite Development Community,
I am a software engineer and joined the community to contribute to the product. 
Could you please help with granting me proper Ignite Jira permissions? My Jira 
user ID is "kukushal". Thank you!

Best regards, Alexey

Re: Cassandra configuration SO question

[Igor Sapego]

Andrey,

You are right. Somehow, I have not noticed that.
Thanks for your help.

Best Regards,
Igor

On Thu, Jun 22, 2017 at 8:27 PM, Andrey Gura  wrote:

> I've commented first reply to the question. But actualy I didn't test it.
>
> On Thu, Jun 22, 2017 at 8:24 PM, Andrey Gura  wrote:
> > org.*h2*.jdbc.JdbcSQLException
> >
> > It isn't realted with JDBC. He uses schema name instead of table name
> > for insert.
> >
> > On Thu, Jun 22, 2017 at 2:41 PM, Igor Sapego  wrote:
> >> There is still no reply for this ticket. Who can take a look?
> >> Val? Andrey?
> >>
> >> Best Regards,
> >> Igor
> >>
> >> On Tue, Jun 20, 2017 at 2:37 AM, Igor Rudyak  wrote:
> >>
> >>> Hi guys,
> >>>
> >>> According to the exception it looks like a JDBC  problem, rather than
> >>> Cassandra related staff. As I remember Ignite JDBC (1.8 version for
> sure)
> >>> uses some weird names for the tables like *. >>> name>*.
> >>>
> >>> Because of this you just can't simple do "*select * from my_cache*",
> but
> >>> should do something like "*select * from
> my_cache.my_java_class_name*". I
> >>> assume that in insert statement you should also use
> >>> *cache1.my_java_class_name* instead of just *cache1*.
> >>>
> >>>
> >>>
> >>> Igor
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> On Mon, Jun 19, 2017 at 4:03 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> >>> wrote:
> >>>
> >>> > Igor, which Igor are you asking? (no pun intended) Perhaps it makes
> sense
> >>> > to explicitly add him to CC.
> >>> >
> >>> > D.
> >>> >
> >>> > On Mon, Jun 19, 2017 at 4:17 PM, Igor Sapego 
> wrote:
> >>> >
> >>> > > Igor,
> >>> > >
> >>> > > Can you please take a look at this question at SO?
> >>> > >
> >>> > > https://stackoverflow.com/questions/44589774/configure-
> >>> > > apache-ignite-cache-with-cassandra-and-odbc/44630522
> >>> > >
> >>> > > Best Regards,
> >>> > > Igor
> >>> > >
> >>> >
> >>>
>

[GitHub] ignite pull request #2183: IGNITE-5528 - IS_EVICT_DISABLED flag is not clear...

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

IGNITE-5528 - IS_EVICT_DISABLED flag is not cleared on cache store exception

Fixed.

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

$ git pull https://github.com/gridgain/apache-ignite ignite-5528

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

https://github.com/apache/ignite/pull/2183.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 #2183


commit 29e2499100b4f559eb3ee7e877d099f6983cbd74
Author: Alexey Goncharuk 
Date:   2017-06-20T04:59:09Z

IGNITE-5528 - IS_EVICT_DISABLED flag is not cleared on cache store 
exception.




---
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.
---

[GitHub] ignite pull request #2182: IGNITE-5552: ServiceProcessor recalculates all se...

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

IGNITE-5552: ServiceProcessor recalculates all service assignments even if 
there is a pending topology change

Fixed.

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

$ git pull https://github.com/gridgain/apache-ignite ignite-5552

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

https://github.com/apache/ignite/pull/2182.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 #2182


commit 3464a79b560106d47dd5cf0bae4b21dce7778e9d
Author: Andrey V. Mashenkov 
Date:   2017-06-21T16:30:27Z

IGNITE-5552: ServiceProcessor recalculates all service assignments even if 
there is a pending topology change.




---
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-5579) Make sure identical binary metadata updates from the same node do not happen twice

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5579:


 Summary: Make sure identical binary metadata updates from the same 
node do not happen twice
 Key: IGNITE-5579
 URL: https://issues.apache.org/jira/browse/IGNITE-5579
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Affects Versions: 1.7
Reporter: Alexey Goncharuk
 Fix For: 2.1


It is possible that multiple user threads attempt identical binary metadata 
update concurrently. In this case, a node will just increase contention on the 
cache key, but once the lock is acquired there will be nothing changed. On 
large topologies, this may lead to nodes waiting for the metadata update for 
hours (!).
We should work out a way to identify identical metadata updates and allow only 
one thread to proceed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5578) Discovery events coalescing

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5578:


 Summary: Discovery events coalescing
 Key: IGNITE-5578
 URL: https://issues.apache.org/jira/browse/IGNITE-5578
 Project: Ignite
  Issue Type: Improvement
  Components: cache, general
Affects Versions: 1.0
Reporter: Alexey Goncharuk
 Fix For: 2.1


There is an issue that has been in Ignite long ago and with the growing 
community and growing cluster sizes, it becomes more tangible.

When a bunch of nodes leave or join cluster, we generate a separate discovery 
event for each node, and each discovery event generates a partition map 
exchange. 
The first idea that came to my mind was to coalesce the partition map 
exchanges, but this is extremely difficult to implement on unstable topology.
Instead, we can introduce NODES_JOINED / NODES_FAILED events and batch multiple 
events on discovery level when possible. In this case, very few extra partition 
map exchanges are possible.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] ignite pull request #2181: IGNITE-5454

[gvvinblade]

GitHub user gvvinblade opened a pull request:

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

IGNITE-5454



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

$ git pull https://github.com/gridgain/apache-ignite ignite-5454

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

https://github.com/apache/ignite/pull/2181.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 #2181


commit c6bba4b3b1857ab592d6e322ae6eb5766034c4f7
Author: Igor Seliverstov 
Date:   2017-06-23T08:16:21Z

IGNITE-5454




---
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.
---

Ignite JDBC and "Runnable tasks outlived thread pool executor service"

[Igor Rudyak]

Hi,

I am using Ignite 2.0.0 JDBC driver and when my queries exceed 12sec
timeout I am reciving such an error:

*Runnable tasks outlived thread pool executor service*


Any ideas on this?

Igor