Hello,
I have some operations which does not care about the order, e.g., each
operation is to increase the key value by 1 or decrease by 1.
So I need a lock to protect each key on read and write. Also I need to put
operations in transaction, since ignite will handle the commit and rollback.
On Monday, October 30, 2017, iostream wrote:
> So the transactional guarantees apply only to cache.get() and cache.put()
> category of APIs?
>
> Yes
> What about SqlFieldsQuery? Does it also support transactional
> commits/rollbacks?
>
>
SQL fields queries fall in the
So the transactional guarantees apply only to cache.get() and cache.put()
category of APIs?
What about SqlFieldsQuery? Does it also support transactional
commits/rollbacks?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Denis,
We should definitely print out a thorough warning if HashMap is passed into
a bulk method (instead of SortedMap). However, we should make sure that we
only print that warning once and not ever time the API is called.
Can you please file a ticket for 2.4?
D.
On Thu, Oct 26, 2017 at 11:05
Hi All,
We are seeing deadlocks, causing a node failed to start for the below
scenario:
1) Two nodes (Node 1 & Node 2) are started-up at the same time.
2) Once the caches are loaded and ready, bring down one node (Node 2).
3) With in a brief duration (~minute time), start again the node (Node 2)
Thanks Alexey. Yes that was it. I wish the documentation had these details.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Thanks much Andrey & Dmitry, the solution is working.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Denis,
Sure. No problem.
Is it possible to reference the article that I have published on LinkedIn
here?:
https://www.linkedin.com/pulse/apache-ignite-visualize-ga-grid-solutions-deep-turik-campbell/
Please advise.
Best,
Turik
--
Sent from:
Hi,
1. Assume I write data item X with a FULL_ASYNC write synchronization mode,
what happens if I immediately attempt to read X? Will I read an old value
or do I wait till the previous writes are completed?
2. If the write mode is PRIMARY_ASYNC, will the immediate read operations
on X get
Hi,
It is very rough estimations.
1. Recommended minimal heap size for server node is 512Mb.
If you plan to retrieve large dataset with getAll or some queries with
large page size, you should bother with requested data will fit in memory.
Also JVM GarbageCollector feels much better if there is
Hi Turik,
Happy to see you keep developing the component! Thanks for giving an update on
this.
Could you write a blog post about Zeppelin usage? You can use your personal
blog and we will add a reference to a post to this page:
https://ignite.apache.org/blogs.html
—
Denis
> On Oct 29, 2017,
Hi,
IgniteCache.query() method requires CACHE_READ permission,
but looks like all JDBC clients bypass security checks.
On Mon, Oct 30, 2017 at 5:27 PM, calebs wrote:
> Hi Andrew,
>
> Then, does JDBC "thick" client have the support security plugin? The
> security includes
Hi,
I am trying to work with and modify the underlying cache of a RDD, however,
I can not seem to access any values or iterate through it.
The premise behind the algorithm is there is no good way to do this in an
RDD fashion as each row operation modifys multiple row values. I can do this
on the
Hi, I've created issue for this case:
https://issues.apache.org/jira/browse/IGNITE-6792
Reproducer is attached to JIRA, also test was added into branch.
According to my brief testing, cache.size() method also returns less count
than initial load.
Sincerely,
Dmitriy Pavlov
пт, 27 окт. 2017 г. в
Hi Rajiv,
Seems, it is same issue as IGNITE-6380.
I see tread blocks on dynamic cache for ignite datastructures creation.
[1] https://issues.apache.org/jira/browse/IGNITE-6380
On Sat, Oct 28, 2017 at 12:15 AM, rajivgandhi
wrote:
> Hi,
> In line with a deadlock
Hi Andrew,
Then, does JDBC "thick" client have the support security plugin? The
security includes User Authentication and Authorization.
In GridCacheContext, I see the following method
/**
* @param op Operation to check.
* @throws SecurityException If security check failed.
Dmitry,
Yes, you are right. we should broadcast a job with local scan queries.
On Mon, Oct 30, 2017 at 4:54 PM, Dmitry Pavlov
wrote:
> Hi Andrey, should we limit scan query to be executed only for current node
> here with setLocal() method?
>
>
> пн, 30 окт. 2017 г. в
Hi Andrey, should we limit scan query to be executed only for current node
here with setLocal() method?
пн, 30 окт. 2017 г. в 16:48, Andrey Mashenkov :
> As a workaround you can try to broadcast a task :
>
> Collection res =
>
As a workaround you can try to broadcast a task :
Collection res =
ignite.compute(ignite.cluster().forCacheNodes("mycache")).broadcast(
new IgniteCallable() {
/** Auto-inject ignite instance. */
@IgniteInstanceResource
private
Hi,
This is known bug that transformer applies only to first page of results.
Here is a ticket [1]
[1] https://issues.apache.org/jira/browse/IGNITE-5804
On Sat, Oct 28, 2017 at 8:57 AM, naresh.goty wrote:
> Hi All,
>
> We are seeing an issue with calculating size of
Hi Caleb,
JDBC thin client have no support security plugin for now.
If you don't need full permissions support for sql objects (i mean "GRANT"
operation),
but just restrict unauthorized access to grid, then you can wait for
IGNITE-6625 [1] and try JDBC via SSL.
[1]
Hi,
Ignite will be able to read data.
Community decided to maintain backward compatibilty of persistent store at
least for minor versions. Also there are several tests checking this
compatiblity.
Sincerely,
Dmitriy Pavlov
пн, 30 окт. 2017 г. в 14:49, Paulus de B.
Hi, does anyone know if e.g. version 2.3 will be able to read 2.2 persisted
data (Ignite native persistence)? Will this be true for future releases as
well?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Anand,
Can you share your CacheStore implementation?
Do you use CacheStoreAdapter<>?
Very probably you don't have your own "CacheStore.writeAll()" implementation
that is used for batches. And the default one is used (it just sequentially
calls "CacheStore.write()" for all entries in a batch).
Dear support team,
I am trying to estimate memory efficiently available for cache payload in
cluster. I base my calculation on
https://apacheignite.readme.io/docs/capacity-planning. Can you please
confirm that the following formula gives rough but realistic estimation of
memory available for
Hi blackfield,
I can't reproduce the issue with changing number of backups when cache was
re-created.
On Fri, Oct 27, 2017 at 8:45 PM, blackfield
wrote:
> @Andrew Mashenkov, I notice that you opened IGNITE-6781.
> However, I actually destroyed the original cache
Igor, thank you for assistance in clarifying this issue. It really seems to
be specific to configuration of Excel ODBC connections rather than
specifically Ignite ODBC driver.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Thank you for your response, I will look further into the problem and see if
I can find any workarounds.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Could you put the cache configuration and the sample code?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
After few days (2/3) of load testing I am getting below exceptions:-
[04:20:06,294][ERROR][sys-stripe-3-#4%LoginServices%][GridCacheIoManager]
Failed processing message [senderId=b2df236f-4fba-4794-b0e4-4e040581ba9d,
msg=GridNearAtomicSingleUpdateRequest [key=KeyCacheObjectImpl [part=243,
Hi Folks,
Under load testing after few days (2/3) days of run I am getting below
exception:-
org.apache.ignite.IgniteException: Failed to create string representation of
binary object.
at
31 matches
Mail list logo