I‘m only speculating but this looks very similar to the issue I had last week and reported to the group here.Caused by: org.h2.message.DbException: Hexadecimal string with odd number of characters: "5" [90003-197]Why does H2 think it’s hex String format? For me it turned
Hi Taras,
attached the extract from the local node log (which is a Ignite client)
and the remote node log (which is a Ignite server with persistance enabled).
What's really strange is that previous value "IDX_STAGE_308" seems to be
the root cause? This is a value in column UCID but it's not rela
Hi Taras,
OK, I’ll try to get this later today.
Thanks
Thomas.
On 29.07.22 at 12:49, Taras Ledkov wrote:
> Hi,
>
> Could you provide the original exception from the map node?
> It must be available at the log files of the map node.
>
One additional log I noticed on the server node for these SQL queries;
WARN QueryParser For join two partitioned tables join condition
should contain the equality operation of affinity keys. Left side:
JOBQUEUE; right side: JOBS
Is this a warning or can it cause the below exception?
Thanks
Hi,
I'm getting (unreliable until now) Exception when executing SQL query in
Ignite 2.13.
It seems to be connected to the parameter for column UCID. When
searching for "6bf1dfc9-311b-432f-9342-257400dcc59e" the below exception
happens on our production server:
Caused by: javax.cache.CacheExcept
Hi Igniters,
can you please comment or correct the scenario described below? I assume
zero-downtime and fault-tolerance against data loss on node crashes is a
key feature of Ignite but the procedure in failure scenarios is not
clear to me.
Thanks!
On 19.06.22 11:32, jay.et...@gmx.de wrote:
Hi,
Fixed it. It was indeed a wrongly configured IP address!
On 15.06.22 22:29, don.tequ...@gmx.de wrote:
Both server node and thin client are on the same computer, each
running in a separate Docker container with network „host“. CPU load
does not seem to be an issue and other server nodes on the s
Any reason why BinaryObjectVectorizer is a final class? It would be
convenient to be able to extend it for specific subclasses on
pre-defined features.
On 22.06.22 18:32, don.tequ...@gmx.de wrote:
Responding to my own question in case someone else has a similar
question: The solution is to use
Responding to my own question in case someone else has a similar
question: The solution is to use BinaryObjectVectorizer which gets
the labeled features from the binary object!
*Question:* Why is BinaryObjectVectorizer a final class? It would be
convenient to be able to extend it for specific sub
Both server node and thin client are on the same computer, each running in a separate Docker container with network „host“. CPU load does not seem to be an issue and other server nodes on the same computer and from other computers connect to the cluster just fine without
Hi,
I'm experiencing a connection issue when using Java ThinClient at the
customer site. It is using Ignite 2.13.
From time to time it happens that the ThinClient cannot connect at
startup and gets a "connection refused". After several tries it
connects, but frequently is "loses" connection agai
Hi,
I'm experimenting with a Ignite cluster with multiple server nodes and
multiple client nodes. My understanding is that with Ignite I can avoid
data loss of all persistent caches and can avoid downtime for all clients.
If the above assumption is correct, how do I manage the servers and
baseli
Hi Igniters,
I'm wondering if a SQL update statement must be different when used from
a ThinClient? It doesn't seem to have any effect for me, nor does it
output an error.
For the below code I get this output:
Row: [1, Foo, 2]
Row: [2, Bar, 4]
Row: [1, Foo, 3]
Row: [2, Bar, 5]
Row: [1, Foo,
Hi Maxim,
OK, that’s alright. Thanks for your comment.
I agree the log message should be improved. But also, if it‘s actually not
intended that sock.shutdownInput() is skipped, then the function should
probably also split into two try blocks.
Thanks!
On 16.02.22 at 12:13, Maxim Muzafarov wr
Instead of creating a cache with lock objects wouldnБ─≥t it be easier to use a semaphore for each cache where you want to achieve strong reader-Writer consistency?https://ignite.apache.org/docs/latest/data-structures/semaphoreThen every time before reading/writing you ac
Wow, that seems to do the trick. When forcing the index use on the column that I order by the query returns within milliseconds instead of >40 seconds!I‘ll do more tests but so far it looks like you are right, this helps significantly:USE INDEX(my_index_on_order_by_column
The QUEUED field is a BIGINT that contains timestamp from System.currentTimeMillis(), so it should be pretty easy to sort, shouldn’t it? Looks like the field STATUS (used in where clause) and field QUEUED (used in order clause) are not working optimal when used together.
Yes it works well indeed! Thanks!On 05.04.21 at 12:56, Ilya Kasnacheev wrote:
From: "Ilya Kasnacheev" Date: 5. April 2021To: user@ignite.apache.orgCc: Subject: Re: Correctly s
18 matches
Mail list logo
