Manuel Núñez created IGNITE-13203:
-
Summary: Improve OptimizedObjectOutputStream serialisation
performance
Key: IGNITE-13203
URL: https://issues.apache.org/jira/browse/IGNITE-13203
Project: Ignite
Alexandr created IGNITE-13204:
-
Summary: Java Thin client Kubernetes discovery
Key: IGNITE-13204
URL: https://issues.apache.org/jira/browse/IGNITE-13204
Project: Ignite
Issue Type: New Feature
Anton, Nikolay,
Let's agree on what we are arguing about: whether it is about "like or
don't like" or about technical properties of suggested solutions.
If it is about likes and dislikes, then the whole discussion is
meaningless. However, I hope together we can analyse pros and cons
carefull
Hello, Maxim.
> 1. tiden can deploy artifacts by itself, while ducktape relies on
> dependencies being deployed by external scripts
Why do you think that maintaining deploy scripts coupled with the testing
framework is an advantage?
I thought we want to see and maintain deployment scripts separ
Max,
Thanks for joining us.
> 1. tiden can deploy artifacts by itself, while ducktape relies on
> dependencies being deployed by external scripts.
No. It is important to distinguish development, deploy, and orchestration.
All-in-one solutions have extremely limited usability.
As to Ducktests:
Dock
Vladimir Steshin created IGNITE-13205:
-
Summary: Represent in logs, javadoc affection of several node
addresses on failure detection.
Key: IGNITE-13205
URL: https://issues.apache.org/jira/browse/IGNITE-13205
Igniters.
All who are interested in integration testing framework discussion are welcome
into slack channel -
https://join.slack.com/share/zt-fk2ovehf-TcomEAwiXaPzLyNKZbmfzw?cdn_fallback=2
> 2 июля 2020 г., в 13:06, Anton Vinogradov написал(а):
>
> Max,
> Thanks for joining us.
>
> > 1. ti
Vladimir Steshin created IGNITE-13206:
-
Summary: Represent in the doc affection of several node addresses
on failure detection.
Key: IGNITE-13206
URL: https://issues.apache.org/jira/browse/IGNITE-13206
Hello!
Ivan, you really really need to move these two dots as a first argument in
your example, instead of a last one, or people will going to hit this issue
every time they try CMake.
Regards,
--
Ilya Kasnacheev
ср, 1 июл. 2020 г. в 06:18, Ivan Daschinsky :
> Pavel, pay attention to two dots
Anton Kalashnikov created IGNITE-13207:
--
Summary: Checkpointer code refactoring: Splitting
GridCacheDatabaseSharedManager ant Checkpointer
Key: IGNITE-13207
URL: https://issues.apache.org/jira/browse/IGNITE-1
Folks,
Please share the summary of that Slack conversation here for records once
you find common ground.
-
Denis
On Thu, Jul 2, 2020 at 3:22 AM Nikolay Izhikov wrote:
> Igniters.
>
> All who are interested in integration testing framework discussion are
> welcome into slack channel -
> https:
Vladimir Steshin created IGNITE-13208:
-
Summary: Refactoring of IgniteSpiOperationTimeoutHelper
Key: IGNITE-13208
URL: https://issues.apache.org/jira/browse/IGNITE-13208
Project: Ignite
I
Kirill,
I've looked through the patch.
Looks good, but it feels like the first thing someone will try to do given
bytesRcvd and duration is to divide one by another to get an average speed.
Do you think it's reasonable to also add it to the logs? Maybe even to the
metrics?
Also, this works with
Valentin Kulichenko created IGNITE-13209:
Summary: JavaIgniteCatalogExample doesn't work with a standalone
Spark cluster
Key: IGNITE-13209
URL: https://issues.apache.org/jira/browse/IGNITE-13209
If multiple indexes are to be built "number of indexed keys" metric may be
misleading.
As a cluster admin, I'd like to know:
- Are all indexes ready on a node?
- How many indexes are to be built?
- How much resources are used by the index building (how many threads are used)?
- Which index(es?) i
LongMetric startTime = mreg.findMetric("RebalancingStartTime");
LongMetric lastCancelledTime =
mreg.findMetric("RebalancingLastCancelledTime");
LongMetric endTime = mreg.findMetric("RebalancingEndTime");
LongMetric partitionsLeft = mreg.findMetric();
LongMet
16 matches
Mail list logo
