Thank you so much.
then, if im not going to be use 11211 port.
what should i do. I do not want to binding 11211 port. is there any way?? or it
will be just automatically binding??
나의 iPhone에서 보냄
> 2020. 5. 18. 오후 10:27, Ilya Kasnacheev 작성:
>
>
> Hello!
>
> I have to correct, 11211 is not
Igniters,
Some time ago, we united with Igor to produce a webinar about Ignite SQL
essentials:
https://bit.ly/2WzlCrp
Beginners will get a full understanding of our SQL capabilities while
experienced Ignite developers will learn more about memory management
internals in relation to SQL, will get
I wanted to see if there are any plans to support near caches for thin
clients? I think it would be a great feature. I know I could use it right
now.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
It seems the issue exist only if one uses data streamer with binaryobject
builder. If I use straight JDBC to insert data, the issue goes away. Any
idea what one needs to do to get this working with binary objects?
Everything else is the same between the two scenarios.
On Mon, May 18, 2020 at 4:39
It turned out that I'd get partial results in some cases, when joining
partitioned caches. But I still don't understand why I am not getting all
the rows that the joined query should return.
My assumption is that if you have caches with primary keys, containing the
affinity key, then the related
Hi,
To explicitly deploy classes copy them to the libs dir. (located in
$IGNITE_HOME\libs)
Ignite takes the jars from the libs dir and puts them into the classpath.
Your classes need to be in the classpath.
Use jinfo or Visual VM to look at the classpath of the running java
ignite
Hi,
A node has to join the cluster to receive/register for messages/events.
You can store events:
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/eventstorage/memory/MemoryEventStorageSpi.html
On every node join, replay the events stored.
see:
Hi
Can anyone help me by providing inputs to the questions posted in my
previous message.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Thanks for the inputs.It is really helpful.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi
Can any let me know whether should i deploy my Ignite Project developed in
UNIX in each and every node.If Yes, then should it be deployed on the bin
folder shipped with ignite or can it be kept in any folder.
Currently we are following steps
1. We created a bean file which has all the
No error. Just no records is returned, as opposed to the join between the
replicated and partitioned cache which returns ass applicable rows. Sorry,
for not being clear.
On Mon, May 18, 2020 at 9:00 AM Ilya Kasnacheev
wrote:
> Hello!
>
> Fails how? Is the result set incorrect? Any specific
Hi Ignite experts,
I am facing an issue where some messages sent to a node are sometimes missed
when the node just joins the cluster.
On some debugging, I found that this is because as soon as the node joins
the cluster, the sender node receives a NODE_JOINED event for that receiver
node and it
Hello!
Binarylizable may be shorter but BinaryObject supports evolvable objects,
as in, you can add new fields, and cache operations will usually preserve
these.
You will only lose these when you de-serialize your object to old version
of POJO, but most of internal operations (such as
Hello!
In both cases Ignite will walk through the segments it needs, and adjust
persistence for any data that was updated in already completed operations.
Archive or no archive is a logistical choice, as far as my understanding
goes.
Regards,
--
Ilya Kasnacheev
вт, 12 мая 2020 г. в 07:28,
I would like to break down this question into two questions.
1. Can we have key-values with different expire times in the same cache? (I
think the answer for this is yes, because the redis layer in ignite allows
for this)
2. I am trying to build a ruby thin client for Apache Ignite and got a
Hello!
Yes, as it was mentioned on the list, it is not going to replace already
existing keys' values.
Regards,
--
Ilya Kasnacheev
ср, 13 мая 2020 г. в 08:01, Akash Shinde :
> Hi,
> My question is specifically for clo.apply(key, data) that I invoked in
> CacheStoreAdapter.loadCache
>
Hello!
These are for some Ignite internal caches. They have sensible small default
value, you do not need to tune them.
Regards,
--
Ilya Kasnacheev
чт, 14 мая 2020 г. в 10:59, kay :
> Hello again :)
>
> I read memory configuration section.
>
>
Hello!
Fails how? Is the result set incorrect? Any specific error message? Please
share details.
Regards,
--
Ilya Kasnacheev
пн, 18 мая 2020 г. в 16:49, narges saleh :
> Hi All,
> I have encountered a puzzling join case.
> I have 3 tables on a cluster of two ignite server nodes:
> table-A
Hello.Thanks for u reply.
Please see this JIRA ticket:
https://issues.apache.org/jira/browse/IGNITE-13020
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
Direct IO module is experimental and should not be used unless performance
is tested first, in your specific use case.
Regards,
--
Ilya Kasnacheev
пн, 18 мая 2020 г. в 16:47, 38797715 <38797...@qq.com>:
> Hi,
>
> If direct IO is disabled, the startup speed will be doubled, including
>
Hello!
I actually think that you should be conservative with that setting, since
large inline size will make your B+-tree taller which may lead to worse
performance.
Setting it to some good default would make sense. It depends on structure
and selectivity of your primary keys.
Regards,
--
Ilya
Hi Ilya,
Then I think this property should be ready in the production planning stage.
So the problem is, if there are many tables in the system and many
tables have combined primary keys, should this attribute be configured
with a relatively large value at the beginning, such as 40 and 50?
Hi All,
I have encountered a puzzling join case.
I have 3 tables on a cluster of two ignite server nodes:
table-A (id + org = primary), replicated
id
org. <-- affinity
other fields
table-B (id, org, add-id=primary key), partitioned
id
org <- affinity
addr-id
other fields
table-C (id, org,
Hi,
If direct IO is disabled, the startup speed will be doubled, including
some other tests. I find that direct IO has a great impact on the read
performance.
在 2020/5/14 上午5:16, Evgenii Zhuravlev 写道:
Can you share full logs from all nodes?
вт, 12 мая 2020 г. в 18:24, 38797715
Hello!
Please write to user-unsubscr...@ignite.apache.org, etc, to unsubscribe
from lists.
Regards,
--
Vivian Huertaz
On Mon, May 18, 2020, 7:14 AM Ilya Kasnacheev
wrote:
> Hello!
>
> Please write to user-unsubscr...@ignite.apache.org, etc, to unsubscribe
> from lists.
>
> Regards,
> --
>
Hello!
I think this is correct. Moreover, setting this property on a part of
cluster may lead to problems of its own. It is recommended to set ot before
deploying a cluster.
Regards,
--
Ilya Kasnacheev
пн, 18 мая 2020 г. в 16:40, 18624049226 <18624049...@163.com>:
> Hi Ilya,
>
> Thank you
Hi Ilya,
Thank you very much for your reply!
I wonder if the existing primary key index will not be rebuilt after
this property is configured? Will only affect newly created tables in
the future?
在 2020/5/18 下午9:25, Ilya Kasnacheev 写道:
Hello!
Yes, it will have global impact on all indexes
Hello!
I have to correct, 11211 is not used by thick JDBC driver (Which is a
regular client node), instead it is used by control.sh tool mostly. And
some other legacy tools.
Regards,
--
Ilya Kasnacheev
ср, 13 мая 2020 г. в 17:44, Evgenii Zhuravlev :
> Hi,
>
> Ports are described here:
>
Hello!
Yes, it will have global impact on all indexes on primary keys, and all
indexes created without INLINE SIZE clause.
Regards,
--
Ilya Kasnacheev
чт, 14 мая 2020 г. в 16:53, 38797715 <38797...@qq.com>:
> Hi,
>
> I see this property.
> If this property is configured, it has a global
Hello!
Before put() is completed, Binary Object Schema is not created/updated and
so the type names are not reflected here.
Unfortunately, if you need to read all fields of binary objects, you may
need to use internal APIs (which may not work as expected or change between
releases),
such as, in
Hello!
Remote filter is code. It can execute arbitrary logic. It can adjust to
what it needs to filter, change its own behavior with time.
Regards,
--
Ilya Kasnacheev
пн, 18 мая 2020 г. в 15:40, zork :
> Hi Ilya,
> Thanks for your response.
> I'm aware of remote filters but can these filters
Hello!
I think it is somewhat slower, but not by much, and it certainly does not
wipe all the benefits of using Data Streamer. It's OK to use.
Regards,
--
Ilya Kasnacheev
пн, 18 мая 2020 г. в 01:36, narges saleh :
> Hi All,
>
> I am going to get updates for the existing records in the cache,
Hello!
Please write to user-unsubscr...@ignite.apache.org, etc, to unsubscribe
from lists.
Regards,
--
Ilya Kasnacheev
пн, 18 мая 2020 г. в 16:13, ANKIT SINGHAI :
>
>
> --
> Regards,
> Ankit Singhai
>
--
Regards,
Ankit Singhai
Hello!
I just wanted to add that you can't create tables in parallel. Table
creation is sequential since it involves a Partition Map Exchange, which is
a blocking operation.
It can become a bottleneck quickly.
Regards,
--
Ilya Kasnacheev
пт, 15 мая 2020 г. в 07:24, adipro :
> We created a
Hello!
I can see how such scenario can expose issues in Apache Ignite's SQL. Can
you please create a JIRA ticket with this code?
Regards,
--
Ilya Kasnacheev
сб, 16 мая 2020 г. в 12:51, yangjiajun <1371549...@qq.com>:
> Hello.Sorry for so late to reply.I have got a reproducer.
>
> Here is the
Hi Ilya,
Thanks for your response.
I'm aware of remote filters but can these filters be modified once the query
is already attached?
Because if not, then this would not solve my use case as the filter would
always give me updates on a fixed subset of keys, however in my case this
subset is varying
Got it. Thanks a lot. This is very useful
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
You can use Data Streamer with allowOverride flag set can do incremental
load with keys replacement. Load cache is tailored for initial loading only.
Of course, you will have to write your own code around Data Streamer.
Regards,
--
Ilya Kasnacheev
пт, 15 мая 2020 г. в 18:53, nithin91
Hello!
Continuous query has a notion of 'remote filter'. This is a piece of code
which is executed near data (on server nodes) to determine if the update
needs to be sent over network.
https://apacheignite.readme.io/docs/continuous-queries#remote-filter
If you define a proper remote filter,
Hello!
Why do you focus on "too many dirty pages" message? It is purely
informational.
If you wish to avoid that, you need to make sure that less than half of
checkpoint page buffer is ever filled with updates which are pending to the
written to disk, between scheduled checkpoints.
Ideally you
Hello!
I think this is because the other node (second server) cannot ping the
first node (server1) via communication (port 47100 is closed or connection
is blocked).
Please provide complete log from both nodes.
Regards,
--
Ilya Kasnacheev
вс, 17 мая 2020 г. в 21:13, Vasily Laktionov :
> Hi
Since there are several approaches on solving this, I’m continue with your
code, a couple of suggestions:
- Create streamer instance out of loop, and close it on finally, not within the
loop.
- stmr.autoflushfrequency(0) as you do it every 2000 elements…
- Don’t forget remaining data (< 2000)
Hi
Implemented the code as suggested by you. Please find the code related to
this. Please let me know is this
right way of implementing what you suggested.
Also can you please let me know the use of stmr.autoflushfrequency(2000)
method usage .If i pass higher number to this method,will that
Thanks for sharing this.Its really helpful
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
We’d need to see your code. As I noted previously, running a compute job does
not start a server node.
> On 18 May 2020, at 11:21, nithin91
> wrote:
>
> Hi
>
> W.r.t client mode i am clear, But what is the use of starting the compute
> job on server node as when i start the the job on
Hi
W.r.t client mode i am clear, But what is the use of starting the compute
job on server node as when i start the the job on server node following
things happen
It is creating a new server node every time and the node is getting
disconnected once the job is done. But the problem with this
Ignition.start() doesn’t start a compute job, it starts a new node (a server
node by default). If you want t create a client node, you can do that in the
configuration file or by adding "Ignition.setClientMode(true)” before you start
the node. Then you can run a compute job:
Yes, that’s the removeAll method! There’s another method signature, one that
accepts a parameter:
public void removeAll(Set keys) throws TransactionException;
There are a few ways to update multiple entries. You can always use the SQL
UPDATE commend, but the equivalent to removeAll() is
Hi!
This is the method you are looking for (also available in async mode):
/**
* {@inheritDoc}
* @throws TransactionException If operation within transaction is failed.
*/
@IgniteAsyncSupported
@Override public void removeAll(Set keys) throws
TransactionException;
The method mentioned in the API is cache.removeAll() which removes all the
elements is the cache but i want to remove certain entries from cache at
once like cache.removeAll(List of Keys). is there any such method or
efficient way to remove entries corresponding to List of Keys at once .
Hi
I have initially two nodes,
But when i am initiating the compute job(IgniteCompute compute =
ignite.compute()) from server i.e Ignite ignite=Ignition.star("Server.xml")
it is creating a new server node every time and the node is getting
disconnected once the job is done. But the problem with
Thanks.This information is very helpful.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
> To execute a compute job on server nodes, should i use the below command by
> starting as client node.Please correct me if i am wrong.
> IgniteCompute compute = ignite.compute(cluster.forRemotes());
That would start a compute job on a remote node, which could be another client!
If you just
54 matches
Mail list logo