Hello.
I have cache with query entity. Now I want to add new field to query
entity of existing cache. I take query entity from existing cache and
query entity with new fields, search new field and add it with DLL
'ALTER TABLE'. And now I have problem because query entity from cache
configuration
I found solution. Query "select column_name, data_type from
information_schema.columns where table_schema = ? and table_name = ?" in
local mode.
On 08/16/2018 06:28 PM, Dmitry Lazurkin wrote:
> Hello.
>
> I have cache with query entity. Now I want to add new field to query
&
Hi, Andrei. Thank you for reply.
I have found that problem is in unmarshalling:
2018-11-12 13:18:24.375 INFO 10 --- [-sock-reader-#3]
o.a.i.spi.discovery.tcp.TcpDiscoverySpi : 1
2018-11-12 13:18:24.375 DEBUG 10 --- [o-msg-worker-#4]
o.a.i.spi.discovery.tcp.TcpDiscoverySpi : Received metrics
2
2018-11-12 14:10:56.262 ERROR 10 --- [-sock-reader-#3]
o.a.ignite.marshaller.jdk.JdkMarshaller : Unmarshall 3:
TcpDiscoveryNodeAddedMessage [node=TcpDiscoveryNode [id=06960cfd-17
Does class loader load many classes on initial connect?
On 11/12/18 16:28, Dmitry Lazurkin wrote:
> Hi, Andrei. Th
I've found. TcpDiscoveryNode try to resolve sockAddrs in readExternal
method from hostNames (first) and addrs (second). TcpDiscoverySpi fills
hostNames for node with local hostnames. And of course new client node
can resolve only local hostname. In my case resolution of other node's
hostnames
take 10 seconds for each hostname.
On 11/12/18 17:28, Dmitry Lazurkin wrote:
> After reconnect unmarshalling of TcpDiscoveryNodeAddedMessage takes 20
> seconds:
> 2018-11-12 14:10:36.105 ERROR 10 --- [-sock-reader-#3]
> o.a.ignite.marshaller.jdk.JdkMarshaller : Unmarshall 1
> 2018-11-
Hello.
I need some advice. I have 1 client and 1 server. Ignite client
connection to server take ~1 minute. And I don't understand why.
In server log I see next entry:
2018-11-09 16:34:16,471 [tcp-disco-client-message-worker-#16] DEBUG
o.a.i.s.d.tcp.TcpDiscoverySpi - Redirecting message to
Hello.
On 17.11.2018 13:25, siva wrote:
> Quetions:
> ===
> 1.How to get the existing table columnNames ?
>
> i am trying to use this query but its throwing exception
>
> *select COLUMN_NAME from INFORMATION_SCHEMA.COLUMNS where
> TABLE_NAME='Person'*
You need query with setLocal(true). I
I think I can comment this lines in
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtLocalPartition:
if (grp.walEnabled())
ctx.wal().log(new
PartitionMetaStateRecord(grp.groupId(), id, state(), updateCounter()));
PS.
Issue with patch: https://issues.apache.org/jira/browse/IGNITE-10513
On 12/3/18 17:43, Dmitry Lazurkin wrote:
> OK. I have found steps to reproduce.
>
> For reproducing we need Ignite with slow disk. Or I known how to
> emulate slow hard disk:
>
> Add t
java:1846)
>
> at
>
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1757)
>
>
>
> Which version do you use?
>
> Is this reproducible? Every time?
>
>
>
> Thanks,
>
> Stan
>
>
>
>
>
&g
.java:1757)
>
>
>
> Which version do you use?
>
> Is this reproducible? Every time?
>
>
>
> Thanks,
>
> Stan
>
>
>
>
>
> *From: *Dmitry Lazurkin <mailto:dila...@gmail.com>
> *Sent: *20 ноября 2018 г. 15:44
> *To: *user@ignite.apache.
> Which version do you use?
>
> Is this reproducible? Every time?
>
>
>
> Thanks,
>
> Stan
>
>
>
>
>
> *From: *Dmitry Lazurkin <mailto:dila...@gmail.com>
> *Sent: *20 ноября 2018 г. 15:44
> *To: *user@ignite.apache.org <mailto:user@ignite.apache.org&
Try to print putted object with new field from java code. Column in
QueryEntity is just link to binary object field. So you may be have
different names for binary field and column.
PS. I use ignite 2.6 and don't have problems with new fields/columns.
On 11/22/18 05:26, kcheng.mvp wrote:
> Thank
Hello.
Ignite client stops connecting to server after exception:
2018-11-19 16:00:49,257 [tcp-client-disco-reconnector-#5] DEBUG
o.a.i.s.d.tcp.TcpDiscoverySpi - Resolved addresses from IP finder:
[/10.48.14.1:47500]
2018-11-19 16:00:49,257 [tcp-client-disco-reconnector-#5] DEBUG
Hello.
Partitions on Ignite cluster stuck forever in MOVING state after
restart. Cluster version is 2.7.0#20181130-sha1:256ae401. I don't see
any errors in logs about moving partitions and and I don't understand
why Ignite try to move partitions. May be I can enable some additional
logs for
Some java code that helps me on node startup:
// Call for each partition in parallel
private void preloadPartition(int partition) {
IgniteCache cache = ignite
.cache("test_cache")
.withKeepBinary();
ScanQuery query = new
ScanQuery<>(partition, (k,
Hello.
I would like to run task on all nodes with specified cache or all
partitions of specified cache and throw exception if some node is
offline. I use this code:
private ClusterGroup getCacheClusterGroup() {
Set baselineConsitentIds = ignite
.cluster()
.currentBaselineTopology()
.stream()
Hello,
I have 3 nodes with backups=1 and partitionLostPolicy=READ_WRITE_SAFE.
Node-2 and node-3 own partition 2. I shutdown node-2 and node-3. After
that cluster has partition 2 in state=LOST.
Now I should call resetLostPartitions for restore state of partition 2.
For now I see only one way for
wrote:
> Hello!
>
> Have you tried to start this on Nightly Build? Can you try that?
>
> If it still would not work, can you share your DB+wal files?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> вт, 5 мар. 2019 г. в 20:37, Dmitry Lazurkin <mailto:dila...@gmail.com&g
Ignite version: 2.7.0#20181130-sha1:256ae401
Hello.
I have exception on node startup:
java.lang.IllegalMonitorStateException: Attempted to release write lock
while not holding it [lock=7fa721ec8610, state=0001
at
org.apache.ignite.internal.util.OffheapReadWriteLock.writeUnlock(OffheapReadWriteLock.java:266)
at
Thank you, this is https://issues.apache.org/jira/browse/IGNITE-9303
On 3/6/19 7:11 PM, Dmitry Lazurkin wrote:
> Thank you for reply, Ilya.
>
>> Have you tried to start this on Nightly Build? Can you try that?
>
> No, on 2.7.0#20181130-sha1:256ae401. I will try Nightly Build
Hello,
I known I can preload ordinary partitions with
IgniteCache#localPreloadPartition. But I haven't seen any possibility
for preloading indexes to memory. Now I run sql query for each indexes
to force preloading.
But I saw in wiki documentation that indexes belong to partition with
special
Alexandr, thank you. I'll be in the loop.
On 10.09.2020 17:36, Alexandr Shapkin wrote:
> Hi,
>
> Looks like this is the part of the upcoming warmup feature [1] that should
> be published with the next Ignite release (2.10) or the upcoming GridGain
> edition (v8.7.26?) [2].
>
> Please, check the
This leads to problem with indexes.
On 30.09.2020 14:38, Ilya Kasnacheev wrote:
> Hello!
>
> Why would you want to do this?
>
> Try removing part-NNN.bin from your persistence to achieve this. Be
> sure to check in on testing first.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 30 сент. 2020 г.
May be: ScanQuery with partition number and cache.localClearAll for keys.
On 01.10.2020 11:47, Vladimir Pligin wrote:
> To be honest it doesn't look trivial.
> I'm not sure at the moment why one could need that.
> Could you please describe your use-case?
> It will definitely help us to design a
Hello,
I try to define compound index with some field and _key:
create index idx_desc on mytable (somecolumn asc, _key desc);
create index idx_asc on mytable (somecolumn asc, _key asc);
Error: Column doesn't exist: _KEY (state=42000,code=3008)
Is this bug? Because I see _key column in sqlline
Hello, folks.
I have big cache with configured rebalanceMode = ASYNC, rebalanceDelay =
10_000ms. Persistence is enabled, maxWalArchiveSize = 10GB. And I passed
-DIGNITE_PREFER_WAL_REBALANCE=true and
-DIGNITE_PDS_WAL_REBALANCE_THRESHOLD=1 to Ignite. So node should use
historical rebalance if
ill have to recreate.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> сб, 10 апр. 2021 г. в 19:22, Dmitry Lazurkin <mailto:dila...@gmail.com>>:
>
> Hello, folks.
>
> I have big cache with configured rebalanceMode = ASYNC,
> rebalanceDelay =
>
30 matches
Mail list logo
