Hello,
I am facing "org.apache.ignite.binary.BinaryObjectException: Method
"rawReader" can be called only once." when tried to use raw mode.
I have a super class and few extending classes, both are implementing
Binarylizable. In readBinary method of extending class calling
"super.readBinary(binar
Ibrahim,
I've checked with our community members (copied) and it doesn't look like a
known issue. Sergey, what details do we need to reproduce the behavior?
-
Denis
On Mon, Sep 30, 2019 at 4:24 AM ihalilaltun
wrote:
> Hi Denis,
>
> Our problem is not related to configuration parameters. We al
I'm attempting to create a table and I'm setting the cache name according to
the examples in the documentation.
CREATE TABLE IF NOT EXISTS batch_test (x varchar(10), y int, z float, PRIMARY
KEY (y)) WITH "CACHE_NAME=foo_1234_test_test";
I've run this query through sqlline and a C++ executable u
Tried to run the reproducer and got `Cache doesn't exist:
6e7b08b5-3bfd-4026-b322-c4a34ffkafd7_Forms` exception.
On Tue, Oct 1, 2019 at 3:16 PM siva wrote:
> Hi Pavel,
>
>
> *Maybe something else is affecting request time in staging?*
> chances of others services trying to connect (from front en
Thanks for your reply. Can you answer the 2nd part of the question?
1) UtilityCachePoolSize do and do I care about it if I am a client?
2) ManagementPoolSize do and do I care about it if I am a client?
3) QueryTheadPool (documented) but do I need it on a client?
Would be helpful if these could b
Hi,
The root cause of the performance looks like in the change the default
count of atomic backups [1] on the 2.4 and later.
Please try to use IgniteAtomicSequence instead of the IgniteAtomicLong
to generate IDs.
[1]. org.apache.ignite.configuration.AtomicConfiguration#DFLT_BACKUPS
18.09.201
Hi,
Yeah, it seems to be that bug.
As far as can see it's resolved and marked to be released as a part of 2.8.
I haven't managed to find that commit in other branches unfortunately.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
It’s being discussed in the developer list right now. January seems to be the
current target.
Regards,
Stephen
> On 2 Oct 2019, at 10:41, Marco Bernagozzi wrote:
>
> Cool, thanks!
> Any idea when 2.8 is planned to be released?
>
> Regards,
> Marco
>
> On Wed, 2 Oct 2019 at 11:31, Stephen Dar
Cool, thanks!
Any idea when 2.8 is planned to be released?
Regards,
Marco
On Wed, 2 Oct 2019 at 11:31, Stephen Darlington <
stephen.darling...@gridgain.com> wrote:
> Looks like it missed being part of the 2.7.x release by a month or two. It
> will be resolved when 2.8.0 comes out.
>
> Regards,
>
Hi!
We have some problem with service grid.
Configuration
- Data nodes (group of nodes)-2 PCs (CPU-8/mem-32).
- Service nodes (group of nodes) -3 PCs (CPU-8/mem-32).
Data node configuration:
IgniteConfiguration cfg = new IgniteConfiguration configuration();
final UUID uuid = UUID.ra
Looks like it missed being part of the 2.7.x release by a month or two. It will
be resolved when 2.8.0 comes out.
Regards,
Stephen
> On 2 Oct 2019, at 09:59, Marco Bernagozzi wrote:
>
> I'm getting this error when the nodes are shutting down.
> What are the possible causes for this?
> A bug wa
Thank you for the feedback!
Kurt
From: Andrei Aleksandrov
Sent: Wednesday, October 2, 2019 11:27 AM
To: user@ignite.apache.org
Subject: Re: Authorizing thin clients
External Email: Use caution in opening links or attachments.
Hi Kurt,
Unfortunately from the box Ignite provide only simple usern
Hi Kurt,
Unfortunately from the box Ignite provide only simple username/password
authentication for thin clients.
You can read more about it here:
https://apacheignite.readme.io/docs/advanced-security
BR,
Andrei
10/1/2019 3:08 PM, Kurt Semba пишет:
Hi all,
is there a way to define which
This seems to be a new bug, and unrelated to IGNITE-10010.
Both the nodes were fully operational when the null pointer exception happened.
The logs show that and both the nodes crashed
Can you give some insights into this, possible scenarios this could have led
this?
Is there any potential workar
I'm getting this error when the nodes are shutting down.
What are the possible causes for this?
A bug was marked for this a year ago or so, but was marked as resolved, it
seems?
http://apache-ignite-issues.70530.x6.nabble.com/jira-Updated-IGNITE-9826-Ignite-node-with-TcpDiscoveryS3IpFinder-can-hang
15 matches
Mail list logo