Alright, it took me longer to get back and look into it. Sorry for a delay.
Overall, folks, the things look creepy, seriously. I see 3 primary issues
ranged by priority.
1st, until the failure handler gets smart enough how to deal with
SYSTEM_WORKER_BLOCKED/SYSTEM_CRITICAL_OPERATION_TIMEOUT
Igor Sapego created IGNITE-11748:
Summary: Node.js thin: auto-generated documentation stored in Git
Key: IGNITE-11748
URL: https://issues.apache.org/jira/browse/IGNITE-11748
Project: Ignite
Anton,
I'm trying tell you that this proxy can produce false positive result,
incorrect result and just hide bugs. What will the next solution?
withNoBugs proxy?
You can perform consistency check using idle verify utility. Recovery
tool is good idea but user should trigger this process, not some
Ivan Rakov created IGNITE-11747:
---
Summary: Document --tx control script commands
Key: IGNITE-11747
URL: https://issues.apache.org/jira/browse/IGNITE-11747
Project: Ignite
Issue Type: Task
Hi Igniters,
Unfortunately, Ignite C++ examples cannot build without
https://issues.apache.org/jira/browse/IGNITE-11195
So this issue should be included in the scope.
Sincerely,
Dmitriy Pavlov
пт, 12 апр. 2019 г. в 13:53, Dmitriy Pavlov :
> Hi Igniters,
>
> A bit of update: Last change fixing
Sergei Ryzhov created IGNITE-11746:
--
Summary: It is necessary to work out the ability to read basic
parameters from environment variables so that administrators would not have to
enter them every time
Key: IGNITE-11746
Ilya Kasnacheev created IGNITE-11745:
Summary: Rebalancing overwhelmingly prefers some supplier nodes to
others
Key: IGNITE-11745
URL: https://issues.apache.org/jira/browse/IGNITE-11745
Project:
Seems, we already fixed all bugs caused this feature, but there is no
warranty we will not create new :)
This proxy is just checker that consistency is ok.
>> reaching bugless implementation
Not sure it's possible. Once you have software it contains bugs.
This proxy will tell you whether these
Method name is minor problem. I still believe that there is no need
for this proxy because there are no any guarantees about bugless
implementation this functionality. Better way is reaching bugless
implementation of current functionality.
On Mon, Apr 15, 2019 at 4:51 PM Anton Vinogradov wrote:
Andrey,
>> It means also that at least method name is bad.
Agreed, already discussed with Aleksey Plekhanov.
Decided that ".withConsistencyCheck()" is a proper name.
>> What is the profit?
This proxy allows to check (and fix) is there any consistency violation
across the topology.
The proxy will
PetrovMikhail created IGNITE-11744:
--
Summary: Configuration for explicit plugins providing.
Key: IGNITE-11744
URL: https://issues.apache.org/jira/browse/IGNITE-11744
Project: Ignite
Issue
Sergey Chugunov created IGNITE-11743:
Summary: Stopping caches concurrently with node join may lead to
crash of the node
Key: IGNITE-11743
URL: https://issues.apache.org/jira/browse/IGNITE-11743
Thanks for responding, I will file JIRA issue shortly.
On Mon, Apr 15, 2019 at 2:24 PM Павлухин Иван wrote:
> Hi,
>
> +1
>
> I failed to imagine a case when IgniteSystemProperties.getString can
> make a real harm.
>
> пн, 15 апр. 2019 г. в 09:35, Ilya Kasnacheev :
> >
> > Hello!
> >
> > I think
Anton,
what does expression "withConsistency" mean? From user's standpoint it
means that all operations performed without this proxy are not
consistent. It means also that at least method name is bad.
Are there any guarantees that withConsistency proxy will not contain
bugs that will lead to
Hello, Ilya.
> Ignite does not touch every page of data region, and until you touch a page
> OS will not allocate any specific physical RAM to the virtual RAM address of
> that page.
This is not true.
Take a look into this discussion [1]
> Moreover, AFAIK Ignite will not even allocate all the
Ilya Borisov created IGNITE-11742:
-
Summary: Web console: grid-showing-rows component in grids with no
selection
Key: IGNITE-11742
URL: https://issues.apache.org/jira/browse/IGNITE-11742
Project:
Hello!
Ignite does not touch every page of data region, and until you touch a page
OS will not allocate any specific physical RAM to the virtual RAM address
of that page.
Moreover, AFAIK Ignite will not even allocate all the memory permitted by
data region until it is needed. It will allocate
Hi,
+1
I failed to imagine a case when IgniteSystemProperties.getString can
make a real harm.
пн, 15 апр. 2019 г. в 09:35, Ilya Kasnacheev :
>
> Hello!
>
> I think it does indeed makes sense to always use
> *IgniteSystemProperties.getStri**ng*
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> чт, 11
Hello, Igniters.
Why test on TC can allocate Data Region bigger than the amount of available RAM?
How can I disable this feature in a specific test?
"memoryAllocated=1024.0 GiB ... required=1093413MB, available=96675MB"
I have a test [1] that try to create Data Region of 1024 Gib size.
I want
Hello!
I think it does indeed makes sense to always use
*IgniteSystemProperties.getStri**ng*
Regards,
--
Ilya Kasnacheev
чт, 11 апр. 2019 г. в 16:40, Alexey Kuznetsov :
> Hi, Igniters.
>
> What do you think, if we will use " IgniteSystemProperties.getString(key)"
> instead of "
20 matches
Mail list logo
