Sorry for forget the attachments.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I encountered a problem when restarting ignite, a node seems to be unable to
process the request anymore, because its CacheStore did not process the
update operations of database. Here is the log it printed:
2018-12-12 07:06:27:556 [exchange-worker-#42] WARN
Sorry for forgetting the attachments.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I encountered a problem when restarting ignite, a node seems to be unable to
process the request anymore, because its CacheStore did not process the
update operations of database. Here is the log it printed:
2018-12-12 07:06:27:556 [exchange-worker-#42] WARN
Thanks for sharing the command.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Ilya,
The setup is a 3 VM nodes in openstack all connected through each other in
tenant network.
Following is the configuation used in all 3 ignite nodes to start the setup:
ignite-ycsb-all-same-network.xml
Hi,
We are going to upgrade our Ignite Distributed Clusters from version 2.1 to
version 2.5.3 .
Are there are guidelines on the best practices of upgrading the cluster with
minimal downtime / data loss?
Is the standard practice to shut down the entire cluster, upgrade and
restart?
Thanks,
Anand
I am interested to use Ignite to speedup Spark as in
https://apacheignite-fs.readme.io/docs/ignite-for-spark, but all the example
seems to be in Java/Scala. Is there an easy way to do the same in Python? I
read somewhere that Ignite has an ODBC driver and perhaps a RESTful api as
an alternative.
Denis,
Is this a regression? Have we created a ticket to address it?
--
Denis
On Tue, Dec 11, 2018 at 4:13 AM Denis Mekhanikov
wrote:
> Andrey,
>
> Thanks for the info!
>
> Denis
>
> вт, 11 дек. 2018 г. в 14:02, Andrey Davydov :
>
>> Hello,
>>
>> When I update Ignite from 2.6 to 2.7, I have
Jose,
Rewind the recording to ~ 13 mins 30 secs, a speaker explains how to
configure high-availability across racks (aka. rack-awareness):
https://www.youtube.com/watch?v=u8BFLDfOdy8=1806s
The same concept can be applied for DCs. But check the cross-DC latency
first. If it's high then the
Discovery is a basic functionality, that is needed for clustering. You can
try to implement your own DiscoverySpi, which will do absolutely nothing,
but do you really want it?
вт, 11 дек. 2018 г. в 13:42, Skollur :
> is there anyway i can run ignite on machine and port without discovery?
>
>
>
>
is there anyway i can run ignite on machine and port without discovery?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Port 10800 is used by Ignite for thin clients by default, looks like it was
bound earlier on this machine. But why do you want to use 10800 for
discovery?
вт, 11 дек. 2018 г. в 13:09, Skollur :
> It is different machine. Wondering why not able to use same port? I have
> put
> the IP and port for
It is different machine. Wondering why not able to use same port? I have put
the IP and port for each node in different machine.
Machine 1: node
discovery.setLocalAddress("192.2.2.1");
discovery.setLocalPort(new Integer("10800")));
Machine 2: node
discovery.setLocalAddress("192.2.2.2");
There is also a portRange property, which is set to 100 by default. If the
first address is already occupied, then discovery will try to bind to the
next one.
вт, 11 дек. 2018 г. в 12:14, Skollur :
> I have following code in node1 ->
> TcpDiscoverySpi discovery = new TcpDiscoverySpi();
>
I have following code in node1 ->
TcpDiscoverySpi discovery = new TcpDiscoverySpi();
discovery.setLocalAddress("192.2.2.1");
discovery.setLocalPort(new Integer("10800")));
cfg.setDiscoverySpi(discovery);
and node 2 ->
TcpDiscoverySpi discovery = new
Thanks for the response, Denis.
I am afraid that I don't really understand how to leverage the feature you
indicated, purely from the Javadocs...
Can you provide a simple set of node-configs, that would illustrate and
accomplish what I am trying to achieve?
Thanks,
Jose
--
Sent from:
Thanks. I use sql in transaction context, but in 2.6 I havent problem this.
Now I changed mode to TRANSACTIONAL_SNAPSHOT and Transaction to pessimistic
repeatable and problem was gone.
About first problem.. I create small project to reproduce it.
Hi Andrey,
It looks like you try to run "Select" sql query inside explicit transaction.
Please, let us know if it is not true.
This was workable in 2.7 as SQL had no transactional support and query just
ignored transactional context (however "Select for Update" wasn't).
For now, SQL Select query
Hi Andrey,
It looks like your persisted data was read incorrectly by upgraded
Ignite. It would be great if you provide runnable reproducer.
Regarding Optimistic Serializable transactions. They are still
supported by caches with TRANSACTIONAL atomicity mode. In your error
it looks like that your
In case, when you have replicated cache and you connected with thin client
only to one of them, it decides that it can perform query on the one node
only, because all data can be found locally. You can try to connect a
different client to the different node and divide all queries into 2
clients.
Hello!
If you use 2.7 AND column values cannot fit into index, warning will be
printed which will show both current and expected inline size.
Regards,
--
Ilya Kasnacheev
вт, 11 дек. 2018 г. в 15:58, Denis Mekhanikov :
> Jose,
>
> There is no such metric currently.
> The only way to
Hello!
You could write this message to developers list in a separate thread, see
if there will be any discussion.
Regards,
--
Ilya Kasnacheev
ср, 5 дек. 2018 г. в 18:29, piotr.romanski :
> Hi all, I think that Krzysztof raised a valid concern. Actually, in my
> opinion the manual
Jose,
There is no such metric currently.
The only way to understand it now is to try loading data with and without
indices,
and compare results.
There is an enhancement proposal, that covers this functionality:
Hello!
All cache values are now always stored off-heap, on-heap is only used as
cache (on top of cache).
1. You should check if performance is good enough without on-heap caching.
2. You should have some constant amount of RAM for heap (4G is allright,
but it depends) and dedicate the rest of
Hello!
I believe if all fields' lengths are known (e.g. number columns) it is the
exact number of bytes required to store them.
If some of lenghts are unknown I believe it's 10 by default.
Not sure you can introspect it after index is created.
Regards,
--
Ilya Kasnacheev
сб, 8 дек. 2018 г. в
Hello!
Can you post a small reproducer project so that I can look without
reimplementing it for the second time?
Regards,
--
Ilya Kasnacheev
пн, 10 дек. 2018 г. в 21:10, Andrey Davydov :
> I’ve got strange exception after update my project from 2.6 to 2.7. It
> happens when I run DELETE SQL
I am explicitly set the --host and -- port 11211 parameters and it is work.
Thanks.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
We will need more details about your setup to be able to answer anything.
Regards,
--
Ilya Kasnacheev
вт, 11 дек. 2018 г. в 08:27, summasumma :
> Can anyone pls help me with this issue ?
>
> Thanks
> ...summa
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Andrey,
Thanks for the info!
Denis
вт, 11 дек. 2018 г. в 14:02, Andrey Davydov :
> Hello,
>
> When I update Ignite from 2.6 to 2.7, I have to update Spring to
> corresponding version too (from 4.16 to 4.18). And I got some exceptions on
> application stop (org.apache.ignite.internal.
>
Johe,
You can configure a corresponding backup filter for your cache affinity
function.
Use the following method to specify it in a cache config:
RendezvousAffinityFunction.html#setAffinityBackupFilter
Hello!
ALTER USER "ignite" WITH PASSWORD 'new_passwd'
Regards,
--
Ilya Kasnacheev
вт, 11 дек. 2018 г. в 14:14, radha :
> Thanks for you reply.
> I have enabled authentication.
> Let me put my understanding,
> superuser [deafult user created by ignite while deploying ignite] cannot be
>
Thanks for you reply.
I have enabled authentication.
Let me put my understanding,
superuser [deafult user created by ignite while deploying ignite] cannot be
changed before/after deploying ignite.
There is an option to change the superuser password using alter command
after deploying the
Hello,
When I update Ignite from 2.6 to 2.7, I have to update Spring to
corresponding version too (from 4.16 to 4.18). And I got some exceptions on
application stop (org.apache.ignite.internal.IgniteInterruptedCheckedExcept
ion on backplane scheduled queries).
As I find with debugger, in
Following the thread for same question!
Note: I had a similar question in the following thread for some inputs:
http://apache-ignite-users.70518.x6.nabble.com/Geo-redundancy-support-in-Ignite-tt25477.html
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Yuriy,
Do you see any exceptions in log of control.sh script or cluster nodes,
when you run the baseline command?
Try specifying --host and --port parameters explicitly.
Denis
вт, 11 дек. 2018 г. в 12:56, Yuriy :
> Hello.
>
> After updating from 2.6 to 2.7 control.sh --baseline can not
Hello.
After updating from 2.6 to 2.7 control.sh --baseline can not connect to the
cluster.
[root@ignat3 apache-ignite-2.7.0-bin]# sh bin/control.sh --baseline
Control utility [ver. 2.7.0#20181130-sha1:256ae401]
2018 Copyright(C) Apache Software Foundation
User: root
Upgraded, the problem is the same. jdk Same version ,JCache version 1.1
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
38 matches
Mail list logo
