Hi,
How many nodes do you have? Can you check the same scenario with one node
only? How do you run queries? Is client on the same machine as a server
node?
I would recommend enabling DEBUG logs for org.apache.ignite.cache.hibernate
package. DEBUG logs can show all get and put operations for
Hi,
A table has two varchar columns, one column created with specific column length
and other created without any specific length as shown below:
CREATE TABLE person (id LONG PRIMARY KEY, name VARCHAR(64), last_name VARCHAR)
Can we create index on varchar columns without any specific length? In
Yeah the key thing is to be able to be notified when all records have been
updated in the cache.
We've tried using IgniteLock or this too by the way (e.g. the writer locks,
writes the records, unlocks).
Then the client app, internally queues all updates as they arrive from the
continuous query.
Hello!
It may handle your use case (doing something when all records are in cache).
But it will not fix the tool that you're using for it (continuous query
with expectation of batched handling).
Regards,
--
Ilya Kasnacheev
пт, 6 нояб. 2020 г. в 16:41, ssansoy :
> Ah ok so this wouldn't help
Hi,
*1) What load profile do you have? *
Ans: We have 2 clusters, each having 2 nodes, one cluster is having approx
15 GB data (Replication) & second cluster is having approx 5 GB data
(Partitioned) with eviction policy.
*2) Do you use SQL queries?*
Ans: Yes, We are using.
*3) Is it possible to
Manesh,
>> When running a large SELECT from a thick client node, could data be
>> fetched from the backup instead of primary partitions?
readFromBackup=true affects only cache operations, it doesn't work with SQL
queries.
>> in a two server system, if readFromBackup = False for a cache, and if
Ah ok so this wouldn't help solve our problem?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
No, it does not mean anything about the continuous query listener.
But it means that once a data streamer is flushed, all data is available in
caches.
Regards,
--
Ilya Kasnacheev
вт, 3 нояб. 2020 г. в 16:28, ssansoy :
> Thanks,
> How is this different to multiple puts inside a
1. Reads mostly go to the primary but yes, in some circumstances it’ll read
from the backup with that configuration set to true
2. No. It’ll “rebalance,” which means backup partitions would be promoted to
primaries. Your client would still get a response
3. Yes — though in practice the window
In general it should be ok to use connection pooling with Ignite. Is your
network ok? It look like a connection is being closed because of network
issues.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
What load profile do you have? Do you use SQL queries? Is it possible to
share your client node configuration?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Ashish,
Yes, it works that way because Ignite launches Jetty server under the hood
to handle HTTP requests.
Could you please clarify what concerns you exactly? In general a number of
threads doesn't indicate anything "bad" or "good".
--
Sent from:
Hello, Asish!
Try to clean your BeanConfig class. Write this class like (in the client
and in the server app):
import org.springframework.context.annotation.Configuration;
import org.springframework.context.annotation.ImportResource;
@Configuration
Dennis
"The WAL archive is used to store WAL segments that may be needed to recover
the node after a crash. The number of segments kept in the archive is such that
the total size of all segments does not exceed the specified size of the WAL
archive"
Given the above in documentation, if we
14 matches
Mail list logo
