+1
With regards,
Cos
On 2020-09-21 20:35, Nikita Ivanov wrote:
My vote is to just call ignite "IgniteDB". That's it. No other additional
explanation is required as no amount of additional verbiage will help.
Every DB is different: from MongoDB, to RedisDB, to CockroachDB, to Oracle
- they
Sergei Ryzhov created IGNITE-13473:
--
Summary: Snapshot tests for ducktape
Key: IGNITE-13473
URL: https://issues.apache.org/jira/browse/IGNITE-13473
Project: Ignite
Issue Type: Task
Ilya Kasnacheev created IGNITE-13474:
Summary: Client node consistentId uniqueness is not checked
Key: IGNITE-13474
URL: https://issues.apache.org/jira/browse/IGNITE-13474
Project: Ignite
Bot was down due to No space left on the device error.
It seems, that one of our cache entry (cache-teamcityFatBuild) eats most of the
disk space (193 of 200 Gb for all caches).
Is there a way to shrink it on disk (cache entries are being cleaned, but that
seems to not affect disk usage)?
>
Sergey,
Thank you for your answer. While I am not happy with the proposed
approach but things never were easy. Unfortunately I cannot suggest
100% better approaches so far. So, I should trust your vision.
2020-09-22 10:29 GMT+03:00, Sergey Chugunov :
> Ivan,
>
> Checkpointer in Maintenance Mode
Ivan,
Checkpointer in Maintenance Mode is started and allows normal operations as
it may be needed for defragmentation and possibly other cases.
Discovery is started with a special implementation of SPI that doesn't make
attempts to seek and/or connect to the rest of the cluster. From that
Nikolay, can you try again? Seems to work fine for me.
On Tue, Sep 22, 2020 at 9:57 AM Nikolay Izhikov wrote:
> Hello, Igniters.
>
> Currently, mtcga bot is down - 502 bad gateway error.
> Can someone help with it?
>
> https://mtcga.gridgain.com/prs.html
>
Hello, Igniters.
Currently, mtcga bot is down - 502 bad gateway error.
Can someone help with it?
https://mtcga.gridgain.com/prs.html
Ryabov Dmitrii created IGNITE-13472:
---
Summary: JDBC bulkload operations are processed with wrong
security context
Key: IGNITE-13472
URL: https://issues.apache.org/jira/browse/IGNITE-13472
Project:
Guys,
I've filled the ticket with reproducer [1] for the discovery bug. This bug
caused by [2] ticket. We discussed with Vladimir Steshin privately and
decided to revert this ticket. I will do it today (after TC bot visa) if
there are no objections.
[1]:
Pavel Tupitsyn created IGNITE-13471:
---
Summary: Execute user-defined compute jobs asynchronously when
CompletionStage is returned
Key: IGNITE-13471
URL: https://issues.apache.org/jira/browse/IGNITE-13471
Yes, this makes a lot of sense (and can be applied to Services, too).
I've filed the ticket: https://issues.apache.org/jira/browse/IGNITE-13471
This requires a separate IEP, of course.
On Mon, Sep 21, 2020 at 6:33 PM mnk wrote:
> Pavel Tupitsyn wrote
> >> result of a remote execution is a
Ilya Kasnacheev created IGNITE-13475:
Summary: NPE on IgniteTxHandler.finishDhtLocal
Key: IGNITE-13475
URL: https://issues.apache.org/jira/browse/IGNITE-13475
Project: Ignite
Issue Type:
Stanilovsky Evgeny created IGNITE-13476:
---
Summary: Calcite improvements. Implement ProjectionNode.
Key: IGNITE-13476
URL: https://issues.apache.org/jira/browse/IGNITE-13476
Project: Ignite
I cast my vote for the "table". This term is generic, well-understood and
naturally fits SQL-intensive use cases. Basically, we don't need to
reinvent the wheel and the "table" aligns with our internal storage
structure proposed for 3.0.
Vladimir Ozerov's thoughts down below this discussion
Ignite Developers,
As part of our sponsorship of ApacheCon, our company MuseDev is doing a Bug
Bash for select Apache projects. We'll bring members of the ApacheCon
community together to find and fix a range of security and performance bugs
during the conference, and gameify the experience with
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
Hi all,
There is the run.sh script that’s required for docker images deployment and
internally it just invokes the default ignite.sh script prior to starting a
node.
So far, so good, but we discovered that it doesn’t propagate system signals
to the JVM due to its internal logic and also
I believe that remote JMX access should NOT be enabled by default in any Ignite
distributions - neither docker nor regular binary package.
Enabling remote JMX requires caution. It is a powerful interface, and the fact
that ignite.sh enables it by default with no security (!) bothers me a lot.
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
23 matches
Mail list logo
