Hi,
Can you show the server node log?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Issue-with-Ignite-Zeppelin-tp14990p15014.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi Narayana,
Can you show the code that is working and that code that is not working?
Also note that SQL queries are currently not enlisted in transactions
anyway, so most likely you're not having semantics that you expect.
Transactional support for SQL is expected sometime this year.
-Val
--
If you mean that it hangs, then please attach thread dump.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Unable-to-start-the-ignite-sh-in-verbose-mode-tp14477p14607.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi Aiden,
Technically this should be done as I already described on SO [1]. You will
need to remodel the data so that the portion of data used for collocation is
represented as a separate field, this field has to be part of key object and
configured as affinity key.
[1]
https://stackoverflow.com/
Hi Saji,
Kill command kill the process, it's designed more for standalone server
nodes rather than embedded clients. What is the condition when you may want
to stop the client?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Can-java-code-look-up-cache-in-
I would also add that 2.1 will have brand new persistence storage that will
make all cache work transparently across memory and disk. You will not have
to worry about where the particular data actually resides.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.co
Hi Lei,
Currently you can create a data frame only based on result set of a query,
and this data frame will be local. We don't have support for data frames
yet. And in case you're not using SQL, then Ignite is actually schema less.
-Val
--
View this message in context:
http://apache-ignite-us
If you implement Hive over HDFS, there is no reason to have IGFS in the first
place.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Cache-over-HDFS-tp13553p14515.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi,
I'm not sure it even make sense. If transaction is rolled back, all values
included in this transaction are rolled back, so you have to retry the whole
transaction. If you have frequent conflicts, then you should consider using
pessimistic transaction instead.
-Val
--
View this message in
Jeff,
Consistency here means that queries never return partial updates. I.e.
atomicity is guaranteed. However, queries are always executed outside of
transactional scope, even if there is a ongoing transaction in the same
thread. Basically, if transaction commits 2 entries, concurrently executed
q
Sam,
To avoid deserialization you can set CacheConfiguration#copyOnRead to false.
As for clear(), there is no notification for it. Who triggers it? Can the
client that calls clear(), then execute whatever needs to be executed as a
post-action? You can use compute APIs for this, for example.
-Val
You can read here about user attributes:
https://apacheignite.readme.io/docs/cluster#cluster-node-attributes
For the node filter example, refer to JavaDoc:
https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/util/AttributeNodeFilter.java
-Val
--
View this
Hi Jeff,
Transactional consistency and MVCC is (and always will be) available only
for transactional caches. But for queries MVCC is not supported at all yet.
Queries are not enlisted in transactions and therefore you can get dirty
reads. Full support will be added by the end of the year (hopefull
Rishi,
Does the issue go away if you stop triggering monitoring every 5 minutes.
Such frequency is very small, it should not cause any issues of course.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/frequet-disconnection-in-ignite-cluster-tp14411p14505.h
Hi Priya,
You can provide path explicitly to open command:
open -cpath /path/to/xml
As for cache size, are you using 2.0? If yes, do you have on-heap cache
enabled?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Visor-Help-tp14481p14504.html
Sent
Sam,
It sounds like you can set CacheConfiguration#invalidate property to true.
This will force Ignite to invalidate near cache entry on update rather that
syncing it with a new value. Is this what you're looking for?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.n
Hi,
Can you please tell what is a business use case behind this? What exactly
are you trying to achieve with Ignite?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Loading-similar-data-to-specific-instance-and-not-all-instances-tp14387p14502.html
Sent fro
Hi,
Riccardo Iacomini wrote
>- Will a local file system persistence strategy be available in future
>releases of Ignite?
The new disk storage will be available in 2.1.
Riccardo Iacomini wrote
>- Using the write-behind mode, will operations on the cache still be
>mapped 1 on 1 o
Hi,
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Info-tp14473p14499.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
It's something in your network. If you can't telnet to this address, Ignite
will obviously not able to connect either.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Connecting-to-remote-host-from-client-gives-error-tp14395p14498.html
Sent from the Apache
Where is the error?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Unable-to-start-the-ignite-sh-in-verbose-mode-tp14477p14496.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Artem,
The whole point of service proxy is to allow remote execution via API that
*you* created. Therefore, if this API returns some result, this can be done
only synchronously. In case there is no result, you can trigger async
execution within the service itself and return right away. Another opt
Vladimir wrote
> It is just a test. In real project, of course, there are many nodes
> holding the cache. Node A represents a part of cluster.
You can lose the whole cluster group as well. My point is that getting in
cache during initialization doesn't make it safe, because cache can
disappear in
Hi Rishi,
ignite.cluster().nodes() will give the list of nodes and full information
about topology. Will this work for you?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-1-6-0-suspected-memory-leak-from-DynamicCacheDescriptor-tp9443p14492.html
Sen
Then it might be blocked by firewall. These messages simply mean that client
can't establish connection with this socket address.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Connecting-to-remote-host-from-client-gives-error-tp14395p1.html
Sent from
Srini,
Please refer to [1] for information on how to use the store and
configuration examples.
If default port is not 9042, then I don't see an issue. You have to either
explicitly specify your default port, or provide all addresses as host:port
strings.
[1] https://apacheignite-mix.readme.io/do
Hi Czeslaw,
Please properly subscribe to the mailing list so that the community can
receive email notifications for your messages. To subscribe, send empty
email to user-subscr...@ignite.apache.org and follow simple instructions in
the reply.
cszczotka wrote
> I’m using cache with read-through/w
You're starting a client node and it connect to server cluster. Do you have
any server nodes?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Connecting-to-remote-host-from-client-gives-error-tp14395p14434.html
Sent from the Apache Ignite Users mailing list
Hi,
Please take a look and play with examples provided by Ignite:
https://github.com/apache/ignite/tree/master/examples/src/main/java/org/apache/ignite/examples/computegrid
They show how to do this kind of basic operations.
-Val
--
View this message in context:
http://apache-ignite-users.705
Hi,
What exactly is consuming the memory? Do you have a heap dump?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-0-vs-Ignite-1-7-or-later-tp14401p14432.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Sam,
What is the business use case behind this?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Event-Listeners-tp8306p14431.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Tom,
It sounds like these jobs are triggered pretty frequently. So why not create
a small application that will create an embedded client once and also have
an internal timer or cron based scheduler to execute jobs periodically. You
can do the topology check within this application as well, instea
iostream wrote
> Hi,
>
> I have 2 caches, each with POJO values that look like -
>
> public class Value1 {
>
> @QuerySqlField(index = true)
> private Long a;
>
> @QuerySqlField(index = true)
> private String b;
>
> }
>
> public class Value2 {
>
> @QuerySqlField(
Hi,
Please properly subscribe to the mailing list so that the community can
receive email notifications for your messages. To subscribe, send empty
email to user-subscr...@ignite.apache.org and follow simple instructions in
the reply.
--
View this message in context:
http://apache-ignite-use
Priya,
There are no configuration properties that can be changed in runtime.
However, most of your requirements seem to be related to dynamic schema
change. This already happens transparently on object level thanks to binary
format [1] used as a default data storage format. On SQL level this will
Alexander,
It doesn't matter if you use SQL. Without SQL it should work though. Did you
get any exception when you tried this?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Mix-in-cache-keys-objects-with-different-types-tp14354p14426.html
Sent from the A
Hi Alexander,
Ticket for this already exists for a while:
https://issues.apache.org/jira/browse/IGNITE-5189
You can try to set java.net.preferIPv4Stack=true system property, usually it
helps to avoid this exception.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.na
Hi Alexander,
This function provided inconsistent mapping for caches created on different
topology versions. Basically this means that collocation was not working
properly in some scenario, so we decided to get rid of this function. Please
use RendezvousAffinityFunction instead.
-Val
--
View t
Hi,
See CacheConfiguration#nodeFilter property. It's just a predicate that
filters out nodes, cache will be deployed only on those for which filter
returns true. The easiest way would be to set custom attributes via
IgniteConfiguration#userAttributes and filter out using AttributeNodeFilter
which
Try to set java.net.preferIPv4Stack=true system property on all nodes.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Starting-the-Server-tp14398p14422.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi Roger,
This is a known issue: https://issues.apache.org/jira/browse/IGNITE-5189
Try to set java.net.preferIPv4Stack=true system property.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Unable-to-connect-from-Windows-Java-client-to-Linux-server-cluster
Rishi,
This is usually caused by either network or memory issues. Check that you
don't have any network glitches and that there are no GC pauses, memory
leaks, etc. on the nodes.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/frequet-disconnection-in-igni
Hi Srini,
Is Cassandra listening to port other than 9042?
Also how do you configure Cassandra store? connection.properties file is
used only in tests, Ignite doesn't actually provide this way of configuring.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com
Hi Stephen,
Please properly subscribe to the mailing list so that the community can
receive email notifications for your messages. To subscribe, send empty
email to user-subscr...@ignite.apache.org and follow simple instructions in
the reply.
macdonagh wrote
> Are there logs which will show the
Hi Roger,
It's perfectly fine to use UUID as a key. In case of composite key I would
recommend to create a class with multiple fields to encapsulate all values
there.
Auto generation is not supported, at least for now.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6
Hi Sam,
Continuous queries only work with data update operations like put, remove,
etc. So to get notification you should use remove() method instead of
clear(). If you have a persistence store and you don't want to remove from
there, you can do this as a workaround:
cache.withSkipStore().remove(
BTW, in 2.1 Ignite will introduce persistence storage that will allow to
execute SQL queries without preloading data into memory.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Web-Console-query-on-Oracle-database-cache-return-empty-resultset-tp13546p14360
Hi Alexander,
Having a separate cache per data type always was recommended, as it provides
better isolation of data sets from each other, and therefore less error
prone. In 2.0 this became a requirement due to architectural changes and
leaning towards SQL database.
-Val
--
View this message in
Hi Raymond,
Got it. Feel free to let us know in case you have more information. I would
great to have more insight and improve performance if needed.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Possible-race-condition-when-starting-up-Ignite-nodes-taki
Hi Artem,
I think the only way to do this synchronously and consistently is to
manually load all required objects from database and put them all within a
single transaction.
You can't do synchronous updates in continuous query listener as it can
cause a deadlock.
-Val
--
View this message in
Hi,
Is it the same issue that is discussed in
http://apache-ignite-users.70518.x6.nabble.com/Streaming-test-td14039.html?
Someone will take a look at your project and respond there.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Use-AtomicLong-or-AtomicSe
Hi Steve,
Community doesn't do maintenance releases, so you will have to do the build
by yourself.
Also there are 3rd party vendors like GridGain (www.gridgain.com) that
provide professional support for Ignite and can help you with this.
-Val
--
View this message in context:
http://apache-ig
Hi Alexander,
We need to understand why null appeared there and fix this root cause
instead of fixing the consequence. Do you have any tests that you can share?
Also would be great is you create a Jira ticket and send a message to dev
list, this discussion belongs there I think.
-Val
--
View
Hi Raymond,
What exactly is slower? Can you provide any tests?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Possible-race-condition-when-starting-up-Ignite-nodes-taking-part-in-partition-affinity-map-tp14293p14349.html
Sent from the Apache Ignite Users
Prashant,
This is maximum heap size controlled by JVM Xmx property. I guess you just
set the same for both server and client.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Apache-heap-getting-increase-with-cacheConfig-setCopyOnRead-as-false-tp14175p14348
Hi Vladimir,
Vladimir wrote
> Node B must know wheter the cache is already created. If not it must not
> start to avoid such runtime problems. That's why the cache is acquired at
> the initialization. That looks like reasonable and comfortable way.
What is the exact scenario when cache is not av
Hi Priya,
Cache configuration can't be changed in runtime in any of the versions. What
properties are you looking to change exactly?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Dynamically-update-the-Cache-Configuration-without-restsrting-client-and-se
Did you check the execution plan? Is index properly used? Also how big is
result set returned by the query before 'limit 10' is applied?
BTW, it's generally not valid to do 'limit 10' without ordering, as you can
get different results from consequent execution of the same query with the
same data
Hi,
Please properly subscribe to the mailing list so that the community can
receive email notifications for your messages. To subscribe, send empty
email to user-subscr...@ignite.apache.org and follow simple instructions in
the reply.
abhishek dutta gupta wrote
> I have query on how we can acces
Hi Austin,
Can you ask Camel community about this? I'm not sure if this is a valid test
or not.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Using-Camel-Ignite-for-inserting-json-object-to-Ignite-s-Cache-tp13513p14296.html
Sent from the Apache Ignite Us
abhishek dutta gupta wrote
> Can we write custom query? How good is the query part of this apart from
> Infinispan? What are the advantages rather than Infinispan?
Ignite fully supports SQL querying, so you can execute any query that is
possible with SQL.
abhishek dutta gupta wrote
> How we can
No, this can be done only via QueryEntity.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/assign-alias-for-table-name-using-annotations-tp13759p14292.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi Dmitri,
I think the answer is no. What's is the purpose of this?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/cache-insert-update-performance-tp14049p14291.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi Gordon,
Separate cache per type is recommended approach. Feel free to use it.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Modelling-Question-tp14087p14290.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
What is IgniteDictionaryMapper class? It creates cache within Spring bean
initialization, and then the cache tries to acquire a bean for cache store
in another thread. This thread tries to acquire the same Spring lock which
causes a deadlock. See 'main' thread in the same thread dump.
I think you
This thread is a duplicate:
http://apache-ignite-users.70518.x6.nabble.com/How-to-create-a-dump-of-updated-data-in-cache-into-local-td14268.html
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/How-to-create-a-dump-of-updated-data-in-cache-tp14269p14288.html
Responded on SO:
https://stackoverflow.com/questions/44884312/ignite-data-backup-in-hard-disk
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/How-to-create-a-dump-of-updated-data-in-cache-into-local-tp14268p14287.html
Sent from the Apache Ignite Users maili
Prashant,
Do you mean that you have a client and a server on the same box? If so, why
do you need that? Client node is also a JVM process and it will always
consume some memory. Of course, much less than server as it doesn't store
data.
-Val
--
View this message in context:
http://apache-igni
Read-through doesn't work with SQL queries, only with key based access.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Web-Console-query-on-Oracle-database-cache-return-empty-resultset-tp13546p14285.html
Sent from the Apache Ignite Users mailing list archi
Devis,
Suggestion would be not to create a new thread for each request :)
It looks like you're using some kind of framework, so don't know how this
should be done properly there, but generally thread creation is a heavy
operation by itself, so it's always better to use thread pools.
Additionally,
This looks like a network issue. Please check that connections can be
established between any nodes in topology and nothing is blocked by
firewall. Note that connectivity must be bidirectional, even for clients
(i.e. server node can establish TCP connection with client node). Also note
that both di
Hi Ryan,
Yes, I think. But note that will create a high contention on this method -
each job request will acquire the same lock. Although, it's probably not an
issue in your case as you do not allow to execute more than one job at a
time anyway.
-Val
--
View this message in context:
http://ap
Muthu,
IgniteAtomicSequence generates unique long value, while IgniteUuid is a
heavier object. Other than that, they provide similar guarantees.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Grid-Cluster-unique-UUID-possible-with-IgniteUuid-tp13574p14281
If you're reloading data from IGFS to a regular cache, why do you need IGFS
in the first place? Why not load data directly in the cache?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/IGFS-Question-tp13447p14280.html
Sent from the Apache Ignite Users maili
Hi Doug,
_key is implicitly indexed, no need to configure additional index for it.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/odd-query-plan-with-joins-tp13680p14279.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
nash1k wrote
> hi!
> Did you resolve this problem? We have the same issue and can't do anything
> with it. Yep cassandra is under high load but how we can fix it? More
> cassandra nodes or more ignite nodes? Or may be there are some hacks?
> (read through, write through, write behind with batches a
There is no way to do this in 2.0. You'll have to wait for 2.1.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Fetch-column-names-in-sql-query-results-tp14089p14277.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Prashant,
To avoid what? Why did you set copyOnRead to false in the first place?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Apache-heap-getting-increase-with-cacheConfig-setCopyOnRead-as-false-tp14175p14190.html
Sent from the Apache Ignite Users maili
Please attach full verbose logs and thread dumps from both nodes.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/NodeFilter-for-cache-and-GridDhtPartitionsExchangeFuture-Failed-to-wait-for-partition-release-future-tp14179p14185.html
Sent from the Apache Ig
Prashant,
Ignite always stores binary representation of an object. Whenever you read
it, its is deserialized which actually creates a copy. In case copyOnRead is
set to false, deserialized object if also cached so that deserialization
step is skipped. But this doubles memory consumption.
-Val
What threads are left behind? Do you have a thread dump that you can show?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Server-node-fails-to-start-with-exception-IllegalThreadStateException-tp14150p14171.html
Sent from the Apache Ignite Users mailing lis
Hi Sumanta,
The way how nodes discover each other depends only on discovery
configuration, it doesn't matter if nodes are started in embedded or
standalone mode. Please refer to [1] for all available options. On Google
Cloud you can use native integration [2].
[1] https://apacheignite.readme.io/d
Saji,
You're using try-with-resources syntax, which calls Ignite.close() at the
end and therefore stops the node. Getting rid of it will do the trick.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Can-java-code-look-up-cache-in-server-without-Ignition-st
Ryan,
Yes, this is about IgniteMessaging API.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Concurrent-job-execution-and-FifoQueueCollisionSpi-parallelJobsNumber-1-tp8697p13586.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Ryan,
I added a comment in the ticket. I would recommend you to set the size of
public thread pool to 1 (IgniteConfiguration#publicThreadPoolSize) to make
sure that jobs are not executed in parallel.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Concurre
Agree :)
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Swapping-to-Disk-Ignite-2-0-tp13522p13578.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi,
Please properly subscribe to the mailing list so that the community can
receive email notifications for your messages. To subscribe, send empty
email to user-subscr...@ignite.apache.org and follow simple instructions in
the reply.
Artёm Basov wrote
> Lets take example from
> https://apachei
Continuous queries are independent from each other and both will get all
required notifications with exactly-once guarantee.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Two-Continuous-Queries-listening-to-same-event-tp13571p13575.html
Sent from the Apac
Hi Austin,
I'm probably missing something, but why do you expect this to insert entry
into cache? Where did you find the syntax below?
.to("ignite-cache:cache:myCacheName?operation=PUT")
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Using-Camel-Ignite-f
For on-heap memory you can use eviction policies:
https://apacheignite.readme.io/docs/evictions
For off-heap limit is specified in CacheConfiguration#offHeapMaxMemory
property.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Swapping-to-Disk-Ignite-2-0-tp13
Raja,
First of all, it sounds like entry processor fits your use case a bit
better: https://apacheignite.readme.io/docs/jcache#entryprocessor
But in any case, you should debug and profile your execution first. Is
everything working as expected? What is taking time? Etc.
-Val
--
View this mess
IGFS cache can't and should not be accessed directly. Use FileSystem API for
this.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/IGFS-Question-tp13447p13536.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Please attach full logs.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Failed-to-wait-for-initial-partition-map-exchange-tp6252p13487.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
In 1.9 you can use read-only processor to avoid locking:
https://issues.apache.org/jira/browse/IGNITE-4932
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Blocked-get-operation-problem-tp9133p13441.html
Sent from the Apache Ignite Users mailing list archive
Hi Ryan,
I will take a look this week.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Concurrent-job-execution-and-FifoQueueCollisionSpi-parallelJobsNumber-1-tp8697p13440.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Vladimir,
As I told before, this message is very generic and can be caused by multiple
reasons (sometimes it's not even an issue BTW - it's warning, not an error).
First things to check is memory consumption, GC and network.
-Val
--
View this message in context:
http://apache-ignite-users.705
You need to provide correct value class when executing a query, in your case
it should be ArrayList. The "ArrayList.class" that you provided
there doesn't make any sense.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-cache-range-query-using-cache-k
Basically, swap space is another storage layer. You have on-heap, off-heap
and then swap. So in case of on-heap mode only entry will be written in swap
when it's evicted from cache due to eviction policy. With off-heap enabled
it will be written to swap when it's evicted from there due to off-heap
Hi David,
You can use TcpDiscoverySpi#joinTimeout for this.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/How-to-detect-if-Ignite-server-nodes-are-connectable-tp12992p13000.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Generally, you can't add new node while holding a lock. If you're holding
locks for long period of time, I would recommend you to revisit the
architecture. In any case, make sure that you properly release all the
locks. Also I think you should to upgrade to the latest version, I believe
there were
401 - 500 of 2301 matches
Mail list logo