Hello Alex, thanks for the tip but putting everything on the namespace ignite
does not help.
I also rechecked the documentation. I still get the 403.
Additional question : how does the service account and the service relate?
So I have a
1) service account
kubectl describe serviceaccount ignite
There is the question. It turns out that I need to collocate the table,
because the field COL will have different values?
But how can i do this?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Thank you!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
The org.apache.ignite.internal.processors.cache.query.CacheQuery interface
has a comment:
* {@code Group by} and {@code sort by} statements are applied
separately
* on each node, so result set will likely be incorrectly grouped or
sorted
* after results from multiple
Hi Ilya,
Yes, So filter gets created but not executed on more than one node. 'Entered
Remote Filter' happens only on one node. 'Filter created' log is printed in
the 'create()' method of the Factory.
'Entered Remote Filter' is printed in the evaluate method of the
CacheEntryEventFilter.
That
Hi - Yes, Ignite native persistence is enabled.
Thanx and Regards,
KR Kumar
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
I see that you've bound everything to the "default" namespace.
kubectl describe serviceaccount ignite
Name:ignite
Namespace: default
Make everything in the "ignite" namespace as described here:
https://apacheignite.readme.io/docs/rbac-authorization
Hello,
I am deploying an embeded version of ignite on AKS and I am getting this
error:
Caused by: java.io.IOException: Server returned HTTP response code: 403 for
URL:
https://kubernetes.default.svc.cluster.local:443/api/v1/namespaces/default/endpoints/processing-engine-pe-v1-ignite
at
Hello!
1. I guess it is a honest mistake.
2. The idea here is that you can't expect that GROUP BY COL will return
anything relevant, if the table is not collocated by COL.
Regards,
--
Ilya Kasnacheev
пт, 10 июл. 2020 г. в 17:34, Surkov.Aleksandr :
> The
Hi,
I think it is not a priority issue, because in general it is right.
EVT_CACHE_REBALANCE_STOPPED event is received when all data loaded to a node,
but switch of affinity happens after all cache will be rebalanced.
At first, why do you need to know, when affinity change after rebalance? In my
Hello!
I see the following lines on all 3 nodes:
2020-07-09 16:41:02,957 [disco-notifier-worker-#101] DEBUG
com.COMPANYNAME.prophet.configstore.common.remote.ConfigStoreTableRemoteFilterFactory
[] - projectname LISTENS: Filter creation started with
Hello!
It seems that communication connections were closed after CG pause, then
you have got half-open connections. It is recommended to keep
socketWriteTimeout and failure detection timeout in relative sync.
Default socketWriteTimeout on TcpConnectionSpi is very low while your
failure detection
HI Ilya,
Please find the attached logs.
You will notice that this log is only on server 1 - "projectname LISTENS:
Entered Remote Filter ."
You can also see that the filter has been created on all the three nodes. (
LOG : projectname LISTENS: Filter created )
server1RemoteFilterExecuted.txt
Hello!
I guess that Apache Ignite 2.9 will have snapshotting capabilities.
Traditionally we rely more on backup nodes/partitions than on off-line
backups.
Regards,
--
Ilya Kasnacheev
ср, 8 июл. 2020 г. в 12:23, marble.zh...@coinflex.com <
marble.zh...@coinflex.com>:
> Hi, any suggestions?
>
Hello!
It seems that the node fell behind in switching to new topology. Can you
provide full log of this node? I guess that something was blocking PME.
Regards,
--
Ilya Kasnacheev
чт, 9 июл. 2020 г. в 09:44, Mahesh Renduchintala <
mahesh.renduchint...@aline-consulting.com>:
> Hi,
>
> We
Hello!
Can you provide full thread dump (jstack) after you see these messages?
Regards,
--
Ilya Kasnacheev
ср, 8 июл. 2020 г. в 15:57, Kamlesh Joshi :
> Hi Stephen/Team,
>
>
>
> Did you got any chance to look into this?
>
>
>
> *Thanks and Regards,*
>
> *Kamlesh Joshi*
>
>
>
> *From:*
Hello!
Can you throw together a reproducer project which shows this behavior? I
would check.
Regards,
--
Ilya Kasnacheev
пт, 3 июл. 2020 г. в 13:14, ssansoy :
> Thanks - the issue I have now is how can I confirm that the local listen
> has
> returned before executing my code?
> e.g. in the
Hello!
Yes, there is Data Streamer Thread Pool Size on server, which corresponds
to perNodeParallelOperations.
Server will not run more parallel operations than thread pool size.
Regards,
--
Ilya Kasnacheev
вт, 7 июл. 2020 г. в 23:18, Edward Chen :
> Hello,
>
> In IgniteDataStreamer, there
Hello!
Can you provide an example of REST response? I don't understand how this
issue manifests.
Regards,
--
Ilya Kasnacheev
ср, 8 июл. 2020 г. в 01:25, Maxim Volkomorov <2201...@gmail.com>:
> I have "type":{"platformType":false}" in REST response for my
> enum object property.
>
> Object
Hello!
I don't think so. It is supposed to speed it up. Do you have persistence?
With persistence, you would expect a slow-down after an initial spike.
Regards,
--
Ilya Kasnacheev
пт, 10 июл. 2020 г. в 15:09, krkumar24061...@gmail.com <
krkumar24061...@gmail.com>:
> Hi Guys - If I have my
Hi Guys - If I have my data streamer's allowOverwrite is set to false which
is default, will this cause my read IOPS go up as it need to check if the
key already exist? Bcoz the behavior that we see is that the write
performance goes down significantly after it has inserted few billion rows
and
Hello!
I don't think there is any, if we are talking of off-heap size.
Any problems in case of node failure are shared by persistent clusters
which have more data than RAM.
Regards,
--
Ilya Kasnacheev
ср, 8 июл. 2020 г. в 18:01, Maxim Volkomorov <2201...@gmail.com>:
> Is there a RAM limit
Hello!
Maybe you have some firewall issue here, such as only one way connections
are possible but not the other way around.
We do not recommend geo-distributed clustering with Apache Ignite.
Regards,
--
Ilya Kasnacheev
вт, 7 июл. 2020 г. в 06:59, trans :
> Hi, can someone please suggest on
Hello!
As far as I know, there is no such way yet.
Regards,
--
Ilya Kasnacheev
чт, 9 июл. 2020 г. в 17:22, krkumar24061...@gmail.com <
krkumar24061...@gmail.com>:
> Hi Guys - I have a five node cluster and all the nodes are part of the
> baseline. Ignite native persistence is enabled. If one
Hello!
This is weird, I recommend checking logs for exceptions, maybe the filter
cannot run on two other server nodes.
Regards,
--
Ilya Kasnacheev
пт, 10 июл. 2020 г. в 10:25, VeenaMithare :
> Hello,
>
> We have a 3 server cluster . The Caches on this cluster are configured as
>
Hello,
We have a 3 server cluster . The Caches on this cluster are configured as
PARTITIONED, with 1 BACKUP.
We also have a client executing a simple continuous query awaiting updates
on record where NAME=AA.
1. When this record is updated, I see the remote filter being executed only
on one
26 matches
Mail list logo