[jira] [Updated] (IGNITE-4025) .NET: Services example get exception on the standalone node from time to time
[
https://issues.apache.org/jira/browse/IGNITE-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-4025:
---
Attachment: standalone_ignite-e0b91af5.0.log
serviceExample_ignite-a76dc416.0.log
> .NET: Services example get exception on the standalone node from time to time
> --
>
> Key: IGNITE-4025
> URL: https://issues.apache.org/jira/browse/IGNITE-4025
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.8
>Reporter: Vasilisa Sidorova
> Labels: .net
> Attachments: serviceExample_ignite-a76dc416.0.log,
> standalone_ignite-e0b91af5.0.log
>
>
> -
> STEPS FOR REPRODUCE
> -
> # Run standalone Apache Ignite.NET node as it's wrote in the xmldoc of
> example (it can be one or more nodes)
> # Start Service example
> -
> ACTUAL RESULT
> -
> There is exception on the on the standalone node console after example node
> is stopped:
> {noformat}
> [19:22:04,478][SEVERE][sys-#26%null%][IgniteTxManager] Failed to send one
> phase commit ack to backup node [backup=a76dc416-1946-4501-a866-057fe17e797e]
> class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
> Failed to send message because node left grid
> [nodeId=a76dc416-1946-4501-a866-057fe17e797e, msg=
> GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion [topVer=87078016,
> time=1475598123955, order=1475598068782, nodeOrder=1]],
> super=GridCacheMessage [msgId=-1, depI
> nfo=null, err=null, skipPrepare=false, cacheId=0, cacheId=0]]]
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:987)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
> at
> org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
> at
> org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
> at
> org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6587)
> at
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:790)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Look at the attached logs
> -
> EXPECTED RESULT
> -
> There aren't any exception on the nodes
> -
> ADDITIONAL INFO
> -
> Reproducible is 2/4
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4025) .NET: Services example get exception on the standalone node from time to time
Vasilisa Sidorova created IGNITE-4025:
--
Summary: .NET: Services example get exception on the standalone
node from time to time
Key: IGNITE-4025
URL: https://issues.apache.org/jira/browse/IGNITE-4025
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 1.8
Reporter: Vasilisa Sidorova
-
STEPS FOR REPRODUCE
-
# Run standalone Apache Ignite.NET node as it's wrote in the xmldoc of example
(it can be one or more nodes)
# Start Service example
-
ACTUAL RESULT
-
There is exception on the on the standalone node console after example node is
stopped:
{noformat}
[19:22:04,478][SEVERE][sys-#26%null%][IgniteTxManager] Failed to send one phase
commit ack to backup node [backup=a76dc416-1946-4501-a866-057fe17e797e]
class org.apache.ignite.internal.cluster.ClusterTopologyCheckedException:
Failed to send message because node left grid
[nodeId=a76dc416-1946-4501-a866-057fe17e797e, msg=
GridDhtTxOnePhaseCommitAckRequest [vers=[GridCacheVersion [topVer=87078016,
time=1475598123955, order=1475598068782, nodeOrder=1]], super=GridCacheMessage
[msgId=-1, depI
nfo=null, err=null, skipPrepare=false, cacheId=0, cacheId=0]]]
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:987)
at
org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$2.finish(IgniteTxManager.java:283)
at
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.finish0(GridDeferredAckMessageSender.java:214)
at
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer.access$000(GridDeferredAckMessageSender.java:111)
at
org.apache.ignite.internal.processors.cache.GridDeferredAckMessageSender$DeferredAckMessageBuffer$1.run(GridDeferredAckMessageSender.java:159)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6587)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:790)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}
Look at the attached logs
-
EXPECTED RESULT
-
There aren't any exception on the nodes
-
ADDITIONAL INFO
-
Reproducible is 2/4
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-4024) .Net: .net examples xmldoc need to be improved
[
https://issues.apache.org/jira/browse/IGNITE-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-4024:
---
Priority: Minor (was: Major)
> .Net: .net examples xmldoc need to be improved
> --
>
> Key: IGNITE-4024
> URL: https://issues.apache.org/jira/browse/IGNITE-4024
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.8
>Reporter: Vasilisa Sidorova
>Priority: Minor
> Labels: .net
>
> The string from examples xmldoc:
> {noformat}
> 1) Run %IGNITE_HOME%/platforms/dotnet/bin/Apache.Ignite.exe:
> /// Apache.Ignite.exe
> -configFileName=platforms\dotnet\examples\apache.ignite.examples\app.config
> -assembly=[path_to_Apache.Ignite.ExamplesDll.dll]
> {noformat}
> doesn't work as it is.
> Proposal: change string to:
> {noformat}
> 1) Run Apache.Ignite.exe from %IGNITE_HOME%\platforms\dotnet\bin\:
> /// Apache.Ignite.exe
> -configFileName=%IGNITE_HOME%\platforms\dotnet\examples\apache.ignite.examples\app.config
> -assembly=[path_to_Apache.Ignite.ExamplesDll.dll]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4024) .Net: .net examples xmldoc need to be improved
Vasilisa Sidorova created IGNITE-4024:
--
Summary: .Net: .net examples xmldoc need to be improved
Key: IGNITE-4024
URL: https://issues.apache.org/jira/browse/IGNITE-4024
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 1.8
Reporter: Vasilisa Sidorova
The string from examples xmldoc:
{noformat}
1) Run %IGNITE_HOME%/platforms/dotnet/bin/Apache.Ignite.exe:
/// Apache.Ignite.exe
-configFileName=platforms\dotnet\examples\apache.ignite.examples\app.config
-assembly=[path_to_Apache.Ignite.ExamplesDll.dll]
{noformat}
doesn't work as it is.
Proposal: change string to:
{noformat}
1) Run Apache.Ignite.exe from %IGNITE_HOME%\platforms\dotnet\bin\:
/// Apache.Ignite.exe
-configFileName=%IGNITE_HOME%\platforms\dotnet\examples\apache.ignite.examples\app.config
-assembly=[path_to_Apache.Ignite.ExamplesDll.dll]
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-3956) .NET: NuGet examples for LinqPad failed for specific scenario
[
https://issues.apache.org/jira/browse/IGNITE-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova closed IGNITE-3956.
--
Assignee: (was: Vasilisa Sidorova)
Fix verified for Apache Ignite 1.8
> .NET: NuGet examples for LinqPad failed for specific scenario
> -
>
> Key: IGNITE-3956
> URL: https://issues.apache.org/jira/browse/IGNITE-3956
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.6
> Environment: Win7, Apache Ignite 1.6.8, LINQPad 4
>Reporter: Vasilisa Sidorova
>Priority: Minor
> Labels: .net
> Fix For: 1.8
>
> Attachments: LINQPad 4_exampleError.png
>
>
> -
> DESCRIPTION
> -
> Nuget examples for LinqPad fail if they are running one-by-one with pure Java
> node. Proposal: remove "CreateCache" method by "GetOrCreateCache" and/or get
> different names to caches from different examples
> -
> STEPS FOR REPRODUCE
> -
> # In the default-config.xml add properties dor class
> org.apache.ignite.configuration.IgniteConfiguration:
> {noformat}
>
>
>
>
>
>
>
>
>
>class="org.apache.ignite.binary.BinaryBasicNameMapper">
>
>
>
>
>
> {noformat}
> # Run pure Java node (ignite.bat)
> # Run LinqPad 4
> # Add Apache.Ignite package
> # Go to "Samples" Tab -> run all examples from nuget -> Apache.Ignite and
> nuget -> Apache.Ignite.Linq
> -
> ACTUAL RESULT
> -
> Query and PutGet examples fail with "Failed to start cache" exception. Look
> at the attached picture
> -
> EXPECTED RESULT
> -
> Examples can be runnable on the one pure Java node many times without any
> exceptions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-3995) .NET: ASP.NET Session-State Store Provider run cache with default "null" name
[
https://issues.apache.org/jira/browse/IGNITE-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova closed IGNITE-3995.
--
Assignee: (was: Vasilisa Sidorova)
> .NET: ASP.NET Session-State Store Provider run cache with default "null" name
> -
>
> Key: IGNITE-3995
> URL: https://issues.apache.org/jira/browse/IGNITE-3995
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Windows 7 OS
>Reporter: Vasilisa Sidorova
> Labels: .net
> Fix For: 1.8
>
>
> STEPS TO REPDODUCE
> ---
> # Create a new C# Web application in the MS Visual Studio: File -> New ->
> Project -> Visual C# -> Web -> ASP.NET Web Application
> # In the Package Manager Console install Apache.Ignite.AspNet package
> # Open Web.config file and add following code to the "system.web" section:
> {noformat}
>
>
>
> type="Apache.Ignite.AspNet.IgniteSessionStateStoreProvider,
> Apache.Ignite.AspNet" />
>
>
> {noformat}
> # Run project (Ctrl-F5) (ASP.NET page is opened in browser)
> # Connect to started cache via console application or visorcmd and look onto
> cache name
> ---
> ACTUAL RESULT
> ---
> Started cache have "null" name
> ---
> EXPECTED RESULT
> ---
> Default cache name have name differ from "null" - it's bad name and can cause
> unexpected errors
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3995) .NET: ASP.NET Session-State Store Provider run cache with default "null" name
[
https://issues.apache.org/jira/browse/IGNITE-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15532408#comment-15532408
]
Vasilisa Sidorova commented on IGNITE-3995:
Fix verified for Apache Ignite 1.8
> .NET: ASP.NET Session-State Store Provider run cache with default "null" name
> -
>
> Key: IGNITE-3995
> URL: https://issues.apache.org/jira/browse/IGNITE-3995
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Windows 7 OS
>Reporter: Vasilisa Sidorova
>Assignee: Vasilisa Sidorova
> Labels: .net
> Fix For: 1.8
>
>
> STEPS TO REPDODUCE
> ---
> # Create a new C# Web application in the MS Visual Studio: File -> New ->
> Project -> Visual C# -> Web -> ASP.NET Web Application
> # In the Package Manager Console install Apache.Ignite.AspNet package
> # Open Web.config file and add following code to the "system.web" section:
> {noformat}
>
>
>
> type="Apache.Ignite.AspNet.IgniteSessionStateStoreProvider,
> Apache.Ignite.AspNet" />
>
>
> {noformat}
> # Run project (Ctrl-F5) (ASP.NET page is opened in browser)
> # Connect to started cache via console application or visorcmd and look onto
> cache name
> ---
> ACTUAL RESULT
> ---
> Started cache have "null" name
> ---
> EXPECTED RESULT
> ---
> Default cache name have name differ from "null" - it's bad name and can cause
> unexpected errors
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-3995) .NET: ASP.NET Session-State Store Provider run cache with default "null" name
[
https://issues.apache.org/jira/browse/IGNITE-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova reassigned IGNITE-3995:
--
Assignee: Vasilisa Sidorova (was: Vladimir Ozerov)
> .NET: ASP.NET Session-State Store Provider run cache with default "null" name
> -
>
> Key: IGNITE-3995
> URL: https://issues.apache.org/jira/browse/IGNITE-3995
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Windows 7 OS
>Reporter: Vasilisa Sidorova
>Assignee: Vasilisa Sidorova
> Labels: .net
> Fix For: 1.8
>
>
> STEPS TO REPDODUCE
> ---
> # Create a new C# Web application in the MS Visual Studio: File -> New ->
> Project -> Visual C# -> Web -> ASP.NET Web Application
> # In the Package Manager Console install Apache.Ignite.AspNet package
> # Open Web.config file and add following code to the "system.web" section:
> {noformat}
>
>
>
> type="Apache.Ignite.AspNet.IgniteSessionStateStoreProvider,
> Apache.Ignite.AspNet" />
>
>
> {noformat}
> # Run project (Ctrl-F5) (ASP.NET page is opened in browser)
> # Connect to started cache via console application or visorcmd and look onto
> cache name
> ---
> ACTUAL RESULT
> ---
> Started cache have "null" name
> ---
> EXPECTED RESULT
> ---
> Default cache name have name differ from "null" - it's bad name and can cause
> unexpected errors
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-3983) CacheBinaryAutoStoreExample get wrong result
[
https://issues.apache.org/jira/browse/IGNITE-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova closed IGNITE-3983.
--
Assignee: (was: Vasilisa Sidorova)
> CacheBinaryAutoStoreExample get wrong result
>
>
> Key: IGNITE-3983
> URL: https://issues.apache.org/jira/browse/IGNITE-3983
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Ubuntu 14.04, Win7, Apache Ignite 1.8
>Reporter: Vasilisa Sidorova
>Priority: Critical
> Fix For: 1.8
>
>
> -
> DESCRIPTION
> -
> CacheBinaryAutoStoreExample get wrong result
> -
> STEPS FOR REPRODUCE
> -
> # Build examples project
> # Start H2 database TCP server using
> # Start a few nodes using ExampleNodeStartup (it's stable reproducible with
> different numbers of nodes)
> -
> ACTUAL RESULT
> -
> {noformat}
> >>> Populate database with data...
> >>> Cache auto store example started...
> >>> Read value: null
> >>> Overwrote old value: null
> >>> Read value: Person [id=25121642, orgId=1, lastName=Newton,
> >>> firstName=Isaac, salary=100.1, resume=English physicist and mathematician]
> >>> Update salary in transaction...
> >>> Read value after commit: Person [id=25121642, orgId=1, lastName=Newton,
> >>> firstName=Isaac, salary=200.2, resume=English physicist and mathematician]
> >>> --
> >>> Load data to cache from DB with custom SQL...
> >>> Loaded cache entries: 3
> >>> Load ALL data to cache from DB...
> >>> Loaded cache entries: 0
> {noformat}
> -
> EXPECTED RESULT
> -
> {noformat}
> >>> Populate database with data...
> >>> Cache auto store example started...
> >>> Read value: null
> >>> Overwrote old value: null
> >>> Read value: Person [id=25121642, orgId=1, lastName=Newton,
> >>> firstName=Isaac, salary=100.1, resume=English physicist and mathematician]
> >>> Update salary in transaction...
> >>> Read value after commit: Person [id=25121642, orgId=1, lastName=Newton,
> >>> firstName=Isaac, salary=200.2, resume=English physicist and mathematician]
> >>> --
> >>> Load data to cache from DB with custom SQL...
> >>> Loaded cache entries: 3
> >>> Load ALL data to cache from DB...
> >>> Loaded cache entries: 7
> {noformat}
> -
> ADDITIONAL INFO
> -
> Isn't reproducible for previous versions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3983) CacheBinaryAutoStoreExample get wrong result
[
https://issues.apache.org/jira/browse/IGNITE-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530024#comment-15530024
]
Vasilisa Sidorova commented on IGNITE-3983:
Fix verified for Apache Ignite 1.8
> CacheBinaryAutoStoreExample get wrong result
>
>
> Key: IGNITE-3983
> URL: https://issues.apache.org/jira/browse/IGNITE-3983
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Ubuntu 14.04, Win7, Apache Ignite 1.8
>Reporter: Vasilisa Sidorova
>Assignee: Vasilisa Sidorova
>Priority: Critical
> Fix For: 1.8
>
>
> -
> DESCRIPTION
> -
> CacheBinaryAutoStoreExample get wrong result
> -
> STEPS FOR REPRODUCE
> -
> # Build examples project
> # Start H2 database TCP server using
> # Start a few nodes using ExampleNodeStartup (it's stable reproducible with
> different numbers of nodes)
> -
> ACTUAL RESULT
> -
> {noformat}
> >>> Populate database with data...
> >>> Cache auto store example started...
> >>> Read value: null
> >>> Overwrote old value: null
> >>> Read value: Person [id=25121642, orgId=1, lastName=Newton,
> >>> firstName=Isaac, salary=100.1, resume=English physicist and mathematician]
> >>> Update salary in transaction...
> >>> Read value after commit: Person [id=25121642, orgId=1, lastName=Newton,
> >>> firstName=Isaac, salary=200.2, resume=English physicist and mathematician]
> >>> --
> >>> Load data to cache from DB with custom SQL...
> >>> Loaded cache entries: 3
> >>> Load ALL data to cache from DB...
> >>> Loaded cache entries: 0
> {noformat}
> -
> EXPECTED RESULT
> -
> {noformat}
> >>> Populate database with data...
> >>> Cache auto store example started...
> >>> Read value: null
> >>> Overwrote old value: null
> >>> Read value: Person [id=25121642, orgId=1, lastName=Newton,
> >>> firstName=Isaac, salary=100.1, resume=English physicist and mathematician]
> >>> Update salary in transaction...
> >>> Read value after commit: Person [id=25121642, orgId=1, lastName=Newton,
> >>> firstName=Isaac, salary=200.2, resume=English physicist and mathematician]
> >>> --
> >>> Load data to cache from DB with custom SQL...
> >>> Loaded cache entries: 3
> >>> Load ALL data to cache from DB...
> >>> Loaded cache entries: 7
> {noformat}
> -
> ADDITIONAL INFO
> -
> Isn't reproducible for previous versions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3996) .NET: ASP.NET Output Cache provider run cache with default "null" name
[
https://issues.apache.org/jira/browse/IGNITE-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3996:
---
Labels: .net (was: )
> .NET: ASP.NET Output Cache provider run cache with default "null" name
> --
>
> Key: IGNITE-3996
> URL: https://issues.apache.org/jira/browse/IGNITE-3996
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Windows 7
>Reporter: Vasilisa Sidorova
> Labels: .net
> Fix For: 2.0
>
>
> STEPS TO REPDODUCE
> ---
> # Create a new C# Web application in the MS Visual Studio: File -> New ->
> Project -> Visual C# -> Web -> ASP.NET Web Application
> # In the Package Manager Console install Apache.Ignite.AspNet package
> # Open Web.config file and add following code to the "system.web" section:
> {noformat}
>
>
>
> type="Apache.Ignite.AspNet.IgniteOutputCacheProvider, Apache.Ignite.AspNet"
> igniteConfigurationSectionName="igniteConfiguration" cacheName="myWebCache" />
>
>
>
> {noformat}
> and add following code into beginning of "configuration" section:
> {noformat}
>
> type="Apache.Ignite.Core.IgniteConfigurationSection, Apache.Ignite.Core" />
>
>
>
>
>
>
> {noformat}
> # Run project (Ctrl-F5) (ASP.NET page is opened in browser)
> # Connect to started cache via console application or visorcmd and look onto
> cache name
> ---
> ACTUAL RESULT
> ---
> Started cache have "null" name
> ---
> EXPECTED RESULT
> ---
> Default cache name have name differ from "null" - it's bad name and can cause
> unexpected errors
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3996) .NET: ASP.NET Output Cache provider run cache with default "null" name
Vasilisa Sidorova created IGNITE-3996:
--
Summary: .NET: ASP.NET Output Cache provider run cache with
default "null" name
Key: IGNITE-3996
URL: https://issues.apache.org/jira/browse/IGNITE-3996
Project: Ignite
Issue Type: Bug
Affects Versions: 1.8
Environment: Windows 7
Reporter: Vasilisa Sidorova
STEPS TO REPDODUCE
---
# Create a new C# Web application in the MS Visual Studio: File -> New ->
Project -> Visual C# -> Web -> ASP.NET Web Application
# In the Package Manager Console install Apache.Ignite.AspNet package
# Open Web.config file and add following code to the "system.web" section:
{noformat}
{noformat}
and add following code into beginning of "configuration" section:
{noformat}
{noformat}
# Run project (Ctrl-F5) (ASP.NET page is opened in browser)
# Connect to started cache via console application or visorcmd and look onto
cache name
---
ACTUAL RESULT
---
Started cache have "null" name
---
EXPECTED RESULT
---
Default cache name have name differ from "null" - it's bad name and can cause
unexpected errors
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-3199) .NET: ASP.NET Session-State Store Provider
[ https://issues.apache.org/jira/browse/IGNITE-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasilisa Sidorova closed IGNITE-3199. -- Assignee: (was: Vasilisa Sidorova) > .NET: ASP.NET Session-State Store Provider > -- > > Key: IGNITE-3199 > URL: https://issues.apache.org/jira/browse/IGNITE-3199 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Affects Versions: 1.7 >Reporter: Pavel Tupitsyn > Labels: .net > Fix For: 1.8 > > > See https://msdn.microsoft.com/en-us/library/ms178587.aspx > Code should be put to Apache.Ignite.AspNet assembly (see IGNITE-2379) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3199) .NET: ASP.NET Session-State Store Provider
[ https://issues.apache.org/jira/browse/IGNITE-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529584#comment-15529584 ] Vasilisa Sidorova commented on IGNITE-3199: Verified for Apache Ignite 1.8, but open new linked issue IGNITE-3995 > .NET: ASP.NET Session-State Store Provider > -- > > Key: IGNITE-3199 > URL: https://issues.apache.org/jira/browse/IGNITE-3199 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Affects Versions: 1.7 >Reporter: Pavel Tupitsyn >Assignee: Vasilisa Sidorova > Labels: .net > Fix For: 1.8 > > > See https://msdn.microsoft.com/en-us/library/ms178587.aspx > Code should be put to Apache.Ignite.AspNet assembly (see IGNITE-2379) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3995) .NET: ASP.NET Session-State Store Provider run cache with default "null" name
[
https://issues.apache.org/jira/browse/IGNITE-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3995:
---
Description:
STEPS TO REPDODUCE
---
# Create a new C# Web application in the MS Visual Studio: File -> New ->
Project -> Visual C# -> Web -> ASP.NET Web Application
# In the Package Manager Console install Apache.Ignite.AspNet package
# Open Web.config file and add following code to the "system.web" section:
{noformat}
{noformat}
# Run project (Ctrl-F5) (ASP.NET page is opened in browser)
# Connect to started cache via console application or visorcmd and look onto
cache name
---
ACTUAL RESULT
---
Started cache have "null" name
---
EXPECTED RESULT
---
Default cache name have name differ from "null" - it's bad name and can cause
unexpected errors
was:
STEPS TO REPDODUCE
---
# Create a new C# Web application in the MS Visual Studio: File -> New ->
Project -> Visual C# -> Web -> ASP.NET Web Application
# In the Package Manager Console install Apache.Ignite.AspNet package
Result: This should produce no errors (red text)
# Open Web.config file and add following code to the "system.web" section:
{noformat}
{noformat}
# Run project (Ctrl-F5) (ASP.NET page is opened in browser)
# Connect to started cache via console application or visorcmd and look onto
cache name
---
ACTUAL RESULT
---
Started cache have "null" name
---
EXPECTED RESULT
---
Default cache name have name differ from "null" - it's bad name and can cause
unexpected errors
> .NET: ASP.NET Session-State Store Provider run cache with default "null" name
> -
>
> Key: IGNITE-3995
> URL: https://issues.apache.org/jira/browse/IGNITE-3995
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Windows 7 OS
>Reporter: Vasilisa Sidorova
> Labels: .net
>
> STEPS TO REPDODUCE
> ---
> # Create a new C# Web application in the MS Visual Studio: File -> New ->
> Project -> Visual C# -> Web -> ASP.NET Web Application
> # In the Package Manager Console install Apache.Ignite.AspNet package
> # Open Web.config file and add following code to the "system.web" section:
> {noformat}
>
>
>
> type="Apache.Ignite.AspNet.IgniteSessionStateStoreProvider,
> Apache.Ignite.AspNet" />
>
>
> {noformat}
> # Run project (Ctrl-F5) (ASP.NET page is opened in browser)
> # Connect to started cache via console application or visorcmd and look onto
> cache name
> ---
> ACTUAL RESULT
> ---
> Started cache have "null" name
> ---
> EXPECTED RESULT
> ---
> Default cache name have name differ from "null" - it's bad name and can cause
> unexpected errors
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3995) .NET: ASP.NET Session-State Store Provider run cache with default "null" name
[
https://issues.apache.org/jira/browse/IGNITE-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3995:
---
Environment: Windows 7 OS (was: Win7)
> .NET: ASP.NET Session-State Store Provider run cache with default "null" name
> -
>
> Key: IGNITE-3995
> URL: https://issues.apache.org/jira/browse/IGNITE-3995
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.8
> Environment: Windows 7 OS
>Reporter: Vasilisa Sidorova
> Labels: .net
>
> STEPS TO REPDODUCE
> ---
> # Create a new C# Web application in the MS Visual Studio: File -> New ->
> Project -> Visual C# -> Web -> ASP.NET Web Application
> # In the Package Manager Console install Apache.Ignite.AspNet package
> Result: This should produce no errors (red text)
> # Open Web.config file and add following code to the "system.web" section:
> {noformat}
>
>
>
> type="Apache.Ignite.AspNet.IgniteSessionStateStoreProvider,
> Apache.Ignite.AspNet" />
>
>
> {noformat}
> # Run project (Ctrl-F5) (ASP.NET page is opened in browser)
> # Connect to started cache via console application or visorcmd and look onto
> cache name
> ---
> ACTUAL RESULT
> ---
> Started cache have "null" name
> ---
> EXPECTED RESULT
> ---
> Default cache name have name differ from "null" - it's bad name and can cause
> unexpected errors
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3995) .NET: ASP.NET Session-State Store Provider run cache with default "null" name
Vasilisa Sidorova created IGNITE-3995:
--
Summary: .NET: ASP.NET Session-State Store Provider run cache with
default "null" name
Key: IGNITE-3995
URL: https://issues.apache.org/jira/browse/IGNITE-3995
Project: Ignite
Issue Type: Bug
Affects Versions: 1.8
Environment: Win7
Reporter: Vasilisa Sidorova
STEPS TO REPDODUCE
---
# Create a new C# Web application in the MS Visual Studio: File -> New ->
Project -> Visual C# -> Web -> ASP.NET Web Application
# In the Package Manager Console install Apache.Ignite.AspNet package
Result: This should produce no errors (red text)
# Open Web.config file and add following code to the "system.web" section:
{noformat}
{noformat}
# Run project (Ctrl-F5) (ASP.NET page is opened in browser)
# Connect to started cache via console application or visorcmd and look onto
cache name
---
ACTUAL RESULT
---
Started cache have "null" name
---
EXPECTED RESULT
---
Default cache name have name differ from "null" - it's bad name and can cause
unexpected errors
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3983) CacheBinaryAutoStoreExample get wrong result
Vasilisa Sidorova created IGNITE-3983:
--
Summary: CacheBinaryAutoStoreExample get wrong result
Key: IGNITE-3983
URL: https://issues.apache.org/jira/browse/IGNITE-3983
Project: Ignite
Issue Type: Bug
Affects Versions: 1.7
Environment: Ubuntu 14.04, Win7, Apache Ignite 1.7.2
Reporter: Vasilisa Sidorova
Priority: Critical
-
DESCRIPTION
-
CacheBinaryAutoStoreExample get wrong result
-
STEPS FOR REPRODUCE
-
# Build examples project
# Start H2 database TCP server using
# Start a few nodes using ExampleNodeStartup (it's stable reproducible with
different numbers of nodes)
-
ACTUAL RESULT
-
{noformat}
>>> Populate database with data...
>>> Cache auto store example started...
>>> Read value: null
>>> Overwrote old value: null
>>> Read value: Person [id=25121642, orgId=1, lastName=Newton, firstName=Isaac,
>>> salary=100.1, resume=English physicist and mathematician]
>>> Update salary in transaction...
>>> Read value after commit: Person [id=25121642, orgId=1, lastName=Newton,
>>> firstName=Isaac, salary=200.2, resume=English physicist and mathematician]
>>> --
>>> Load data to cache from DB with custom SQL...
>>> Loaded cache entries: 3
>>> Load ALL data to cache from DB...
>>> Loaded cache entries: 0
{noformat}
-
EXPECTED RESULT
-
{noformat}
>>> Populate database with data...
>>> Cache auto store example started...
>>> Read value: null
>>> Overwrote old value: null
>>> Read value: Person [id=25121642, orgId=1, lastName=Newton, firstName=Isaac,
>>> salary=100.1, resume=English physicist and mathematician]
>>> Update salary in transaction...
>>> Read value after commit: Person [id=25121642, orgId=1, lastName=Newton,
>>> firstName=Isaac, salary=200.2, resume=English physicist and mathematician]
>>> --
>>> Load data to cache from DB with custom SQL...
>>> Loaded cache entries: 3
>>> Load ALL data to cache from DB...
>>> Loaded cache entries: 7
{noformat}
-
ADDITIONAL INFO
-
Isn't reproducible for previous versions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-3956) .NET: NuGet examples for LinqPad failed for specific scenario
[
https://issues.apache.org/jira/browse/IGNITE-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova reassigned IGNITE-3956:
--
Assignee: Vasilisa Sidorova
> .NET: NuGet examples for LinqPad failed for specific scenario
> -
>
> Key: IGNITE-3956
> URL: https://issues.apache.org/jira/browse/IGNITE-3956
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.6
> Environment: Win7, Apache Ignite 1.6.8, LINQPad 4
>Reporter: Vasilisa Sidorova
>Assignee: Vasilisa Sidorova
>Priority: Minor
> Labels: .net
> Fix For: 1.8
>
> Attachments: LINQPad 4_exampleError.png
>
>
> -
> DESCRIPTION
> -
> Nuget examples for LinqPad fail if they are running one-by-one with pure Java
> node. Proposal: remove "CreateCache" method by "GetOrCreateCache" and/or get
> different names to caches from different examples
> -
> STEPS FOR REPRODUCE
> -
> # In the default-config.xml add properties dor class
> org.apache.ignite.configuration.IgniteConfiguration:
> {noformat}
>
>
>
>
>
>
>
>
>
>class="org.apache.ignite.binary.BinaryBasicNameMapper">
>
>
>
>
>
> {noformat}
> # Run pure Java node (ignite.bat)
> # Run LinqPad 4
> # Add Apache.Ignite package
> # Go to "Samples" Tab -> run all examples from nuget -> Apache.Ignite and
> nuget -> Apache.Ignite.Linq
> -
> ACTUAL RESULT
> -
> Query and PutGet examples fail with "Failed to start cache" exception. Look
> at the attached picture
> -
> EXPECTED RESULT
> -
> Examples can be runnable on the one pure Java node many times without any
> exceptions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3901) Mesos deployment: IGNITE_PACKAGE_URL parameter don't work correctly
[ https://issues.apache.org/jira/browse/IGNITE-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasilisa Sidorova updated IGNITE-3901: --- Description: - DESCRIPTION - Mesos deployment failed if IGNITE_PACKAGE_URL is used (instead IGNITE_VERSION or IGNITE_PACKAGE_PATH parameters) - STEPS FOR REPRODUCE - # Prepare marathon.json file for deployment through Marathon and set correct IGNITE_PACKAGE_URL here # Run framework according to instruction https://apacheignite.readme.io/docs/mesos-deployment - ACTUAL RESULT - Ignition application is started but nodes couldn't be running as binaries is not fully downloaded (look at the attached picture) - EXPECTED RESULT - Deployment is successful as for IGNITE_VERSION parameter - ADDITIONAL INFO - Isn't reproducible for running framework via jar file in the default mode and with properties.prop file was: - DESCRIPTION - Mesos deployment failed if IGNITE_PACKAGE_URL is used (instead IGNITE_VERSION or IGNITE_PACKAGE_PATH parameters) - STEPS FOR REPRODUCE - # Prepare marathon.json file for deployment through Marathon and set correct IGNITE_PACKAGE_URL here # Run framework according to instruction https://apacheignite.readme.io/docs/mesos-deployment - ACTUAL RESULT - Ignition application is started but nodes couldn't be running as binaries is not fully downloaded (look at the attached picture) - EXPECTED RESULT - Deployment is successful as for IGNITE_VERSION parameter - ADDITIONAL INFO - Reproducible for running framework via jar file in the default mode (without properties.prop file) > Mesos deployment: IGNITE_PACKAGE_URL parameter don't work correctly > --- > > Key: IGNITE-3901 > URL: https://issues.apache.org/jira/browse/IGNITE-3901 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.6 > Environment: Ubuntu 14.04, Apache Ignite 1.6.7 >Reporter: Vasilisa Sidorova > Attachments: failed_task.png > > > - > DESCRIPTION > - > Mesos deployment failed if IGNITE_PACKAGE_URL is used (instead IGNITE_VERSION > or IGNITE_PACKAGE_PATH parameters) > - > STEPS FOR REPRODUCE > - > # Prepare marathon.json file for deployment through Marathon and set correct > IGNITE_PACKAGE_URL here > # Run framework according to instruction > https://apacheignite.readme.io/docs/mesos-deployment > - > ACTUAL RESULT > - > Ignition application is started but nodes couldn't be running as binaries is > not fully downloaded (look at the attached picture) > - > EXPECTED RESULT > - > Deployment is successful as for IGNITE_VERSION parameter > - > ADDITIONAL INFO > - > Isn't reproducible for running framework via jar file in the default mode and > with properties.prop file -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3956) .NET: nuget examples for LinqPad failed for specific scenario
[
https://issues.apache.org/jira/browse/IGNITE-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3956:
---
Summary: .NET: nuget examples for LinqPad failed for specific scenario
(was: .NET: Nuget examples for LinqPad failed for specific scenario)
> .NET: nuget examples for LinqPad failed for specific scenario
> -
>
> Key: IGNITE-3956
> URL: https://issues.apache.org/jira/browse/IGNITE-3956
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.6
> Environment: Win7, Apache Ignite 1.6.8, LINQPad 4
>Reporter: Vasilisa Sidorova
> Labels: .net
> Attachments: LINQPad 4_exampleError.png
>
>
> -
> DESCRIPTION
> -
> Nuget examples for LinqPad fail if they are running one-by-one with pure Java
> node. Proposal: remove "CreateCache" method by "GetOrCreateCache" and/or get
> different names to caches from different examples
> -
> STEPS FOR REPRODUCE
> -
> # In the default-config.xml add properties dor class
> org.apache.ignite.configuration.IgniteConfiguration:
> {noformat}
>
>
>
>
>
>
>
>
>
>class="org.apache.ignite.binary.BinaryBasicNameMapper">
>
>
>
>
>
> {noformat}
> # Run pure Java node (ignite.bat)
> # Run LinqPad 4
> # Add Apache.Ignite package
> # Go to "Samples" Tab -> run all examples from nuget -> Apache.Ignite and
> nuget -> Apache.Ignite.Linq
> -
> ACTUAL RESULT
> -
> Query and PutGet examples fail with "Failed to start cache" exception. Look
> at the attached picture
> -
> EXPECTED RESULT
> -
> Examples can be runnable on the one pure Java node many times without any
> exceptions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3956) Nuget examples for LinqPad fail for specific scenario
[
https://issues.apache.org/jira/browse/IGNITE-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3956:
---
Attachment: LINQPad 4_exampleError.png
> Nuget examples for LinqPad fail for specific scenario
> -
>
> Key: IGNITE-3956
> URL: https://issues.apache.org/jira/browse/IGNITE-3956
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.6
> Environment: Win7, Apache Ignite 1.6.8, LINQPad 4
>Reporter: Vasilisa Sidorova
> Attachments: LINQPad 4_exampleError.png
>
>
> -
> DESCRIPTION
> -
> Nuget examples for LinqPad fail if they are running one-by-one with pure Java
> node. Proposal: remove "CreateCache" method by "GetOrCreateCache" and/or get
> different names to caches from different examples
> -
> STEPS FOR REPRODUCE
> -
> # In the default-config.xml add properties dor class
> org.apache.ignite.configuration.IgniteConfiguration:
> {noformat}
>
>
>
>
>
>
>
>
>
>class="org.apache.ignite.binary.BinaryBasicNameMapper">
>
>
>
>
>
> {noformat}
> # Run pure Java node (ignite.bat)
> # Run LinqPad 4
> # Add Apache.Ignite package
> # Go to "Samples" Tab -> run all examples from nuget -> Apache.Ignite and
> nuget -> Apache.Ignite.Linq
> -
> ACTUAL RESULT
> -
> Query and PutGet examples fail with "Failed to start cache" exception. Look
> at the attached picture
> -
> EXPECTED RESULT
> -
> Examples can be runnable on the one pure Java node many times without any
> exceptions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3956) Nuget examples for LinqPad failed for specific scenario
[
https://issues.apache.org/jira/browse/IGNITE-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3956:
---
Summary: Nuget examples for LinqPad failed for specific scenario (was:
Nuget examples for LinqPad fail for specific scenario)
> Nuget examples for LinqPad failed for specific scenario
> ---
>
> Key: IGNITE-3956
> URL: https://issues.apache.org/jira/browse/IGNITE-3956
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.6
> Environment: Win7, Apache Ignite 1.6.8, LINQPad 4
>Reporter: Vasilisa Sidorova
> Attachments: LINQPad 4_exampleError.png
>
>
> -
> DESCRIPTION
> -
> Nuget examples for LinqPad fail if they are running one-by-one with pure Java
> node. Proposal: remove "CreateCache" method by "GetOrCreateCache" and/or get
> different names to caches from different examples
> -
> STEPS FOR REPRODUCE
> -
> # In the default-config.xml add properties dor class
> org.apache.ignite.configuration.IgniteConfiguration:
> {noformat}
>
>
>
>
>
>
>
>
>
>class="org.apache.ignite.binary.BinaryBasicNameMapper">
>
>
>
>
>
> {noformat}
> # Run pure Java node (ignite.bat)
> # Run LinqPad 4
> # Add Apache.Ignite package
> # Go to "Samples" Tab -> run all examples from nuget -> Apache.Ignite and
> nuget -> Apache.Ignite.Linq
> -
> ACTUAL RESULT
> -
> Query and PutGet examples fail with "Failed to start cache" exception. Look
> at the attached picture
> -
> EXPECTED RESULT
> -
> Examples can be runnable on the one pure Java node many times without any
> exceptions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3956) Nuget examples for LinqPad fail for specific scenario
Vasilisa Sidorova created IGNITE-3956:
--
Summary: Nuget examples for LinqPad fail for specific scenario
Key: IGNITE-3956
URL: https://issues.apache.org/jira/browse/IGNITE-3956
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 1.6
Environment: Win7, Apache Ignite 1.6.8, LINQPad 4
Reporter: Vasilisa Sidorova
-
DESCRIPTION
-
Nuget examples for LinqPad fail if they are running one-by-one with pure Java
node. Proposal: remove "CreateCache" method by "GetOrCreateCache" and/or get
different names to caches from different examples
-
STEPS FOR REPRODUCE
-
# In the default-config.xml add properties dor class
org.apache.ignite.configuration.IgniteConfiguration:
{noformat}
{noformat}
# Run pure Java node (ignite.bat)
# Run LinqPad 4
# Add Apache.Ignite package
# Go to "Samples" Tab -> run all examples from nuget -> Apache.Ignite and
nuget -> Apache.Ignite.Linq
-
ACTUAL RESULT
-
Query and PutGet examples fail with "Failed to start cache" exception. Look at
the attached picture
-
EXPECTED RESULT
-
Examples can be runnable on the one pure Java node many times without any
exceptions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-3861) ODBC: installer doesn't support path to driver with backspaces
[
https://issues.apache.org/jira/browse/IGNITE-3861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova closed IGNITE-3861.
--
Assignee: (was: Vasilisa Sidorova)
Fix verified for Ignite 1.6.8
> ODBC: installer doesn't support path to driver with backspaces
> --
>
> Key: IGNITE-3861
> URL: https://issues.apache.org/jira/browse/IGNITE-3861
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 1.6
> Environment: Win 8, odbc installer 1.6.7
>Reporter: Vasilisa Sidorova
> Fix For: 1.8
>
>
> -
> STEPS FOR REPRODUCE
> -
> # Build odbc driver according to instruction from
> $IGNITE_HOME/platforms/cpp/DEVNOTES.txt
> # Put driver into folder with path which contains backspaces
> # Install odbc driver according to instruction from
> $IGNITE_HOME/platforms/cpp/odbc/README.txt
> -
> ACTUAL RESULT
> -
> # Driver get error like this:
> {noformat}
> C:\ignite\platforms\cpp\odbc\install>install_x86.cmd "C:\Program
> Files\IgniteODBC\ignite.odbc.dll"
> warning: The path you have specified seems to be a directory. Note that you
> have to specify path to driver file itself instead.
> Installing driver: ""C:\Program Files\IgniteODBC\ignite.odbc.dll""
> The operation completed successfully.
> The operation completed successfully.
> ERROR: Invalid syntax.
> Type "REG ADD /?" for usage.
> The operation completed successfully.
> Driver can not be found: ""C:\Program Files\IgniteODBC\ignite.odbc.dll""
> Call format: install_x86 abs_path_to_driver
> Press any key to continue . . .
> {noformat}
> # Driver isn't installed
> -
> EXPECTED RESULT
> -
> Driver is installed without any exceptions or should give correct and clear
> error string
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-3199) .NET: ASP.NET Session-State Store Provider
[ https://issues.apache.org/jira/browse/IGNITE-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasilisa Sidorova reassigned IGNITE-3199: -- Assignee: Vasilisa Sidorova > .NET: ASP.NET Session-State Store Provider > -- > > Key: IGNITE-3199 > URL: https://issues.apache.org/jira/browse/IGNITE-3199 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Affects Versions: 1.7 >Reporter: Pavel Tupitsyn >Assignee: Vasilisa Sidorova > Labels: .net > Fix For: 1.8 > > > See https://msdn.microsoft.com/en-us/library/ms178587.aspx > Code should be put to Apache.Ignite.AspNet assembly (see IGNITE-2379) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3901) Mesos deployment: IGNITE_PACKAGE_URL parameter don't work correctly
[ https://issues.apache.org/jira/browse/IGNITE-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasilisa Sidorova updated IGNITE-3901: --- Summary: Mesos deployment: IGNITE_PACKAGE_URL parameter don't work correctly (was: Mesos deployment: some Mesos parameters don't work correctly) > Mesos deployment: IGNITE_PACKAGE_URL parameter don't work correctly > --- > > Key: IGNITE-3901 > URL: https://issues.apache.org/jira/browse/IGNITE-3901 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.6 > Environment: Ubuntu 14.04, Apache Ignite 1.6.7 >Reporter: Vasilisa Sidorova > Attachments: failed_task.png > > > - > DESCRIPTION > - > Mesos deployment failed if IGNITE_PACKAGE_URL is used (instead IGNITE_VERSION > or IGNITE_PACKAGE_PATH parameters) > - > STEPS FOR REPRODUCE > - > # Prepare marathon.json file for deployment through Marathon and set correct > IGNITE_PACKAGE_URL here > # Run framework according to instruction > https://apacheignite.readme.io/docs/mesos-deployment > - > ACTUAL RESULT > - > Ignition application is started but nodes couldn't be running as binaries is > not fully downloaded (look at the attached picture) > - > EXPECTED RESULT > - > Deployment is successful as for IGNITE_VERSION parameter > - > ADDITIONAL INFO > - > Reproducible for running framework via jar file in the default mode (without > properties.prop file) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3901) Mesos deployment: IGNITE_PACKAGE_URL parameter don't work correctly
[ https://issues.apache.org/jira/browse/IGNITE-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasilisa Sidorova updated IGNITE-3901: --- Attachment: failed_task.png > Mesos deployment: IGNITE_PACKAGE_URL parameter don't work correctly > --- > > Key: IGNITE-3901 > URL: https://issues.apache.org/jira/browse/IGNITE-3901 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.6 > Environment: Ubuntu 14.04, Apache Ignite 1.6.7 >Reporter: Vasilisa Sidorova > Attachments: failed_task.png > > > - > DESCRIPTION > - > Mesos deployment failed if IGNITE_PACKAGE_URL is used (instead IGNITE_VERSION > or IGNITE_PACKAGE_PATH parameters) > - > STEPS FOR REPRODUCE > - > # Prepare marathon.json file for deployment through Marathon and set correct > IGNITE_PACKAGE_URL here > # Run framework according to instruction > https://apacheignite.readme.io/docs/mesos-deployment > - > ACTUAL RESULT > - > Ignition application is started but nodes couldn't be running as binaries is > not fully downloaded (look at the attached picture) > - > EXPECTED RESULT > - > Deployment is successful as for IGNITE_VERSION parameter > - > ADDITIONAL INFO > - > Reproducible for running framework via jar file in the default mode (without > properties.prop file) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3901) Mesos deployment: some Mesos parameters don't work correctly
Vasilisa Sidorova created IGNITE-3901: -- Summary: Mesos deployment: some Mesos parameters don't work correctly Key: IGNITE-3901 URL: https://issues.apache.org/jira/browse/IGNITE-3901 Project: Ignite Issue Type: Bug Components: general Affects Versions: 1.6 Environment: Ubuntu 14.04, Apache Ignite 1.6.7 Reporter: Vasilisa Sidorova - DESCRIPTION - Mesos deployment failed if IGNITE_PACKAGE_URL is used (instead IGNITE_VERSION or IGNITE_PACKAGE_PATH parameters) - STEPS FOR REPRODUCE - # Prepare marathon.json file for deployment through Marathon and set correct IGNITE_PACKAGE_URL here # Run framework according to instruction https://apacheignite.readme.io/docs/mesos-deployment - ACTUAL RESULT - Ignition application is started but nodes couldn't be running as binaries is not fully downloaded (look at the attached picture) - EXPECTED RESULT - Deployment is successful as for IGNITE_VERSION parameter - ADDITIONAL INFO - Reproducible for running framework via jar file in the default mode (without properties.prop file) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (IGNITE-3868) ODBC: DSN support for Windows works incorrectly
[
https://issues.apache.org/jira/browse/IGNITE-3868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova reopened IGNITE-3868:
First part is fixed - Apache Ignite DSN source is correctly added.
But second issue - connection to the cache from Tableau via DSN is still
reproducible. Please, look at this.
> ODBC: DSN support for Windows works incorrectly
> ---
>
> Key: IGNITE-3868
> URL: https://issues.apache.org/jira/browse/IGNITE-3868
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 1.7
> Environment: Win 8, Apache Ignite 1.6.7
>Reporter: Vasilisa Sidorova
>Assignee: Vasilisa Sidorova
> Labels: odbc
> Fix For: 1.8
>
>
> -
> DESCRIPTION
> -
> Some keys aren't registered in the registry during odbc driver installation
> and during DSN user data source adding:
> HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Apache Ignite\Setup
> HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\Apache Ignite
> DSN\{port,protocol_version}
> -
> STEPS FOR REPRODUCE
> -
> # Build and install odbc driver according to instruction from product binaries
> # Go to Control Panel\System and Security\Administrative Tools\ODBC Data
> Source Administrator (or run "odbcad32" command)
> # Try to add Apache Ignite DSN source
> -
> ACTUAL RESULT
> -
> Error message appear. Source isn't adding. There isn't
> HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Apache Ignite\Setup key in the
> registry
> -
> EXPECTED RESULT
> -
> Source is installed without any exception
> -
> NEXT STEPS FOR REPRODUCE
> -
> # Add HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Apache
> Ignite\Setup=[path_to_ignite_odbc_driver] into registry
> # Add Apache Ignite DSN source in the ODBC Data Source Administrator
> # Start some cache
> # Run Tableau
> # Try to connect to the cache using DSN
> -
> ACTUAL RESULT
> -
> Connection error message appears. There aren't
> HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\Apache Ignite
> DSN\{port,protocol_version} keys in the registry
> -
> EXPECTED RESULT
> -
> Connection is successful
> -
> ADDITIONAL INFO
> -
> Keys HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\Apache Ignite
> DSN\{port,protocol_version} are registered in the registry after user run
> "Configure" command (without any changes) for Apache Ignite DSN source
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-3868) ODBC: DSN support for Windows works incorrectly
[
https://issues.apache.org/jira/browse/IGNITE-3868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova reassigned IGNITE-3868:
--
Assignee: Vasilisa Sidorova (was: Vladimir Ozerov)
> ODBC: DSN support for Windows works incorrectly
> ---
>
> Key: IGNITE-3868
> URL: https://issues.apache.org/jira/browse/IGNITE-3868
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 1.7
> Environment: Win 8, Apache Ignite 1.6.7
>Reporter: Vasilisa Sidorova
>Assignee: Vasilisa Sidorova
> Labels: odbc
> Fix For: 1.8
>
>
> -
> DESCRIPTION
> -
> Some keys aren't registered in the registry during odbc driver installation
> and during DSN user data source adding:
> HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Apache Ignite\Setup
> HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\Apache Ignite
> DSN\{port,protocol_version}
> -
> STEPS FOR REPRODUCE
> -
> # Build and install odbc driver according to instruction from product binaries
> # Go to Control Panel\System and Security\Administrative Tools\ODBC Data
> Source Administrator (or run "odbcad32" command)
> # Try to add Apache Ignite DSN source
> -
> ACTUAL RESULT
> -
> Error message appear. Source isn't adding. There isn't
> HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Apache Ignite\Setup key in the
> registry
> -
> EXPECTED RESULT
> -
> Source is installed without any exception
> -
> NEXT STEPS FOR REPRODUCE
> -
> # Add HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Apache
> Ignite\Setup=[path_to_ignite_odbc_driver] into registry
> # Add Apache Ignite DSN source in the ODBC Data Source Administrator
> # Start some cache
> # Run Tableau
> # Try to connect to the cache using DSN
> -
> ACTUAL RESULT
> -
> Connection error message appears. There aren't
> HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\Apache Ignite
> DSN\{port,protocol_version} keys in the registry
> -
> EXPECTED RESULT
> -
> Connection is successful
> -
> ADDITIONAL INFO
> -
> Keys HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\Apache Ignite
> DSN\{port,protocol_version} are registered in the registry after user run
> "Configure" command (without any changes) for Apache Ignite DSN source
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3868) ODBC: DNS support for Windows works incorrectly
[
https://issues.apache.org/jira/browse/IGNITE-3868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3868:
---
Description:
-
DESCRIPTION
-
Some keys aren't registered in the registry during odbc driver installation and
during DSN user data source adding:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Apache Ignite\Setup
HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\Apache Ignite
DSN\{port,protocol_version}
-
STEPS FOR REPRODUCE
-
# Build and install odbc driver according to instruction from product binaries
# Go to Control Panel\System and Security\Administrative Tools\ODBC Data Source
Administrator (or run "odbcad32" command)
# Try to add Apache Ignite DSN source
-
ACTUAL RESULT
-
Error message appear. Source isn't adding. There isn't
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Apache Ignite\Setup key in the
registry
-
EXPECTED RESULT
-
Source is installed without any exception
-
NEXT STEPS FOR REPRODUCE
-
# Add HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Apache
Ignite\Setup=[path_to_ignite_odbc_driver] into registry
# Add Apache Ignite DSN source in the ODBC Data Source Administrator
# Start some cache
# Run Tableau
# Try to connect to the cache using DSN
-
ACTUAL RESULT
-
Connection error message appears. There aren't
HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\Apache Ignite
DSN\{port,protocol_version} keys in the registry
-
EXPECTED RESULT
-
Connection is successful
-
ADDITIONAL INFO
-
Keys HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\Apache Ignite
DSN\{port,protocol_version} are registered in the registry after user run
"Configure" command (without any changes) for Apache Ignite DSN source
was:
-
DESCRIPTION
-
Some keys aren't registered in the registry during odbc driver installation and
during DSN user data source adding:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Apache Ignite\Setup
HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\Apache Ignite
DSN\{port,protocol_version}
-
STEPS FOR REPRODUCE
-
# Build and install odbc driver according to instruction from product binaries
# Go to Control Panel\System and Security\Administrative Tools\ODBC Data Source
Administrator (or run "odbcad32" command)
# Try to add Apache Ignite DSN source
-
ACTUAL RESULT
-
Error message appear. Source isn't adding. There isn't
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Apache Ignite\Setup key in the
registry
-
EXPECTED RESULT
-
Source is installed without any exception
-
NEXT STEPS FOR REPRODUCE
-
# Add HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Apache
Ignite\Setup=[path_to_ignite_odbc_driver] into registry
# Add Apache Ignite DSN source in the ODBC Data Source Administrator
# Start some cache
# Run Tableau
# Try to connect to the cache using DSN
-
ACTUAL RESULT
-
Connection error message appear. There aren't
HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\Apache Ignite
DSN\{port,protocol_version} keys in the registry
-
EXPECTED RESULT
-
Connection is successful
-
ADDITIONAL INFO
-
Keys HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\Apache Ignite
DSN\{port,protocol_version} are registered in the registry after user run
"Configure" command (without any changes) for Apache Ignite DSN source
> ODBC: DNS support for Windows works incorrectly
> ---
>
> Key: IGNITE-3868
> URL: https://issues.apache.org/jira/browse/IGNITE-3868
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 1.6
> Environment: Win 8,
[jira] [Created] (IGNITE-3868) ODBC: DNS support for Windows works incorrectly
Vasilisa Sidorova created IGNITE-3868:
--
Summary: ODBC: DNS support for Windows works incorrectly
Key: IGNITE-3868
URL: https://issues.apache.org/jira/browse/IGNITE-3868
Project: Ignite
Issue Type: Bug
Components: odbc
Affects Versions: 1.6
Environment: Win 8, Apache Ignite 1.6.7
Reporter: Vasilisa Sidorova
-
DESCRIPTION
-
Some keys aren't registered in the registry during odbc driver installation and
during DSN user data source adding:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Apache Ignite\Setup
HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\Apache Ignite
DSN\{port,protocol_version}
-
STEPS FOR REPRODUCE
-
# Build and install odbc driver according to instruction from product binaries
# Go to Control Panel\System and Security\Administrative Tools\ODBC Data Source
Administrator (or run "odbcad32" command)
# Try to add Apache Ignite DSN source
-
ACTUAL RESULT
-
Error message appear. Source isn't adding. There isn't
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Apache Ignite\Setup key in the
registry
-
EXPECTED RESULT
-
Source is installed without any exception
-
NEXT STEPS FOR REPRODUCE
-
# Add HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Apache
Ignite\Setup=[path_to_ignite_odbc_driver] into registry
# Add Apache Ignite DSN source in the ODBC Data Source Administrator
# Start some cache
# Run Tableau
# Try to connect to the cache using DSN
-
ACTUAL RESULT
-
Connection error message appear. There aren't
HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\Apache Ignite
DSN\{port,protocol_version} keys in the registry
-
EXPECTED RESULT
-
Connection is successful
-
ADDITIONAL INFO
-
Keys HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\Apache Ignite
DSN\{port,protocol_version} are registered in the registry after user run
"Configure" command (without any changes) for Apache Ignite DSN source
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3861) ODBC: installer doesn't support path to driver with backspaces
[
https://issues.apache.org/jira/browse/IGNITE-3861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3861:
---
Environment: Win 8, odbc installer 1.6.7 (was: Win 7, odbc installer 1.6.7)
> ODBC: installer doesn't support path to driver with backspaces
> --
>
> Key: IGNITE-3861
> URL: https://issues.apache.org/jira/browse/IGNITE-3861
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 1.6
> Environment: Win 8, odbc installer 1.6.7
>Reporter: Vasilisa Sidorova
>
> -
> STEPS FOR REPRODUCE
> -
> # Build odbc driver according to instruction from
> $IGNITE_HOME/platforms/cpp/DEVNOTES.txt
> # Put driver into folder with path which contains backspaces
> # Install odbc driver according to instruction from
> $IGNITE_HOME/platforms/cpp/odbc/README.txt
> -
> ACTUAL RESULT
> -
> # Driver get error like this:
> {noformat}
> C:\ignite\platforms\cpp\odbc\install>install_x86.cmd "C:\Program
> Files\IgniteODBC\ignite.odbc.dll"
> warning: The path you have specified seems to be a directory. Note that you
> have to specify path to driver file itself instead.
> Installing driver: ""C:\Program Files\IgniteODBC\ignite.odbc.dll""
> The operation completed successfully.
> The operation completed successfully.
> ERROR: Invalid syntax.
> Type "REG ADD /?" for usage.
> The operation completed successfully.
> Driver can not be found: ""C:\Program Files\IgniteODBC\ignite.odbc.dll""
> Call format: install_x86 abs_path_to_driver
> Press any key to continue . . .
> {noformat}
> # Driver isn't installed
> -
> EXPECTED RESULT
> -
> Driver is installed without any exceptions or should give correct and clear
> error string
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3861) ODBC: installer doesn't support path to driver with backspaces
Vasilisa Sidorova created IGNITE-3861:
--
Summary: ODBC: installer doesn't support path to driver with
backspaces
Key: IGNITE-3861
URL: https://issues.apache.org/jira/browse/IGNITE-3861
Project: Ignite
Issue Type: Bug
Components: odbc
Affects Versions: 1.6
Environment: Win 7, odbc installer 1.6.7
Reporter: Vasilisa Sidorova
-
STEPS FOR REPRODUCE
-
# Build odbc driver according to instruction from
$IGNITE_HOME/platforms/cpp/DEVNOTES.txt
# Put driver into folder with path which contains backspaces
# Install odbc driver according to instruction from
$IGNITE_HOME/platforms/cpp/odbc/README.txt
-
ACTUAL RESULT
-
# Driver get error like this:
{noformat}
C:\ignite\platforms\cpp\odbc\install>install_x86.cmd "C:\Program
Files\IgniteODBC\ignite.odbc.dll"
warning: The path you have specified seems to be a directory. Note that you
have to specify path to driver file itself instead.
Installing driver: ""C:\Program Files\IgniteODBC\ignite.odbc.dll""
The operation completed successfully.
The operation completed successfully.
ERROR: Invalid syntax.
Type "REG ADD /?" for usage.
The operation completed successfully.
Driver can not be found: ""C:\Program Files\IgniteODBC\ignite.odbc.dll""
Call format: install_x86 abs_path_to_driver
Press any key to continue . . .
{noformat}
# Driver isn't installed
-
EXPECTED RESULT
-
Driver is installed without any exceptions or should give correct and clear
error string
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3387) NPE deploy ignite with mesos
[
https://issues.apache.org/jira/browse/IGNITE-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446457#comment-15446457
]
Vasilisa Sidorova edited comment on IGNITE-3387 at 8/29/16 6:40 PM:
-
Ilya, this exception happens due to application couldn't download ignite
version 6.6.6.
It can download only released versions which is in the Apache repository.
For download not public version you should use "IGNITE_PACKAGE_URL" instead
IGNITE_VERSION parameter. So, I think this issue should be closed.
was (Author: vsidorova):
Ilya, this exception happens due to application couldn't download ignite
version 6.6.6.
It can download only released versions which is in the Apache repository.
For download not public version you should use "IGNITE_PACKAGE_URL" instead
IGNITE_VERSION parameter. So, I think this issue could be closed.
> NPE deploy ignite with mesos
>
>
> Key: IGNITE-3387
> URL: https://issues.apache.org/jira/browse/IGNITE-3387
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.7
>Reporter: Ilya Suntsov
> Fix For: 1.8
>
>
> I tried to use marathon to deploy ignite with mesos:
> {noformat}
> curl -X POST -H "Content-type: application/json" --data-binary @marathon.json
> http://192.168.2.106:8080/v2/apps/
> {noformat}
> where marathon.json contains:
> {noformat}
> "id": "ignition",
> "instances": 1,
> "cpus": 1,
> "mem": 512,
> "ports": [0],
> "uris": [
> "https://s3-us-west-2.amazonaws.com/mesos-1234/ignite-mesos-1.6.0.jar;
> ],
> "env": {
> "IGNITE_NODE_COUNT": "4",
> "MESOS_MASTER_URL": "zk://192.168.2.106:2181/mesos",
> "IGNITE_RUN_CPU_PER_NODE": "2",
> "IGNITE_MEMORY_PER_NODE": "2048",
> "IGNITE_VERSION":"6.6.6"
> },
> "cmd": "java -jar ignite-mesos-1.6.0.jar"
> {noformat}
> and got the following exception caused by wrong ignite version from
> marathon.json:
> {noformat}
> Exception in thread "Thread-11" java.lang.NullPointerException
> at
> org.apache.mesos.Protos$CommandInfo$URI$Builder.setValue(Protos.java:8069)
> at
> org.apache.ignite.mesos.IgniteScheduler.createTask(IgniteScheduler.java:128)
> at
> org.apache.ignite.mesos.IgniteScheduler.resourceOffers(IgniteScheduler.java:98)
> {noformat}
> I think we should return another exception/error to be clear what happened.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3387) NPE deploy ignite with mesos
[
https://issues.apache.org/jira/browse/IGNITE-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446457#comment-15446457
]
Vasilisa Sidorova edited comment on IGNITE-3387 at 8/29/16 5:29 PM:
-
Ilya, this exception happens due to application couldn't download ignite
version 6.6.6.
It can download only released versions which is in the Apache repository.
For download not public version you should use "IGNITE_PACKAGE_URL" instead
IGNITE_VERSION parameter. So, I think this issue could be closed.
was (Author: vsidorova):
Ilya, this exception happens due to application couldn't download ignite
version 6.6.6.
It can download only released versions which is in the Apache repository.
For download not public version you should use "IGNITE_URL_PATH" instead
IGNITE_VERSION parameter. So, I think this issue could be closed.
> NPE deploy ignite with mesos
>
>
> Key: IGNITE-3387
> URL: https://issues.apache.org/jira/browse/IGNITE-3387
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.7
>Reporter: Ilya Suntsov
> Fix For: 1.8
>
>
> I tried to use marathon to deploy ignite with mesos:
> {noformat}
> curl -X POST -H "Content-type: application/json" --data-binary @marathon.json
> http://192.168.2.106:8080/v2/apps/
> {noformat}
> where marathon.json contains:
> {noformat}
> "id": "ignition",
> "instances": 1,
> "cpus": 1,
> "mem": 512,
> "ports": [0],
> "uris": [
> "https://s3-us-west-2.amazonaws.com/mesos-1234/ignite-mesos-1.6.0.jar;
> ],
> "env": {
> "IGNITE_NODE_COUNT": "4",
> "MESOS_MASTER_URL": "zk://192.168.2.106:2181/mesos",
> "IGNITE_RUN_CPU_PER_NODE": "2",
> "IGNITE_MEMORY_PER_NODE": "2048",
> "IGNITE_VERSION":"6.6.6"
> },
> "cmd": "java -jar ignite-mesos-1.6.0.jar"
> {noformat}
> and got the following exception caused by wrong ignite version from
> marathon.json:
> {noformat}
> Exception in thread "Thread-11" java.lang.NullPointerException
> at
> org.apache.mesos.Protos$CommandInfo$URI$Builder.setValue(Protos.java:8069)
> at
> org.apache.ignite.mesos.IgniteScheduler.createTask(IgniteScheduler.java:128)
> at
> org.apache.ignite.mesos.IgniteScheduler.resourceOffers(IgniteScheduler.java:98)
> {noformat}
> I think we should return another exception/error to be clear what happened.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-2862) Deployment Ignite in Mesos cluster is failed
[
https://issues.apache.org/jira/browse/IGNITE-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova resolved IGNITE-2862.
Resolution: Cannot Reproduce
Couldn't reproduce it for Apache Ignite 1.7.0
> Deployment Ignite in Mesos cluster is failed
>
>
> Key: IGNITE-2862
> URL: https://issues.apache.org/jira/browse/IGNITE-2862
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.5.0.final
>Reporter: Vasilisa Sidorova
> Attachments: marathon.json, mesos_activetasks.png, mesos_logs.png
>
>
> -
> DESCRIPTION
> -
> Deployment Ignite in Mesos cluster by this instruction
> https://apacheignite.readme.io/docs/mesos-deployment is failed
> -
> STEPS FOR REPRODUCE
> -
> # Do items 1-5 from "RUN THE FRAMEWORK VIA MARATHON" paragraph
> -
> ACTUAL RESULT
> -
> # Ignite nodes didn't start. Only ignition task is running. Look at the
> attached picture "mesos_activetasks.png"
> # Stderr log for ignition task get follow exception:
> {noformat}
> I0318 18:42:08.252142 17138 fetcher.cpp:409] Fetcher Info:
> {"cache_directory":"\/tmp\/mesos\/fetch\/slaves\/20160318-180241-16777343-5050-16554-S0\/root","items":[{"action":"BYPASS_CACHE","uri":{"extract":false,"value":"https:\/\/s3.amazonaws.com\/vasilisk\/m\/ignite-mesos-1.5.0.final.jar"}}],"sandbox_directory":"\/tmp\/mesos\/slaves\/20160318-180241-16777343-5050-16554-S0\/frameworks\/20150603-121744-16842879-5050-6241-\/executors\/ignition.f8fa2435-ed1f-11e5-bea1-0242e00dbbdd\/runs\/776db62f-965f-4e9e-950a-4edb67c44667","user":"root"}
> I0318 18:42:08.253284 17138 fetcher.cpp:364] Fetching URI
> 'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar'
> I0318 18:42:08.253298 17138 fetcher.cpp:238] Fetching directly into the
> sandbox directory
> I0318 18:42:08.253312 17138 fetcher.cpp:176] Fetching URI
> 'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar'
> I0318 18:42:08.253325 17138 fetcher.cpp:126] Downloading resource from
> 'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar' to
> '/tmp/mesos/slaves/20160318-180241-16777343-5050-16554-S0/frameworks/20150603-121744-16842879-5050-6241-/executors/ignition.f8fa2435-ed1f-11e5-bea1-0242e00dbbdd/runs/776db62f-965f-4e9e-950a-4edb67c44667/ignite-mesos-1.5.0.final.jar'
> I0318 18:42:12.091784 17138 fetcher.cpp:441] Fetched
> 'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar' to
> '/tmp/mesos/slaves/20160318-180241-16777343-5050-16554-S0/frameworks/20150603-121744-16842879-5050-6241-/executors/ignition.f8fa2435-ed1f-11e5-bea1-0242e00dbbdd/runs/776db62f-965f-4e9e-950a-4edb67c44667/ignite-mesos-1.5.0.final.jar'
> I0318 18:42:12.293658 17142 exec.cpp:132] Version: 0.23.0
> I0318 18:42:12.296212 17145 exec.cpp:206] Executor registered on slave
> 20160318-180241-16777343-5050-16554-S0
> Mar 18, 2016 6:42:12 PM org.apache.ignite.mesos.IgniteFramework main
> INFO: Enabling checkpoint for the framework
> 2016-03-18 18:42:12.495:INFO::main: Logging initialized @151ms
> 2016-03-18 18:42:22.542:INFO:oejs.Server:main: jetty-9.2.z-SNAPSHOT
> 2016-03-18 18:42:22.579:INFO:oejs.ServerConnector:main: Started
> ServerConnector@1268c278{HTTP/1.1}{172.17.0.1:48610}
> 2016-03-18 18:42:22.580:INFO:oejs.Server:main: Started @10235ms
> Exception in thread "main" java.lang.RuntimeException: Got unexpected
> response code. Response code: 404
> at
> org.apache.ignite.mesos.resource.IgniteProvider.downloadIgnite(IgniteProvider.java:202)
> at
> org.apache.ignite.mesos.resource.IgniteProvider.getIgnite(IgniteProvider.java:132)
> at
> org.apache.ignite.mesos.resource.ResourceProvider.init(ResourceProvider.java:57)
> at org.apache.ignite.mesos.IgniteFramework.main(IgniteFramework.java:77)
> {noformat}
> -
> EXPECTED RESULT
> -
> Tasks for all 3 nodes are running with ignition task.
> -
> ADDITIONAL INFO
> -
> # File "marathon.json" is attached
> # The same exception gets after run framework via jar file
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-2862) Deployment Ignite in Mesos cluster is failed
[
https://issues.apache.org/jira/browse/IGNITE-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova closed IGNITE-2862.
--
> Deployment Ignite in Mesos cluster is failed
>
>
> Key: IGNITE-2862
> URL: https://issues.apache.org/jira/browse/IGNITE-2862
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.5.0.final
>Reporter: Vasilisa Sidorova
> Attachments: marathon.json, mesos_activetasks.png, mesos_logs.png
>
>
> -
> DESCRIPTION
> -
> Deployment Ignite in Mesos cluster by this instruction
> https://apacheignite.readme.io/docs/mesos-deployment is failed
> -
> STEPS FOR REPRODUCE
> -
> # Do items 1-5 from "RUN THE FRAMEWORK VIA MARATHON" paragraph
> -
> ACTUAL RESULT
> -
> # Ignite nodes didn't start. Only ignition task is running. Look at the
> attached picture "mesos_activetasks.png"
> # Stderr log for ignition task get follow exception:
> {noformat}
> I0318 18:42:08.252142 17138 fetcher.cpp:409] Fetcher Info:
> {"cache_directory":"\/tmp\/mesos\/fetch\/slaves\/20160318-180241-16777343-5050-16554-S0\/root","items":[{"action":"BYPASS_CACHE","uri":{"extract":false,"value":"https:\/\/s3.amazonaws.com\/vasilisk\/m\/ignite-mesos-1.5.0.final.jar"}}],"sandbox_directory":"\/tmp\/mesos\/slaves\/20160318-180241-16777343-5050-16554-S0\/frameworks\/20150603-121744-16842879-5050-6241-\/executors\/ignition.f8fa2435-ed1f-11e5-bea1-0242e00dbbdd\/runs\/776db62f-965f-4e9e-950a-4edb67c44667","user":"root"}
> I0318 18:42:08.253284 17138 fetcher.cpp:364] Fetching URI
> 'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar'
> I0318 18:42:08.253298 17138 fetcher.cpp:238] Fetching directly into the
> sandbox directory
> I0318 18:42:08.253312 17138 fetcher.cpp:176] Fetching URI
> 'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar'
> I0318 18:42:08.253325 17138 fetcher.cpp:126] Downloading resource from
> 'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar' to
> '/tmp/mesos/slaves/20160318-180241-16777343-5050-16554-S0/frameworks/20150603-121744-16842879-5050-6241-/executors/ignition.f8fa2435-ed1f-11e5-bea1-0242e00dbbdd/runs/776db62f-965f-4e9e-950a-4edb67c44667/ignite-mesos-1.5.0.final.jar'
> I0318 18:42:12.091784 17138 fetcher.cpp:441] Fetched
> 'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar' to
> '/tmp/mesos/slaves/20160318-180241-16777343-5050-16554-S0/frameworks/20150603-121744-16842879-5050-6241-/executors/ignition.f8fa2435-ed1f-11e5-bea1-0242e00dbbdd/runs/776db62f-965f-4e9e-950a-4edb67c44667/ignite-mesos-1.5.0.final.jar'
> I0318 18:42:12.293658 17142 exec.cpp:132] Version: 0.23.0
> I0318 18:42:12.296212 17145 exec.cpp:206] Executor registered on slave
> 20160318-180241-16777343-5050-16554-S0
> Mar 18, 2016 6:42:12 PM org.apache.ignite.mesos.IgniteFramework main
> INFO: Enabling checkpoint for the framework
> 2016-03-18 18:42:12.495:INFO::main: Logging initialized @151ms
> 2016-03-18 18:42:22.542:INFO:oejs.Server:main: jetty-9.2.z-SNAPSHOT
> 2016-03-18 18:42:22.579:INFO:oejs.ServerConnector:main: Started
> ServerConnector@1268c278{HTTP/1.1}{172.17.0.1:48610}
> 2016-03-18 18:42:22.580:INFO:oejs.Server:main: Started @10235ms
> Exception in thread "main" java.lang.RuntimeException: Got unexpected
> response code. Response code: 404
> at
> org.apache.ignite.mesos.resource.IgniteProvider.downloadIgnite(IgniteProvider.java:202)
> at
> org.apache.ignite.mesos.resource.IgniteProvider.getIgnite(IgniteProvider.java:132)
> at
> org.apache.ignite.mesos.resource.ResourceProvider.init(ResourceProvider.java:57)
> at org.apache.ignite.mesos.IgniteFramework.main(IgniteFramework.java:77)
> {noformat}
> -
> EXPECTED RESULT
> -
> Tasks for all 3 nodes are running with ignition task.
> -
> ADDITIONAL INFO
> -
> # File "marathon.json" is attached
> # The same exception gets after run framework via jar file
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3387) NPE deploy ignite with mesos
[
https://issues.apache.org/jira/browse/IGNITE-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446457#comment-15446457
]
Vasilisa Sidorova edited comment on IGNITE-3387 at 8/29/16 5:25 PM:
-
Ilya, this exception happens due to application couldn't download ignite
version 6.6.6.
It can download only released versions which is in the Apache repository.
For download not public version you should use "IGNITE_URL_PATH" instead
IGNITE_VERSION parameter. So, I think this issue could be closed.
was (Author: vsidorova):
Ilya, this exception happens due to application couldn't download ignite
version 6.6.6.
It can download only versions which is in the Apache repository.
For download not public version you should use "IGNITE_URL_PATH" instead
IGNITE_VERSION parameter. So, I think this issue could be closed.
> NPE deploy ignite with mesos
>
>
> Key: IGNITE-3387
> URL: https://issues.apache.org/jira/browse/IGNITE-3387
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.7
>Reporter: Ilya Suntsov
> Fix For: 1.8
>
>
> I tried to use marathon to deploy ignite with mesos:
> {noformat}
> curl -X POST -H "Content-type: application/json" --data-binary @marathon.json
> http://192.168.2.106:8080/v2/apps/
> {noformat}
> where marathon.json contains:
> {noformat}
> "id": "ignition",
> "instances": 1,
> "cpus": 1,
> "mem": 512,
> "ports": [0],
> "uris": [
> "https://s3-us-west-2.amazonaws.com/mesos-1234/ignite-mesos-1.6.0.jar;
> ],
> "env": {
> "IGNITE_NODE_COUNT": "4",
> "MESOS_MASTER_URL": "zk://192.168.2.106:2181/mesos",
> "IGNITE_RUN_CPU_PER_NODE": "2",
> "IGNITE_MEMORY_PER_NODE": "2048",
> "IGNITE_VERSION":"6.6.6"
> },
> "cmd": "java -jar ignite-mesos-1.6.0.jar"
> {noformat}
> and got the following exception caused by wrong ignite version from
> marathon.json:
> {noformat}
> Exception in thread "Thread-11" java.lang.NullPointerException
> at
> org.apache.mesos.Protos$CommandInfo$URI$Builder.setValue(Protos.java:8069)
> at
> org.apache.ignite.mesos.IgniteScheduler.createTask(IgniteScheduler.java:128)
> at
> org.apache.ignite.mesos.IgniteScheduler.resourceOffers(IgniteScheduler.java:98)
> {noformat}
> I think we should return another exception/error to be clear what happened.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3387) NPE deploy ignite with mesos
[
https://issues.apache.org/jira/browse/IGNITE-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446457#comment-15446457
]
Vasilisa Sidorova edited comment on IGNITE-3387 at 8/29/16 5:24 PM:
-
Ilya, this exception happens due to application couldn't download ignite
version 6.6.6.
It can download only versions which is in the Apache repository.
For download not public version you should use "IGNITE_URL_PATH" instead
IGNITE_VERSION parameter. So, I think this issue could be closed.
was (Author: vsidorova):
Ilya, this exception happens due to application couldn't download ignite
version 6.6.6.
It can download only versions which is in the Apache repository.
For download not public version you should use "IGNITE_URL_PATH" parameter. So,
I think this issue could be closed.
> NPE deploy ignite with mesos
>
>
> Key: IGNITE-3387
> URL: https://issues.apache.org/jira/browse/IGNITE-3387
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.7
>Reporter: Ilya Suntsov
> Fix For: 1.8
>
>
> I tried to use marathon to deploy ignite with mesos:
> {noformat}
> curl -X POST -H "Content-type: application/json" --data-binary @marathon.json
> http://192.168.2.106:8080/v2/apps/
> {noformat}
> where marathon.json contains:
> {noformat}
> "id": "ignition",
> "instances": 1,
> "cpus": 1,
> "mem": 512,
> "ports": [0],
> "uris": [
> "https://s3-us-west-2.amazonaws.com/mesos-1234/ignite-mesos-1.6.0.jar;
> ],
> "env": {
> "IGNITE_NODE_COUNT": "4",
> "MESOS_MASTER_URL": "zk://192.168.2.106:2181/mesos",
> "IGNITE_RUN_CPU_PER_NODE": "2",
> "IGNITE_MEMORY_PER_NODE": "2048",
> "IGNITE_VERSION":"6.6.6"
> },
> "cmd": "java -jar ignite-mesos-1.6.0.jar"
> {noformat}
> and got the following exception caused by wrong ignite version from
> marathon.json:
> {noformat}
> Exception in thread "Thread-11" java.lang.NullPointerException
> at
> org.apache.mesos.Protos$CommandInfo$URI$Builder.setValue(Protos.java:8069)
> at
> org.apache.ignite.mesos.IgniteScheduler.createTask(IgniteScheduler.java:128)
> at
> org.apache.ignite.mesos.IgniteScheduler.resourceOffers(IgniteScheduler.java:98)
> {noformat}
> I think we should return another exception/error to be clear what happened.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-3387) NPE deploy ignite with mesos
[
https://issues.apache.org/jira/browse/IGNITE-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446457#comment-15446457
]
Vasilisa Sidorova edited comment on IGNITE-3387 at 8/29/16 5:24 PM:
-
Ilya, this exception happens due to application couldn't download ignite
version 6.6.6.
It can download only versions which is in the Apache repository.
For download not public version you should use "IGNITE_URL_PATH" parameter. So,
I think this issue could be closed.
was (Author: vsidorova):
Ilya, this exception happens due to application couldn't download ignite
version 6.6.6.
It can download only versions which is in the Apache repository.
Or you can use "IGNITE_URL" parameter, but it doesn't work properly now.:) So,
I think this issue could be closed.
> NPE deploy ignite with mesos
>
>
> Key: IGNITE-3387
> URL: https://issues.apache.org/jira/browse/IGNITE-3387
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.7
>Reporter: Ilya Suntsov
> Fix For: 1.8
>
>
> I tried to use marathon to deploy ignite with mesos:
> {noformat}
> curl -X POST -H "Content-type: application/json" --data-binary @marathon.json
> http://192.168.2.106:8080/v2/apps/
> {noformat}
> where marathon.json contains:
> {noformat}
> "id": "ignition",
> "instances": 1,
> "cpus": 1,
> "mem": 512,
> "ports": [0],
> "uris": [
> "https://s3-us-west-2.amazonaws.com/mesos-1234/ignite-mesos-1.6.0.jar;
> ],
> "env": {
> "IGNITE_NODE_COUNT": "4",
> "MESOS_MASTER_URL": "zk://192.168.2.106:2181/mesos",
> "IGNITE_RUN_CPU_PER_NODE": "2",
> "IGNITE_MEMORY_PER_NODE": "2048",
> "IGNITE_VERSION":"6.6.6"
> },
> "cmd": "java -jar ignite-mesos-1.6.0.jar"
> {noformat}
> and got the following exception caused by wrong ignite version from
> marathon.json:
> {noformat}
> Exception in thread "Thread-11" java.lang.NullPointerException
> at
> org.apache.mesos.Protos$CommandInfo$URI$Builder.setValue(Protos.java:8069)
> at
> org.apache.ignite.mesos.IgniteScheduler.createTask(IgniteScheduler.java:128)
> at
> org.apache.ignite.mesos.IgniteScheduler.resourceOffers(IgniteScheduler.java:98)
> {noformat}
> I think we should return another exception/error to be clear what happened.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3387) NPE deploy ignite with mesos
[
https://issues.apache.org/jira/browse/IGNITE-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446457#comment-15446457
]
Vasilisa Sidorova commented on IGNITE-3387:
Ilya, this exception happens due to application couldn't download ignite
version 6.6.6.
It can download only versions which is in the Apache repository.
Or you can use "IGNITE_URL" parameter, but it doesn't work properly now.:) So,
I think this issue could be closed.
> NPE deploy ignite with mesos
>
>
> Key: IGNITE-3387
> URL: https://issues.apache.org/jira/browse/IGNITE-3387
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.7
>Reporter: Ilya Suntsov
> Fix For: 1.8
>
>
> I tried to use marathon to deploy ignite with mesos:
> {noformat}
> curl -X POST -H "Content-type: application/json" --data-binary @marathon.json
> http://192.168.2.106:8080/v2/apps/
> {noformat}
> where marathon.json contains:
> {noformat}
> "id": "ignition",
> "instances": 1,
> "cpus": 1,
> "mem": 512,
> "ports": [0],
> "uris": [
> "https://s3-us-west-2.amazonaws.com/mesos-1234/ignite-mesos-1.6.0.jar;
> ],
> "env": {
> "IGNITE_NODE_COUNT": "4",
> "MESOS_MASTER_URL": "zk://192.168.2.106:2181/mesos",
> "IGNITE_RUN_CPU_PER_NODE": "2",
> "IGNITE_MEMORY_PER_NODE": "2048",
> "IGNITE_VERSION":"6.6.6"
> },
> "cmd": "java -jar ignite-mesos-1.6.0.jar"
> {noformat}
> and got the following exception caused by wrong ignite version from
> marathon.json:
> {noformat}
> Exception in thread "Thread-11" java.lang.NullPointerException
> at
> org.apache.mesos.Protos$CommandInfo$URI$Builder.setValue(Protos.java:8069)
> at
> org.apache.ignite.mesos.IgniteScheduler.createTask(IgniteScheduler.java:128)
> at
> org.apache.ignite.mesos.IgniteScheduler.resourceOffers(IgniteScheduler.java:98)
> {noformat}
> I think we should return another exception/error to be clear what happened.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-3279) .NET: NLog integration
[
https://issues.apache.org/jira/browse/IGNITE-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova closed IGNITE-3279.
--
Verified for master 1.8
> .NET: NLog integration
> --
>
> Key: IGNITE-3279
> URL: https://issues.apache.org/jira/browse/IGNITE-3279
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Vasilisa Sidorova
> Labels: .net, roadmap
> Fix For: 1.8
>
>
> Provide NLog implementation for {code}Apache.Ignite.Core.Log.ILogger{code}
> Should be in a separate assembly/nuget.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-3279) .NET: NLog integration
[
https://issues.apache.org/jira/browse/IGNITE-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova reassigned IGNITE-3279:
--
Assignee: (was: Vasilisa Sidorova)
> .NET: NLog integration
> --
>
> Key: IGNITE-3279
> URL: https://issues.apache.org/jira/browse/IGNITE-3279
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
> Labels: .net, roadmap
> Fix For: 1.8
>
>
> Provide NLog implementation for {code}Apache.Ignite.Core.Log.ILogger{code}
> Should be in a separate assembly/nuget.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-3404) Single cpp node doesn't build during Apache Ignite C++ Build on Linux
[
https://issues.apache.org/jira/browse/IGNITE-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova reassigned IGNITE-3404:
--
Assignee: (was: Vasilisa Sidorova)
> Single cpp node doesn't build during Apache Ignite C++ Build on Linux
> -
>
> Key: IGNITE-3404
> URL: https://issues.apache.org/jira/browse/IGNITE-3404
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.6
> Environment: Ubuntu 14.04
>Reporter: Vasilisa Sidorova
>
> -
> DESCRIPTION
> -
> Single cpp node doesn't build during Apache Ignite C++ Build on Linux
> -
> STEPS FOR REPRODUCE
> -
> # Build Apache Ignite C++ Build according to instruction from
> platforms/cpp/DEVNOTES.txt:
> {noformat}
> Building the Apache Ignite C++ components:
> * Navigate to the directory $IGNITE_HOME/platforms/cpp
> * Execute the following commands one by one to build the project:
> * libtoolize && aclocal && autoheader && automake --add-missing &&
> autoreconf
> * ./configure
> * make
> {noformat}
> -
> EXPECTED RESULT
> -
> There is ignite binary in the cpp/ignite folder
> -
> ACTUAL RESULT
> -
> There isn't ignite binary in cpp/ignite folder after building
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-3279) .NET: NLog integration
[
https://issues.apache.org/jira/browse/IGNITE-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova reassigned IGNITE-3279:
--
Assignee: Vasilisa Sidorova (was: Pavel Tupitsyn)
> .NET: NLog integration
> --
>
> Key: IGNITE-3279
> URL: https://issues.apache.org/jira/browse/IGNITE-3279
> Project: Ignite
> Issue Type: New Feature
> Components: platforms
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Vasilisa Sidorova
> Labels: .net, roadmap
> Fix For: 1.8
>
>
> Provide NLog implementation for {code}Apache.Ignite.Core.Log.ILogger{code}
> Should be in a separate assembly/nuget.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3444) Documentation for odbc-example should be updated
[
https://issues.apache.org/jira/browse/IGNITE-3444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3444:
---
Description:
-
DESCRIPTION
-
# After user Install ignite odbc driver according to
platforms\cpp\odbc\README.txt he/she should add directories with
libignite-odbc.so to the LD_LIBRARY_PATH (this information is in
platforms\cpp\odbc\README.txt - it's OK). As a rule, it will be done once
# After that user can build and run odbc-example and this action could happens
many times and this can be done much later after driver installation
# Therefore LD_LIBRARY_PATH could be reseted and it will not be enough the
platforms/cpp/examples/README.txt for odbc-example running
-
PROPOSAL
-
Add information about adding path to libignite-odbc.so to the LD_LIBRARY_PATH
into "Running examples on Linux" part of the platforms/cpp/examples/README.txt
For example, this text:
{noformat}
* Make sure path to libignite-odbc.so is added to LD_LIBRARY_PATH (usually it
is /usr/local/lib)
{noformat}
was:
-
DESCRIPTION
-
# After user Install ignite odbc driver according to
platforms\cpp\odbc\README.txt he/she should add directories with
libignite-odbc.so to the LD_LIBRARY_PATH (this information is in
platforms\cpp\odbc\README.txt - it's OK). As a rule, it will be done once
# After that user can build and run odbc-example and this action could happens
many times and this can be done much later after driver installation
# Therefore LD_LIBRARY_PATH could be reseted and it will not be enough the
platforms/cpp/examples/README.txt for odbc-example running
-
PROPOSAL
-
Add information about adding path to libignite-odbc.so to the LD_LIBRARY_PATH
into "Running examples on Linux" part of the platforms/cpp/examples/README.txt
For example, this text:
{noformat}
* Make sure path to libignite-odbc.so is added to LD_LIBRARY_PATH (usually it
is /usr/local/lib)
{noformat}
> Documentation for odbc-example should be updated
>
>
> Key: IGNITE-3444
> URL: https://issues.apache.org/jira/browse/IGNITE-3444
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 1.6
>Reporter: Vasilisa Sidorova
>Priority: Minor
>
> -
> DESCRIPTION
> -
> # After user Install ignite odbc driver according to
> platforms\cpp\odbc\README.txt he/she should add directories with
> libignite-odbc.so to the LD_LIBRARY_PATH (this information is in
> platforms\cpp\odbc\README.txt - it's OK). As a rule, it will be done once
> # After that user can build and run odbc-example and this action could
> happens many times and this can be done much later after driver installation
> # Therefore LD_LIBRARY_PATH could be reseted and it will not be enough the
> platforms/cpp/examples/README.txt for odbc-example running
> -
> PROPOSAL
> -
> Add information about adding path to libignite-odbc.so to the
> LD_LIBRARY_PATH into "Running examples on Linux" part of the
> platforms/cpp/examples/README.txt
> For example, this text:
> {noformat}
> * Make sure path to libignite-odbc.so is added to LD_LIBRARY_PATH (usually it
> is /usr/local/lib)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3444) Documentation for odbc-example should be updated
Vasilisa Sidorova created IGNITE-3444:
--
Summary: Documentation for odbc-example should be updated
Key: IGNITE-3444
URL: https://issues.apache.org/jira/browse/IGNITE-3444
Project: Ignite
Issue Type: Bug
Components: odbc
Affects Versions: 1.6
Reporter: Vasilisa Sidorova
Priority: Minor
-
DESCRIPTION
-
# After user Install ignite odbc driver according to
platforms\cpp\odbc\README.txt he/she should add directories with
libignite-odbc.so to the LD_LIBRARY_PATH (this information is in
platforms\cpp\odbc\README.txt - it's OK). As a rule, it will be done once
# After that user can build and run odbc-example and this action could happens
many times and this can be done much later after driver installation
# Therefore LD_LIBRARY_PATH could be reseted and it will not be enough the
platforms/cpp/examples/README.txt for odbc-example running
-
PROPOSAL
-
Add information about adding path to libignite-odbc.so to the LD_LIBRARY_PATH
into "Running examples on Linux" part of the platforms/cpp/examples/README.txt
For example, this text:
{noformat}
* Make sure path to libignite-odbc.so is added to LD_LIBRARY_PATH (usually it
is /usr/local/lib)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3404) Single cpp node doesn't build during Apache Ignite C++ Build on Linux
Vasilisa Sidorova created IGNITE-3404:
--
Summary: Single cpp node doesn't build during Apache Ignite C++
Build on Linux
Key: IGNITE-3404
URL: https://issues.apache.org/jira/browse/IGNITE-3404
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 1.6
Environment: Ubuntu 14.04
Reporter: Vasilisa Sidorova
-
DESCRIPTION
-
Single cpp node doesn't build during Apache Ignite C++ Build on Linux
-
STEPS FOR REPRODUCE
-
# Build Apache Ignite C++ Build according to instruction from
platforms/cpp/DEVNOTES.txt:
{noformat}
Building the Apache Ignite C++ components:
* Navigate to the directory $IGNITE_HOME/platforms/cpp
* Execute the following commands one by one to build the project:
* libtoolize && aclocal && autoheader && automake --add-missing &&
autoreconf
* ./configure
* make
{noformat}
-
ACTUAL RESULT
-
There is ignite.sh in the cpp/ignite folder
-
EXPECTED RESULT
-
There isn't cpp/ignite folder after building
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-3318) Web console: schema name must be unique for each cache
[ https://issues.apache.org/jira/browse/IGNITE-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasilisa Sidorova reassigned IGNITE-3318: -- Assignee: Vasiliy Sisko (was: Vasilisa Sidorova) It is not user-friendly to reset schema name during cloning without any warning. Is it possible to add message like this: "Found cache "blablabla" in cluster "blablabla" with the same SQL schema name "blablabla". SQL schema name will be reseted"? If it is easier for you make the same message during cache saving (action: reset Schema name after this warning and after saving user could write new name) > Web console: schema name must be unique for each cache > -- > > Key: IGNITE-3318 > URL: https://issues.apache.org/jira/browse/IGNITE-3318 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.7 >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko > Fix For: 1.7 > > > Currently we don't check that schema name is unique. > Just clone cache with schema name ans Save. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-3297) Pipe chart is empty in special case.
[ https://issues.apache.org/jira/browse/IGNITE-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasilisa Sidorova reassigned IGNITE-3297: -- Assignee: (was: Pavel Konstantinov) > Pipe chart is empty in special case. > > > Key: IGNITE-3297 > URL: https://issues.apache.org/jira/browse/IGNITE-3297 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.7 >Reporter: Vasiliy Sisko > Fix For: 1.7 > > > # Execute query where column A and B have the same values in all rows. > # Build Pipe chart where A and B columns set as X and Y columns. > Showed legend for chart but chart area is empty. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (IGNITE-3318) Web console: schema name must be unique for each cache
[ https://issues.apache.org/jira/browse/IGNITE-3318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasilisa Sidorova reopened IGNITE-3318: Assignee: (was: Pavel Konstantinov) It works not good now: during clone cache with schema name only new cache name is proposed. After user click "Confirm" the "Save" button is disabled for new (cloned) cache. So at this moment we have two similar schema name. The cache SQL schema name checking will activate only after user make some changes and try to save cache. > Web console: schema name must be unique for each cache > -- > > Key: IGNITE-3318 > URL: https://issues.apache.org/jira/browse/IGNITE-3318 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.7 >Reporter: Pavel Konstantinov > Fix For: 1.7 > > > Currently we don't check that schema name is unique. > Just clone cache with schema name ans Save. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3344) Couldn't import Ignite Image to Google Compute
[
https://issues.apache.org/jira/browse/IGNITE-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3344:
---
Description:
-
DESCRIPTION
-
Couldn't run Ignite docker container on the Google Compute due to missing
ignite-google-image-1.0.0.tar.gz file
-
STEPS FOR REPRODUCE
-
# In accordance with the instruction
https://apacheignite.readme.io/docs/docker-deployment run command
{noformat}
gcloud compute images create --source-uri
gs://ignite-media/ignite-google-image-1.0.0.tar.gz
{noformat}
-
ACTUAL RESULT
-
The result is " - The resource
'http://storage.googleapis.com/ignite-media/ignite-google-image-1.0.0.tar.gz'
of type 'Google Cloud Storage object' was not found."
-
EXPECTED RESULT
-
The image should be created without any exceptions
was:
-
DESCRIPTION
-
Couldn't run Ignite docker container on the Google Compute due to missing
ignite-google-image-1.0.0.tar.gz file
-
STEPS FOR REPRODUCE
-
# In accordance with the instruction
https://apacheignite.readme.io/docs/docker-deployment run command
{noformat}
gcloud compute images create --source-uri
gs://ignite-media/ignite-google-image-1.0.0.tar.gz
{noformat}
-
ACTUAL RESULT
-
The result is " - The resource
'http://storage.googleapis.com/ignite-media/ignite-google-image-1.0.0.tar.gz'
of type 'Google Cloud Storage object' was not found."
-
EXPECTED RESULT
-
The image should be created without any exceptions
> Couldn't import Ignite Image to Google Compute
> --
>
> Key: IGNITE-3344
> URL: https://issues.apache.org/jira/browse/IGNITE-3344
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.6
>Reporter: Vasilisa Sidorova
>
> -
> DESCRIPTION
> -
> Couldn't run Ignite docker container on the Google Compute due to missing
> ignite-google-image-1.0.0.tar.gz file
> -
> STEPS FOR REPRODUCE
> -
> # In accordance with the instruction
> https://apacheignite.readme.io/docs/docker-deployment run command
> {noformat}
> gcloud compute images create --source-uri
> gs://ignite-media/ignite-google-image-1.0.0.tar.gz
> {noformat}
> -
> ACTUAL RESULT
> -
> The result is " - The resource
> 'http://storage.googleapis.com/ignite-media/ignite-google-image-1.0.0.tar.gz'
> of type 'Google Cloud Storage object' was not found."
> -
> EXPECTED RESULT
> -
> The image should be created without any exceptions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3344) Couldn't import Ignite Image to Google Compute
Vasilisa Sidorova created IGNITE-3344:
--
Summary: Couldn't import Ignite Image to Google Compute
Key: IGNITE-3344
URL: https://issues.apache.org/jira/browse/IGNITE-3344
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 1.6
Reporter: Vasilisa Sidorova
-
DESCRIPTION
-
Couldn't run Ignite docker container on the Google Compute due to missing
ignite-google-image-1.0.0.tar.gz file
-
STEPS FOR REPRODUCE
-
# In accordance with the instruction
https://apacheignite.readme.io/docs/docker-deployment run command
{noformat}
gcloud compute images create --source-uri
gs://ignite-media/ignite-google-image-1.0.0.tar.gz
{noformat}
-
ACTUAL RESULT
-
The result is " - The resource
'http://storage.googleapis.com/ignite-media/ignite-google-image-1.0.0.tar.gz'
of type 'Google Cloud Storage object' was not found."
-
EXPECTED RESULT
-
The image should be created without any exceptions
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3155) visorcmd: connection to the grid with default config doesn't work
[
https://issues.apache.org/jira/browse/IGNITE-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3155:
---
Summary: visorcmd: connection to the grid with default config doesn't work
(was: visorcmd: "open -d" doesn't work )
> visorcmd: connection to the grid with default config doesn't work
> --
>
> Key: IGNITE-3155
> URL: https://issues.apache.org/jira/browse/IGNITE-3155
> Project: Ignite
> Issue Type: Bug
> Components: visor
>Affects Versions: 1.6
> Environment: Ubuntu 14.04, Apache Ignite 1.6.0
>Reporter: Vasilisa Sidorova
>
> -
> DESCRIPTION
> -
> When user try to connect to the grid with default config by command "open -d"
> nothing happens
> -
> STEPS FOR REPRODUCE
> -
> # Run node from IGNITE_HOME with default config (./config/default-config.xml)
> by command "./bin/ignite.sh -v"
> # Run ignitevisorcmd.sh
> # Connect visor to the grid by the command "open -d"
> # Type "node"
> -
> ACTUAL RESULT
> -
> # Topology is empty
> -
> EXPECTED RESULT
> -
> # Message "Detailed statistics (y/n) [n]:" is presented
> -
> ADDITIONAL INFO
> -
> # Reproducible if visorcmd is started before node
> # If the next step for presented scenario will be run node by command
> {noformat}
> ./bin/ignite.sh -v ./examples/config/example-ignite.xml
> {noformat}
> Then topology will not be empty yet. But if scenario is:
> ** run node by command "./bin/ignite.sh -v
> ./examples/config/example-ignite.xml"
> ** run ignitevisorcmd.sh
> ** connect to the grid by the command "open -d"
> ** type "node"
> the result will be the same - topology is empty.
> # It's reproducible if user choose default config (0) through "open" command
> interactive menu
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3155) visorcmd: "open -d" doesn't work
[
https://issues.apache.org/jira/browse/IGNITE-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3155:
---
Description:
-
DESCRIPTION
-
When user try to connect to the grid with default config by command "open -d"
nothing happens
-
STEPS FOR REPRODUCE
-
# Run node from IGNITE_HOME with default config (./config/default-config.xml)
by command "./bin/ignite.sh -v"
# Run ignitevisorcmd.sh
# Connect visor to the grid by the command "open -d"
# Type "node"
-
ACTUAL RESULT
-
# Topology is empty
-
EXPECTED RESULT
-
# Message "Detailed statistics (y/n) [n]:" is presented
-
ADDITIONAL INFO
-
# Reproducible if visorcmd is started before node
# If the next step for presented scenario will be run node by command
{noformat}
./bin/ignite.sh -v ./examples/config/example-ignite.xml
{noformat}
Then topology will not be empty yet. But if scenario is:
** run node by command "./bin/ignite.sh -v ./examples/config/example-ignite.xml"
** run ignitevisorcmd.sh
** connect to the grid by the command "open -d"
** type "node"
the result will be the same - topology is empty.
# It's reproducible if user choose default config (0) through "open" command
interactive menu
was:
-
DESCRIPTION
-
When user try to connect to the grid with default config by command "open -d"
nothing happens
-
STEPS FOR REPRODUCE
-
# Run node from IGNITE_HOME with default config (./config/default-config.xml)
by command "./bin/ignite.sh -v"
# Run ignitevisorcmd.sh
# Connect visor to the grid by the command "open -d"
# Type "node"
-
ACTUAL RESULT
-
# Topology is empty
-
EXPECTED RESULT
-
# Message "Detailed statistics (y/n) [n]:" is presented
-
ADDITIONAL INFO
-
# Reproducible if visorcmd is started before node
# If the next step for presented scenario will be run node by command
{noformat}
./bin/ignite.sh -v ./examples/config/example-ignite.xml
{noformat}
Then topology will not be empty yet. But if scenario is:
** run node by command "./bin/ignite.sh -v ./examples/config/example-ignite.xml"
** run ignitevisorcmd.sh
** connect to the grid by the command "open -d"
** type "node"
the result will be the same - topology is empty.
> visorcmd: "open -d" doesn't work
> -
>
> Key: IGNITE-3155
> URL: https://issues.apache.org/jira/browse/IGNITE-3155
> Project: Ignite
> Issue Type: Bug
> Components: visor
>Affects Versions: 1.6
> Environment: Ubuntu 14.04, Apache Ignite 1.6.0
>Reporter: Vasilisa Sidorova
>
> -
> DESCRIPTION
> -
> When user try to connect to the grid with default config by command "open -d"
> nothing happens
> -
> STEPS FOR REPRODUCE
> -
> # Run node from IGNITE_HOME with default config (./config/default-config.xml)
> by command "./bin/ignite.sh -v"
> # Run ignitevisorcmd.sh
> # Connect visor to the grid by the command "open -d"
> # Type "node"
> -
> ACTUAL RESULT
> -
> # Topology is empty
> -
> EXPECTED RESULT
> -
> # Message "Detailed statistics (y/n) [n]:" is presented
> -
> ADDITIONAL INFO
> -
> # Reproducible if visorcmd is started before node
> # If the next step for presented scenario will be run node by command
> {noformat}
> ./bin/ignite.sh -v ./examples/config/example-ignite.xml
> {noformat}
> Then topology will not be empty yet. But if scenario is:
> ** run node by command "./bin/ignite.sh -v
> ./examples/config/example-ignite.xml"
> ** run ignitevisorcmd.sh
> ** connect to the grid by the command "open -d"
> ** type "node"
> the result will be the same - topology is empty.
> # It's reproducible if user
[jira] [Created] (IGNITE-3155) visorcmd: "open -d" doesn't work
Vasilisa Sidorova created IGNITE-3155:
--
Summary: visorcmd: "open -d" doesn't work
Key: IGNITE-3155
URL: https://issues.apache.org/jira/browse/IGNITE-3155
Project: Ignite
Issue Type: Bug
Components: visor
Affects Versions: 1.6
Environment: Ubuntu 14.04, Apache Ignite 1.6.0
Reporter: Vasilisa Sidorova
-
DESCRIPTION
-
When user try to connect to the grid with default config by command "open -d"
nothing happens
-
STEPS FOR REPRODUCE
-
# Run node from IGNITE_HOME with default config (./config/default-config.xml)
by command "./bin/ignite.sh -v"
# Run ignitevisorcmd.sh
# Connect visor to the grid by the command "open -d"
# Type "node"
-
ACTUAL RESULT
-
# Topology is empty
-
EXPECTED RESULT
-
# Message "Detailed statistics (y/n) [n]:" is presented
-
ADDITIONAL INFO
-
# Reproducible if visorcmd is started before node
# If the next step for presented scenario will be run node by command
{noformat}
./bin/ignite.sh -v ./examples/config/example-ignite.xml
{noformat}
Then topology will not be empty yet. But if scenario is:
** run node by command "./bin/ignite.sh -v ./examples/config/example-ignite.xml"
** run ignitevisorcmd.sh
** connect to the grid by the command "open -d"
** type "node"
the result will be the same - topology is empty.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3115) List of ODBC minor issues
[
https://issues.apache.org/jira/browse/IGNITE-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3115:
---
Description:
There is the list of minor issues for ODBC feature:
1. Win7:
1.1 install_amd64.cmd ODBC driver installator:
1.1.1 The final script output always is "32-bit driver can not be found:
""". It's not necessary to find 32-bit driver. Please, fix it
1.2.1 It's possible to write path to the folder into registry. Please,
add path-to-file validation into the script
1.2 Win Administrative Tools GUI:
1.2.1 DNS settings for Apache Ignite ODBC driver should be disabled (as
this is not implemented yet)
1.3 Documentation:
1.3.1 Please, add information that odbc should be building individual
into "Building binaries:" part of the IGNITE_HOME/platforms/cpp/DEVNOTES.txt
1.3.2 Please relocate instruction "Most likely you will need OS
administrator privileges to execute these scripts." before run install script
in the "Installing ODBC driver on Windows" part of the
IGNITE_HOME/platforms/cpp/odbc/README.txt
2. Ubuntu - documentation:
2.1 It will be more user-friendly to mention that path to libignite-odbc.so
should be in the LD_LIBRARY_PATH environment variable in the "Running examples
on Linux" part of the IGNITE_HOME/platforms/cpp/examples/README.txt
2.2 The command
{noformat}
* libtoolize && aclocal && autoheader && automake --add-missing && autoreconf
{noformat}
is absent in the "Running examples on Linux" part of the
IGNITE_HOME/platforms/cpp/examples/README.txt
3. Please, make the same changes in the documentation on the readme.io
was:
There is the list of minor issues for ODBC feature:
1. Win7:
1.1 install_amd64.cmd ODBC driver installator:
1.1.1 The final script output always is "32-bit driver can not be found:
""". It's not necessary to find 32-bit driver. Please, fix it
1.2.1 It's possible to write path to the folder into registry. Please,
add path-to-file validation into the script
1.2 Win Administrative Tools GUI:
1.2.1 DNS settings for Apache Ignite ODBC driver should be disabled (as
this is not implemented yet)
1.3 Documentation:
1.3.1 Please, add information that odbc should be building individual
into "Building binaries:" part of the IGNITE_HOME/platforms/cpp/DEVNOTES.txt
1.3.2 Please relocate instruction "Most likely you will need OS
administrator privileges to execute these scripts." before run install script
in the "Installing ODBC driver on Windows" part of the
IGNITE_HOME/platforms/cpp/odbc/README.txt
2. Ubuntu - documentation:
2.1 It will be more user-friendly to mention that path to libignite-odbc.so
should be in the LD_LIBRARY_PATH environment variable in the "Running examples
on Linux" part of the IGNITE_HOME/platforms/cpp/examples/README.txt
2.2 The command
{noformat}
* libtoolize && aclocal && autoheader && automake --add-missing && autoreconf
{noformat}
is absent in the "Running examples on Linux" part of the
IGNITE_HOME/platforms/cpp/examples/README.txt
> List of ODBC minor issues
> -
>
> Key: IGNITE-3115
> URL: https://issues.apache.org/jira/browse/IGNITE-3115
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 1.6
> Environment: Ubuntu 14.04, Win7
>Reporter: Vasilisa Sidorova
>Priority: Minor
> Fix For: 1.6
>
>
> There is the list of minor issues for ODBC feature:
> 1. Win7:
> 1.1 install_amd64.cmd ODBC driver installator:
> 1.1.1 The final script output always is "32-bit driver can not be
> found: """. It's not necessary to find 32-bit driver. Please, fix it
> 1.2.1 It's possible to write path to the folder into registry. Please,
> add path-to-file validation into the script
> 1.2 Win Administrative Tools GUI:
> 1.2.1 DNS settings for Apache Ignite ODBC driver should be disabled (as
> this is not implemented yet)
> 1.3 Documentation:
> 1.3.1 Please, add information that odbc should be building individual
> into "Building binaries:" part of the IGNITE_HOME/platforms/cpp/DEVNOTES.txt
> 1.3.2 Please relocate instruction "Most likely you will need OS
> administrator privileges to execute these scripts." before run install script
> in the "Installing ODBC driver on Windows" part of the
> IGNITE_HOME/platforms/cpp/odbc/README.txt
> 2. Ubuntu - documentation:
> 2.1 It will be more user-friendly to mention that path to libignite-odbc.so
> should be in the LD_LIBRARY_PATH environment variable in the "Running
> examples on Linux" part of the IGNITE_HOME/platforms/cpp/examples/README.txt
> 2.2 The command
> {noformat}
> * libtoolize && aclocal && autoheader && automake --add-missing && autoreconf
> {noformat}
> is absent in the "Running examples on Linux" part of the
>
[jira] [Created] (IGNITE-3115) List of ODBC minor issues
Vasilisa Sidorova created IGNITE-3115:
--
Summary: List of ODBC minor issues
Key: IGNITE-3115
URL: https://issues.apache.org/jira/browse/IGNITE-3115
Project: Ignite
Issue Type: Bug
Components: odbc
Affects Versions: 1.6
Environment: Ubuntu 14.04, Win7
Reporter: Vasilisa Sidorova
Priority: Minor
Fix For: 1.6
There is the list of minor issues for ODBC feature:
1. Win7:
1.1 install_amd64.cmd ODBC driver installation:
1.1.1 The final script output is "32-bit driver can not be found: """.
It's not necessary to find 32-bit driver. Please, fix it
1.2.1 It's possible to write path to the folder into registry. Please,
add path-to-file validation into the script
1.2 Win Administrative Tools GUI:
1.2.1 DNS settings for Apache Ignite ODBC driver should be disabled (as
this is not implemented yet)
1.3 Documentation:
1.3.1 Please, add information that odbc should be building individual
into "Building binaries:" part of the IGNITE_HOME/platforms/cpp/DEVNOTES.txt
1.3.2 Please relocate instruction "Most likely you will need OS
administrator privileges to execute these scripts." before run install script
in the "Installing ODBC driver on Windows" part of the
IGNITE_HOME/platforms/cpp/odbc/README.txt
2. Ubuntu - documentation:
2.1 It will be more user-friendly to mention that path to libignite-odbc.so
should be in the LD_LIBRARY_PATH environment variable in the "Running examples
on Linux" part of the IGNITE_HOME/platforms/cpp/examples/README.txt
2.2 The command
{noformat}
* libtoolize && aclocal && autoheader && automake --add-missing && autoreconf
{noformat}
is absent in the "Running examples on Linux" part of the
IGNITE_HOME/platforms/cpp/examples/README.txt
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3115) List of ODBC minor issues
[
https://issues.apache.org/jira/browse/IGNITE-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3115:
---
Description:
There is the list of minor issues for ODBC feature:
1. Win7:
1.1 install_amd64.cmd ODBC driver installator:
1.1.1 The final script output is "32-bit driver can not be found: """.
It's not necessary to find 32-bit driver. Please, fix it
1.2.1 It's possible to write path to the folder into registry. Please,
add path-to-file validation into the script
1.2 Win Administrative Tools GUI:
1.2.1 DNS settings for Apache Ignite ODBC driver should be disabled (as
this is not implemented yet)
1.3 Documentation:
1.3.1 Please, add information that odbc should be building individual
into "Building binaries:" part of the IGNITE_HOME/platforms/cpp/DEVNOTES.txt
1.3.2 Please relocate instruction "Most likely you will need OS
administrator privileges to execute these scripts." before run install script
in the "Installing ODBC driver on Windows" part of the
IGNITE_HOME/platforms/cpp/odbc/README.txt
2. Ubuntu - documentation:
2.1 It will be more user-friendly to mention that path to libignite-odbc.so
should be in the LD_LIBRARY_PATH environment variable in the "Running examples
on Linux" part of the IGNITE_HOME/platforms/cpp/examples/README.txt
2.2 The command
{noformat}
* libtoolize && aclocal && autoheader && automake --add-missing && autoreconf
{noformat}
is absent in the "Running examples on Linux" part of the
IGNITE_HOME/platforms/cpp/examples/README.txt
was:
There is the list of minor issues for ODBC feature:
1. Win7:
1.1 install_amd64.cmd ODBC driver installation:
1.1.1 The final script output is "32-bit driver can not be found: """.
It's not necessary to find 32-bit driver. Please, fix it
1.2.1 It's possible to write path to the folder into registry. Please,
add path-to-file validation into the script
1.2 Win Administrative Tools GUI:
1.2.1 DNS settings for Apache Ignite ODBC driver should be disabled (as
this is not implemented yet)
1.3 Documentation:
1.3.1 Please, add information that odbc should be building individual
into "Building binaries:" part of the IGNITE_HOME/platforms/cpp/DEVNOTES.txt
1.3.2 Please relocate instruction "Most likely you will need OS
administrator privileges to execute these scripts." before run install script
in the "Installing ODBC driver on Windows" part of the
IGNITE_HOME/platforms/cpp/odbc/README.txt
2. Ubuntu - documentation:
2.1 It will be more user-friendly to mention that path to libignite-odbc.so
should be in the LD_LIBRARY_PATH environment variable in the "Running examples
on Linux" part of the IGNITE_HOME/platforms/cpp/examples/README.txt
2.2 The command
{noformat}
* libtoolize && aclocal && autoheader && automake --add-missing && autoreconf
{noformat}
is absent in the "Running examples on Linux" part of the
IGNITE_HOME/platforms/cpp/examples/README.txt
> List of ODBC minor issues
> -
>
> Key: IGNITE-3115
> URL: https://issues.apache.org/jira/browse/IGNITE-3115
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 1.6
> Environment: Ubuntu 14.04, Win7
>Reporter: Vasilisa Sidorova
>Priority: Minor
> Fix For: 1.6
>
>
> There is the list of minor issues for ODBC feature:
> 1. Win7:
> 1.1 install_amd64.cmd ODBC driver installator:
> 1.1.1 The final script output is "32-bit driver can not be found: """.
> It's not necessary to find 32-bit driver. Please, fix it
> 1.2.1 It's possible to write path to the folder into registry. Please,
> add path-to-file validation into the script
> 1.2 Win Administrative Tools GUI:
> 1.2.1 DNS settings for Apache Ignite ODBC driver should be disabled (as
> this is not implemented yet)
> 1.3 Documentation:
> 1.3.1 Please, add information that odbc should be building individual
> into "Building binaries:" part of the IGNITE_HOME/platforms/cpp/DEVNOTES.txt
> 1.3.2 Please relocate instruction "Most likely you will need OS
> administrator privileges to execute these scripts." before run install script
> in the "Installing ODBC driver on Windows" part of the
> IGNITE_HOME/platforms/cpp/odbc/README.txt
> 2. Ubuntu - documentation:
> 2.1 It will be more user-friendly to mention that path to libignite-odbc.so
> should be in the LD_LIBRARY_PATH environment variable in the "Running
> examples on Linux" part of the IGNITE_HOME/platforms/cpp/examples/README.txt
> 2.2 The command
> {noformat}
> * libtoolize && aclocal && autoheader && automake --add-missing && autoreconf
> {noformat}
> is absent in the "Running examples on Linux" part of the
> IGNITE_HOME/platforms/cpp/examples/README.txt
--
This message was sent by Atlassian JIRA
[jira] [Updated] (IGNITE-3115) List of ODBC minor issues
[
https://issues.apache.org/jira/browse/IGNITE-3115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3115:
---
Description:
There is the list of minor issues for ODBC feature:
1. Win7:
1.1 install_amd64.cmd ODBC driver installator:
1.1.1 The final script output always is "32-bit driver can not be found:
""". It's not necessary to find 32-bit driver. Please, fix it
1.2.1 It's possible to write path to the folder into registry. Please,
add path-to-file validation into the script
1.2 Win Administrative Tools GUI:
1.2.1 DNS settings for Apache Ignite ODBC driver should be disabled (as
this is not implemented yet)
1.3 Documentation:
1.3.1 Please, add information that odbc should be building individual
into "Building binaries:" part of the IGNITE_HOME/platforms/cpp/DEVNOTES.txt
1.3.2 Please relocate instruction "Most likely you will need OS
administrator privileges to execute these scripts." before run install script
in the "Installing ODBC driver on Windows" part of the
IGNITE_HOME/platforms/cpp/odbc/README.txt
2. Ubuntu - documentation:
2.1 It will be more user-friendly to mention that path to libignite-odbc.so
should be in the LD_LIBRARY_PATH environment variable in the "Running examples
on Linux" part of the IGNITE_HOME/platforms/cpp/examples/README.txt
2.2 The command
{noformat}
* libtoolize && aclocal && autoheader && automake --add-missing && autoreconf
{noformat}
is absent in the "Running examples on Linux" part of the
IGNITE_HOME/platforms/cpp/examples/README.txt
was:
There is the list of minor issues for ODBC feature:
1. Win7:
1.1 install_amd64.cmd ODBC driver installator:
1.1.1 The final script output is "32-bit driver can not be found: """.
It's not necessary to find 32-bit driver. Please, fix it
1.2.1 It's possible to write path to the folder into registry. Please,
add path-to-file validation into the script
1.2 Win Administrative Tools GUI:
1.2.1 DNS settings for Apache Ignite ODBC driver should be disabled (as
this is not implemented yet)
1.3 Documentation:
1.3.1 Please, add information that odbc should be building individual
into "Building binaries:" part of the IGNITE_HOME/platforms/cpp/DEVNOTES.txt
1.3.2 Please relocate instruction "Most likely you will need OS
administrator privileges to execute these scripts." before run install script
in the "Installing ODBC driver on Windows" part of the
IGNITE_HOME/platforms/cpp/odbc/README.txt
2. Ubuntu - documentation:
2.1 It will be more user-friendly to mention that path to libignite-odbc.so
should be in the LD_LIBRARY_PATH environment variable in the "Running examples
on Linux" part of the IGNITE_HOME/platforms/cpp/examples/README.txt
2.2 The command
{noformat}
* libtoolize && aclocal && autoheader && automake --add-missing && autoreconf
{noformat}
is absent in the "Running examples on Linux" part of the
IGNITE_HOME/platforms/cpp/examples/README.txt
> List of ODBC minor issues
> -
>
> Key: IGNITE-3115
> URL: https://issues.apache.org/jira/browse/IGNITE-3115
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 1.6
> Environment: Ubuntu 14.04, Win7
>Reporter: Vasilisa Sidorova
>Priority: Minor
> Fix For: 1.6
>
>
> There is the list of minor issues for ODBC feature:
> 1. Win7:
> 1.1 install_amd64.cmd ODBC driver installator:
> 1.1.1 The final script output always is "32-bit driver can not be
> found: """. It's not necessary to find 32-bit driver. Please, fix it
> 1.2.1 It's possible to write path to the folder into registry. Please,
> add path-to-file validation into the script
> 1.2 Win Administrative Tools GUI:
> 1.2.1 DNS settings for Apache Ignite ODBC driver should be disabled (as
> this is not implemented yet)
> 1.3 Documentation:
> 1.3.1 Please, add information that odbc should be building individual
> into "Building binaries:" part of the IGNITE_HOME/platforms/cpp/DEVNOTES.txt
> 1.3.2 Please relocate instruction "Most likely you will need OS
> administrator privileges to execute these scripts." before run install script
> in the "Installing ODBC driver on Windows" part of the
> IGNITE_HOME/platforms/cpp/odbc/README.txt
> 2. Ubuntu - documentation:
> 2.1 It will be more user-friendly to mention that path to libignite-odbc.so
> should be in the LD_LIBRARY_PATH environment variable in the "Running
> examples on Linux" part of the IGNITE_HOME/platforms/cpp/examples/README.txt
> 2.2 The command
> {noformat}
> * libtoolize && aclocal && autoheader && automake --add-missing && autoreconf
> {noformat}
> is absent in the "Running examples on Linux" part of the
> IGNITE_HOME/platforms/cpp/examples/README.txt
--
This message was sent by
[jira] [Commented] (IGNITE-2435) Integration with Mesos doesn't work with limited access to internet
[ https://issues.apache.org/jira/browse/IGNITE-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15270770#comment-15270770 ] Vasilisa Sidorova commented on IGNITE-2435: Integration with Mesos works good with new parameter. Nikolay, please, update "Mesos deployment" documentation https://apacheignite.readme.io/docs/mesos-deployment > Integration with Mesos doesn't work with limited access to internet > --- > > Key: IGNITE-2435 > URL: https://issues.apache.org/jira/browse/IGNITE-2435 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.5.0.final >Reporter: Nikolay Tikhonov >Assignee: Nikolay Tikhonov > Fix For: 1.6 > > > Ignite Mesos integration doesn't work behind a firewall. Need to make all > external resources will customizable and avoid unnecessary accesses to web. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3071) Sporadic NPE for TcpDiscoverySpi
Vasilisa Sidorova created IGNITE-3071:
--
Summary: Sporadic NPE for TcpDiscoverySpi
Key: IGNITE-3071
URL: https://issues.apache.org/jira/browse/IGNITE-3071
Project: Ignite
Issue Type: Bug
Affects Versions: 1.5.0.final
Environment: Win8.0
Reporter: Vasilisa Sidorova
Priority: Minor
-
DESCRIPTION
-
Sometimes there is NPE in the node's log during cluster's life. It don't have
any bad side effect yet but it looks not good.
-
STEPS FOR REPRODUCE
-
# Run cluster from several nodes
# Try to do some actions with/in cache (for example, run several java examples)
-
ACTUAL RESULT
-
There is NPE (between examples running) on some node's console:
{noformat}
[15:16:27,546][SEVERE][tcp-disco-ip-finder-cleaner-#5%null%][TcpDiscoverySpi]
Runtime error caught during grid runnable execution: IgniteSpiThread [name=tcp
-disco-ip-finder-cleaner-#5%null%]
java.lang.NullPointerException
at org.apache.ignite.spi.discovery.tcp.ServerImpl$IpFinderCleaner$2.ap
ply(ServerImpl.java:1726)
at org.apache.ignite.spi.discovery.tcp.ServerImpl$IpFinderCleaner$2.ap
ply(ServerImpl.java:1718)
at org.apache.ignite.spi.discovery.tcp.ServerImpl$IpFinderCleaner.clea
nIpFinder(ServerImpl.java:1747)
at org.apache.ignite.spi.discovery.tcp.ServerImpl$IpFinderCleaner.body
(ServerImpl.java:1691)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
{noformat}
-
EXPECTED RESULT
-
There are not any exceptions in the logs during cluster life.
-
ADDITIONAL INFO
-
It reproducible when I work under WiFi (slow connection) instead Eth
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-3043) NPE during restarting remote nodes by ignitevisorcmd
[
https://issues.apache.org/jira/browse/IGNITE-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3043:
---
Summary: NPE during restarting remote nodes by ignitevisorcmd (was: NPE
during restart remote node by ignitevisorcmd)
> NPE during restarting remote nodes by ignitevisorcmd
>
>
> Key: IGNITE-3043
> URL: https://issues.apache.org/jira/browse/IGNITE-3043
> Project: Ignite
> Issue Type: Bug
> Components: visor
>Affects Versions: 1.5.0.final
> Environment: Ubuntu 14.04
>Reporter: Vasilisa Sidorova
> Attachments: ignite-fdaae430.0.log
>
>
> -
> DESCRIPTION
> -
> There is NPE during restarting remote nodes by ignitevisorcmd command "start"
> but nodes are restarted
> -
> STEPS FOR REPRODUCE
> -
> # Run node on the localhost
> # Run ignitevisorcmd on the localhost
> # Open connection to the running node
> # Run nodes on the another host by the command
> {noformat}
> start -h=another_host_ip -u=username -pw=username_password -t=3 -n=3
> -g=path_to_ignite_installation_folder -c=path_to_configuration_file
> {noformat}
> # Verify nodes are started OK
> # Run command
> {noformat}
> start -r -h=another_host_ip -u=username -pw=username_password -t=3 -n=2
> -g=path_to_ignite_installation_folder -c=path_to_configuration_file
> {noformat}
> -
> ACTUAL RESULT
> -
> # There is NPE during restarting remote nodes but nodes are restarted. Look
> at the attached log file:
> {noformat}
> (err) Failed to notify listener:
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2...@21b81941java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.updatePartitionSingleMap(GridDhtPartitionsExchangeFuture.java:1408)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$600(GridDhtPartitionsExchangeFuture.java:87)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:1253)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:1219)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:262)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:225)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceive(GridDhtPartitionsExchangeFuture.java:1219)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1056)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$900(GridCachePartitionExchangeManager.java:105)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:272)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:270)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:1620)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:1602)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:582)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:280)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:204)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:80)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:163)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1058)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:836)
> at
>
[jira] [Updated] (IGNITE-3043) NPE during restart remote node by ignitevisorcmd
[
https://issues.apache.org/jira/browse/IGNITE-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3043:
---
Description:
-
DESCRIPTION
-
There is NPE during restarting remote nodes by ignitevisorcmd command "start"
but nodes are restarted
-
STEPS FOR REPRODUCE
-
# Run node on the localhost
# Run ignitevisorcmd on the localhost
# Open connection to the running node
# Run nodes on the another host by the command
{noformat}
start -h=another_host_ip -u=username -pw=username_password -t=3 -n=3
-g=path_to_ignite_installation_folder -c=path_to_configuration_file
{noformat}
# Verify nodes are started OK
# Run command
{noformat}
start -r -h=another_host_ip -u=username -pw=username_password -t=3 -n=2
-g=path_to_ignite_installation_folder -c=path_to_configuration_file
{noformat}
-
ACTUAL RESULT
-
# There is NPE during restarting remote nodes but nodes are restarted. Look at
the attached log file:
{noformat}
(err) Failed to notify listener:
o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2...@21b81941java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.updatePartitionSingleMap(GridDhtPartitionsExchangeFuture.java:1408)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$600(GridDhtPartitionsExchangeFuture.java:87)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:1253)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:1219)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:262)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:225)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceive(GridDhtPartitionsExchangeFuture.java:1219)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1056)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$900(GridCachePartitionExchangeManager.java:105)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:272)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:270)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:1620)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:1602)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:582)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:280)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:204)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:80)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:163)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1058)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:836)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:104)
at
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:799)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}
# All 3 remote nodes are stopped and 2 nodes are started again
-
EXPECTED RESULT
-
# There aren't any errors during "start" command execution
# Only 2 remote nodes are restarted and one of them stay
[jira] [Updated] (IGNITE-3043) NPE during restart remote node by ignitevisorcmd
[
https://issues.apache.org/jira/browse/IGNITE-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3043:
---
Attachment: ignite-fdaae430.0.log
> NPE during restart remote node by ignitevisorcmd
>
>
> Key: IGNITE-3043
> URL: https://issues.apache.org/jira/browse/IGNITE-3043
> Project: Ignite
> Issue Type: Bug
> Components: visor
>Affects Versions: 1.5.0.final
> Environment: Ubuntu 14.04
>Reporter: Vasilisa Sidorova
> Attachments: ignite-fdaae430.0.log
>
>
> -
> DESCRIPTION
> -
> There is NPE during restart remote nodes by ignitevisorcmd command "start"
> but nodes are restarted
> -
> STEPS FOR REPRODUCE
> -
> # Run node on the localhost
> # Run ignitevisorcmd on the localhost
> # Open connection to the running node
> # Run nodes on the another host by the command
> {noformat}
> start -h=another_host_ip -u=username -pw=username_password -t=3 -n=3
> -g=path_to_ignite_installation_folder -c=path_to_configuration_file
> {noformat}
> # Verify nodes are started OK
> # Run command
> {noformat}
> start -r -h=another_host_ip -u=username -pw=username_password -t=3 -n=2
> -g=path_to_ignite_installation_folder -c=path_to_configuration_file
> {noformat}
> -
> ACTUAL RESULT
> -
> # There is NPE during restart remote nodes but nodes are restarted. Look at
> the attached log file:
> {noformat}
> (err) Failed to notify listener:
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2...@21b81941java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.updatePartitionSingleMap(GridDhtPartitionsExchangeFuture.java:1408)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$600(GridDhtPartitionsExchangeFuture.java:87)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:1253)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:1219)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:262)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:225)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceive(GridDhtPartitionsExchangeFuture.java:1219)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1056)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$900(GridCachePartitionExchangeManager.java:105)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:272)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:270)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:1620)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:1602)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:582)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:280)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:204)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:80)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:163)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1058)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:836)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:104)
> at
>
[jira] [Updated] (IGNITE-3043) NPE during restart remote node by ignitevisorcmd
[
https://issues.apache.org/jira/browse/IGNITE-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3043:
---
Attachment: (was: ignite-fdaae430.0.log)
> NPE during restart remote node by ignitevisorcmd
>
>
> Key: IGNITE-3043
> URL: https://issues.apache.org/jira/browse/IGNITE-3043
> Project: Ignite
> Issue Type: Bug
> Components: visor
>Affects Versions: 1.5.0.final
> Environment: Ubuntu 14.04
>Reporter: Vasilisa Sidorova
>
> -
> DESCRIPTION
> -
> There is NPE during restart remote nodes by ignitevisorcmd command "start"
> but nodes are restarted
> -
> STEPS FOR REPRODUCE
> -
> # Run node on the localhost
> # Run ignitevisorcmd on the localhost
> # Open connection to the running node
> # Run nodes on the another host by the command
> {noformat}
> start -h=another_host_ip -u=username -pw=username_password -t=3 -n=3
> -g=path_to_ignite_installation_folder -c=path_to_configuration_file
> {noformat}
> # Verify nodes are started OK
> # Run command
> {noformat}
> start -r -h=another_host_ip -u=username -pw=username_password -t=3 -n=2
> -g=path_to_ignite_installation_folder -c=path_to_configuration_file
> {noformat}
> -
> ACTUAL RESULT
> -
> # There is NPE during restart remote nodes but nodes are restarted. Look at
> the attached log file:
> {noformat}
> (err) Failed to notify listener:
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2...@21b81941java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.updatePartitionSingleMap(GridDhtPartitionsExchangeFuture.java:1408)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$600(GridDhtPartitionsExchangeFuture.java:87)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:1253)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:1219)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:262)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:225)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceive(GridDhtPartitionsExchangeFuture.java:1219)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1056)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$900(GridCachePartitionExchangeManager.java:105)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:272)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:270)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:1620)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:1602)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:582)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:280)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:204)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:80)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:163)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1058)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:836)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:104)
> at
>
[jira] [Updated] (IGNITE-3043) NPE during restart remote node by ignitevisorcmd
[
https://issues.apache.org/jira/browse/IGNITE-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3043:
---
Attachment: ignite-fdaae430.0.log
> NPE during restart remote node by ignitevisorcmd
>
>
> Key: IGNITE-3043
> URL: https://issues.apache.org/jira/browse/IGNITE-3043
> Project: Ignite
> Issue Type: Bug
> Components: visor
>Affects Versions: 1.5.0.final
> Environment: Ubuntu 14.04
>Reporter: Vasilisa Sidorova
> Attachments: ignite-fdaae430.0.log
>
>
> -
> DESCRIPTION
> -
> There is NPE during restart remote nodes by ignitevisorcmd command "start"
> but nodes are restarted
> -
> STEPS FOR REPRODUCE
> -
> # Run node on the localhost
> # Run ignitevisorcmd on the localhost
> # Open connection to the running node
> # Run nodes on the another host by the command
> {noformat}
> start -h=another_host_ip -u=username -pw=username_password -t=3 -n=3
> -g=path_to_ignite_installation_folder -c=path_to_configuration_file
> {noformat}
> # Verify nodes are started OK
> # Run command
> {noformat}
> start -r -h=another_host_ip -u=username -pw=username_password -t=3 -n=2
> -g=path_to_ignite_installation_folder -c=path_to_configuration_file
> {noformat}
> -
> ACTUAL RESULT
> -
> # There is NPE during restart remote nodes but nodes are restarted. Look at
> the attached log file:
> {noformat}
> (err) Failed to notify listener:
> o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2...@21b81941java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.updatePartitionSingleMap(GridDhtPartitionsExchangeFuture.java:1408)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$600(GridDhtPartitionsExchangeFuture.java:87)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:1253)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:1219)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:262)
> at
> org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:225)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceive(GridDhtPartitionsExchangeFuture.java:1219)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1056)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$900(GridCachePartitionExchangeManager.java:105)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:272)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:270)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:1620)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:1602)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:582)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:280)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:204)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:80)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:163)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1058)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:836)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:104)
> at
>
[jira] [Updated] (IGNITE-3043) NPE during restart remote node by ignitevisorcmd
[
https://issues.apache.org/jira/browse/IGNITE-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3043:
---
Description:
-
DESCRIPTION
-
There is NPE during restart remote nodes by ignitevisorcmd command "start" but
nodes are restarted
-
STEPS FOR REPRODUCE
-
# Run node on the localhost
# Run ignitevisorcmd on the localhost
# Open connection to the running node
# Run nodes on the another host by the command
{noformat}
start -h=another_host_ip -u=username -pw=username_password -t=3 -n=3
-g=path_to_ignite_installation_folder -c=path_to_configuration_file
{noformat}
# Verify nodes are started OK
# Run command
{noformat}
start -r -h=another_host_ip -u=username -pw=username_password -t=3 -n=2
-g=path_to_ignite_installation_folder -c=path_to_configuration_file
{noformat}
-
ACTUAL RESULT
-
# There is NPE during restart remote nodes but nodes are restarted. Look at the
attached log file:
{noformat}
(err) Failed to notify listener:
o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2...@21b81941java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.updatePartitionSingleMap(GridDhtPartitionsExchangeFuture.java:1408)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$600(GridDhtPartitionsExchangeFuture.java:87)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:1253)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:1219)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:262)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:225)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceive(GridDhtPartitionsExchangeFuture.java:1219)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1056)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$900(GridCachePartitionExchangeManager.java:105)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:272)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:270)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:1620)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:1602)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:582)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:280)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:204)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:80)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:163)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1058)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:836)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:104)
at
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:799)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{noformat}
# All 3 remote nodes are stopped and 2 nodes are started again
-
EXPECTED RESULT
-
# There aren't any errors during "start" command execution
# Only 2 remote nodes are restarted and one of them stay
[jira] [Updated] (IGNITE-3043) NPE during restart remote node by ignitevisorcmd
[
https://issues.apache.org/jira/browse/IGNITE-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-3043:
---
Description:
-
DESCRIPTION
-
There is NPE during restart remote nodes by ignitevisorcmd command "start" but
nodes are restarted
-
STEPS FOR REPRODUCE
-
# Run node on the localhost
# Run ignitevisorcmd on the localhost
# Open connection to the running node
# Run nodes on the another host by the command
{noformat}
start -h=another_host_ip -u=username -pw=username_password -t=3 -n=3
-g=path_to_ignite_installation_folder -c=path_to_configuration_file
{noformat}
# Verify nodes are started OK
# Run command
{noformat}
start -r -h=another_host_ip -u=username -pw=username_password -t=3 -n=2
-g=path_to_ignite_installation_folder -c=path_to_configuration_file
{noformat}
-
ACTUAL RESULT
-
# There is NPE during restart remote nodes but nodes are restarted. Look at the
attached log file:
{noformat}
[18:05:07] (err) Failed to notify listener:
o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2...@21b81941java.lang.NullPointerException
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.updatePartitionSingleMap(GridDhtPartitionsExchangeFuture.java:1408)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.access$600(GridDhtPartitionsExchangeFuture.java:87)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:1253)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture$2.apply(GridDhtPartitionsExchangeFuture.java:1219)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:262)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.listen(GridFutureAdapter.java:225)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onReceive(GridDhtPartitionsExchangeFuture.java:1219)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.processSinglePartitionUpdate(GridCachePartitionExchangeManager.java:1056)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$900(GridCachePartitionExchangeManager.java:105)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:272)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$2.onMessage(GridCachePartitionExchangeManager.java:270)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:1620)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$MessageHandler.apply(GridCachePartitionExchangeManager.java:1602)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:582)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:280)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:204)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:80)
at
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:163)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1058)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:836)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:104)
at
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:799)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
[18:05:07,353][SEVERE][sys-#20%null%][GridCacheIoManager] Failed processing
message [senderId=0c626df9-8e71-48dd-b9c1-f9bb1a88d3d5,
msg=GridDhtPartitionsSingleMessage [parts=null, partCntrs=null, client=false,
super=GridDhtPartitionsAbstractMessage [exchId=GridDhtPartitionExchangeId
[jira] [Created] (IGNITE-3043) NPE during restart remote node by ignitevisorcmd
Vasilisa Sidorova created IGNITE-3043:
--
Summary: NPE during restart remote node by ignitevisorcmd
Key: IGNITE-3043
URL: https://issues.apache.org/jira/browse/IGNITE-3043
Project: Ignite
Issue Type: Bug
Components: visor
Affects Versions: 1.5.0.final
Environment: Ubuntu 14.04
Reporter: Vasilisa Sidorova
-
DESCRIPTION
-
There is NPE during restart remote nodes by ignitevisorcmd command "start" but
nodes are restarted
-
STEPS FOR REPRODUCE
-
# Run node on the localhost
# Run ignitevisorcmd on the localhost
# Open connection to the running node
# Run nodes on the another host by the command
{noformat}
start -h=another_host_ip -u=username -pw=username_password -t=3 -n=3
-g=path_to_ignite_installation_folder -c=path_to_configuration_file
{noformat}
# Verify nodes are started OK
# Run command
{noformat}
start -r -h=another_host_ip -u=username -pw=username_password -t=3 -n=2
-g=path_to_ignite_installation_folder -c=path_to_configuration_file
{noformat}
-
ACTUAL RESULT
-
# There is NPE during restart remote nodes but nodes are restarted. Look at the
attached log file
# All 3 remote nodes are stopped and 2 nodes are started again
-
EXPECTED RESULT
-
# There aren't any errors during "start" command execution
# Only 2 remote nodes are restarted and one of them stay running
-
ADDITIONAL INFO
-
# Sometimes the same NPE appears during starting remote nodes but this is
unstable reproducible
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2927) Ignite Yarn application stdout and stderr logs are misrecognized
[ https://issues.apache.org/jira/browse/IGNITE-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasilisa Sidorova updated IGNITE-2927: --- Summary: Ignite Yarn application stdout and stderr logs are misrecognized (was: Ignite Yarn application stdout and stderr logs are misrecognized.) > Ignite Yarn application stdout and stderr logs are misrecognized > > > Key: IGNITE-2927 > URL: https://issues.apache.org/jira/browse/IGNITE-2927 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.5.0.final >Reporter: Vasilisa Sidorova >Priority: Minor > Attachments: 1_appMngr.png, 2_stdoutVSstderr.png, 3_stderrLog.png > > > - > DESCRIPTION > - > Ignite Yarn application stdout and stderr logs are misrecognized. > - > STEPS FOR REPRODUCE > - > # Configure and run YARN and Hadoop cluster > # Run Ignite Yarn application > # Go to web interface for the ResourceManager (http://localhost:8088/) -> > Applications -> RUNNING -> Click onto link for application running in the > previous step > # Click on the "Logs" link (look at the 1_appMngr.png attached picture) > - > ACTUAL RESULT > - > * Stdout is empty (as a rule) (look at the 2_stdoutVSstderr.png attached > picture) > * Stderr contains stdout content (and doesn't contains errors) (look at the > 3_stderrLog.png attached picture) > - > EXPECTED RESULT > - > * Stderr is empty (as a rule) > * Stdout contains stdout content -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2927) Ignite Yarn application stdout and stderr logs are misrecognized.
[ https://issues.apache.org/jira/browse/IGNITE-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasilisa Sidorova updated IGNITE-2927: --- Description: - DESCRIPTION - Ignite Yarn application stdout and stderr logs are misrecognized. - STEPS FOR REPRODUCE - # Configure and run YARN and Hadoop cluster # Run Ignite Yarn application # Go to web interface for the ResourceManager (http://localhost:8088/) -> Applications -> RUNNING -> Click onto link for application running in the previous step # Click on the "Logs" link (look at the 1_appMngr.png attached picture) - ACTUAL RESULT - * Stdout is empty (as a rule) (look at the 2_stdoutVSstderr.png attached picture) * Stderr contains stdout content (and doesn't contains errors) (look at the 3_stderrLog.png attached picture) - EXPECTED RESULT - * Stderr is empty (as a rule) * Stdout contains stdout content was: - DESCRIPTION - Ignite Yarn application stdout and stderr logs are misrecognized. - STEPS FOR REPRODUCE - # Configure and run YARN and Hadoop cluster # Run Ignite Yarn application # Go to web interface for the ResourceManager (http://localhost:8088/) -> Applications -> RUNNING -> Click onto link for application running in the previous step # Click on the "Logs" link - ACTUAL RESULT - * Stdout is empty (as a rule) * Stderr contains stdout content (and doesn't contains errors) - EXPECTED RESULT - * Stderr is empty (as a rule) * Stdout contains stdout content > Ignite Yarn application stdout and stderr logs are misrecognized. > - > > Key: IGNITE-2927 > URL: https://issues.apache.org/jira/browse/IGNITE-2927 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.5.0.final >Reporter: Vasilisa Sidorova >Priority: Minor > Attachments: 1_appMngr.png, 2_stdoutVSstderr.png, 3_stderrLog.png > > > - > DESCRIPTION > - > Ignite Yarn application stdout and stderr logs are misrecognized. > - > STEPS FOR REPRODUCE > - > # Configure and run YARN and Hadoop cluster > # Run Ignite Yarn application > # Go to web interface for the ResourceManager (http://localhost:8088/) -> > Applications -> RUNNING -> Click onto link for application running in the > previous step > # Click on the "Logs" link (look at the 1_appMngr.png attached picture) > - > ACTUAL RESULT > - > * Stdout is empty (as a rule) (look at the 2_stdoutVSstderr.png attached > picture) > * Stderr contains stdout content (and doesn't contains errors) (look at the > 3_stderrLog.png attached picture) > - > EXPECTED RESULT > - > * Stderr is empty (as a rule) > * Stdout contains stdout content -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2927) Ignite Yarn application stdout and stderr logs are misrecognized.
[ https://issues.apache.org/jira/browse/IGNITE-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasilisa Sidorova updated IGNITE-2927: --- Attachment: 3_stderrLog.png 2_stdoutVSstderr.png 1_appMngr.png > Ignite Yarn application stdout and stderr logs are misrecognized. > - > > Key: IGNITE-2927 > URL: https://issues.apache.org/jira/browse/IGNITE-2927 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.5.0.final >Reporter: Vasilisa Sidorova >Priority: Minor > Attachments: 1_appMngr.png, 2_stdoutVSstderr.png, 3_stderrLog.png > > > - > DESCRIPTION > - > Ignite Yarn application stdout and stderr logs are misrecognized. > - > STEPS FOR REPRODUCE > - > # Configure and run YARN and Hadoop cluster > # Run Ignite Yarn application > # Go to web interface for the ResourceManager (http://localhost:8088/) -> > Applications -> RUNNING -> Click onto link for application running in the > previous step > # Click on the "Logs" link (look at the 1_appMngr.png attached picture) > - > ACTUAL RESULT > - > * Stdout is empty (as a rule) (look at the 2_stdoutVSstderr.png attached > picture) > * Stderr contains stdout content (and doesn't contains errors) (look at the > 3_stderrLog.png attached picture) > - > EXPECTED RESULT > - > * Stderr is empty (as a rule) > * Stdout contains stdout content -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2927) Ignite Yarn application stdout and stderr logs are misrecognized.
[ https://issues.apache.org/jira/browse/IGNITE-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasilisa Sidorova updated IGNITE-2927: --- Description: - DESCRIPTION - Ignite Yarn application stdout and stderr logs are misrecognized. - STEPS FOR REPRODUCE - # Configure and run YARN and Hadoop cluster # Run Ignite Yarn application # Go to web interface for the ResourceManager (http://localhost:8088/) -> Applications -> RUNNING -> Click onto link for application running in the previous step # Click on the "Logs" link - ACTUAL RESULT - * Stdout is empty (as a rule) * Stderr contains stdout content (and doesn't contains errors) - EXPECTED RESULT - * Stderr is empty (as a rule) * Stdout contains stdout content was: - DESCRIPTION - Ignite Yarn application stdout and stderr logs are misrecognized. - STEPS FOR REPRODUCE - # Configure and run YARN and Hadoop cluster # Run Ignite Yarn application # Go to web interface for the ResourceManager (http://localhost:8088/) -> Applications -> RUNNING -> Click onto link for application running in the previous step # Click on the "Logs" link - ACTUAL RESULT - ## Stdout is empty (as a rule) ## Stderr contains stdout content (and doesn't contains errors) - EXPECTED RESULT - ## Stderr is empty (as a rule) ## Stdout contains stdout content > Ignite Yarn application stdout and stderr logs are misrecognized. > - > > Key: IGNITE-2927 > URL: https://issues.apache.org/jira/browse/IGNITE-2927 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.5.0.final >Reporter: Vasilisa Sidorova >Priority: Minor > > - > DESCRIPTION > - > Ignite Yarn application stdout and stderr logs are misrecognized. > - > STEPS FOR REPRODUCE > - > # Configure and run YARN and Hadoop cluster > # Run Ignite Yarn application > # Go to web interface for the ResourceManager (http://localhost:8088/) -> > Applications -> RUNNING -> Click onto link for application running in the > previous step > # Click on the "Logs" link > - > ACTUAL RESULT > - > * Stdout is empty (as a rule) > * Stderr contains stdout content (and doesn't contains errors) > - > EXPECTED RESULT > - > * Stderr is empty (as a rule) > * Stdout contains stdout content -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2927) Ignite Yarn application stdout and stderr logs are misrecognized.
[ https://issues.apache.org/jira/browse/IGNITE-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasilisa Sidorova updated IGNITE-2927: --- Description: - DESCRIPTION - Ignite Yarn application stdout and stderr logs are misrecognized. - STEPS FOR REPRODUCE - # Configure and run YARN and Hadoop cluster # Run Ignite Yarn application # Go to web interface for the ResourceManager (http://localhost:8088/) -> Applications -> RUNNING -> Click onto link for application running in the previous step # Click on the "Logs" link - ACTUAL RESULT - ## Stdout is empty (as a rule) ## Stderr contains stdout content (and doesn't contains errors) - EXPECTED RESULT - ## Stderr is empty (as a rule) ## Stdout contains stdout content was: - DESCRIPTION - Ignite Yarn application stdout and stderr logs are misrecognized. - STEPS FOR REPRODUCE - # Configure and run YARN and Hadoop cluster # Run Ignite Yarn application # Go to web interface for the ResourceManager (http://localhost:8088/) -> Applications -> RUNNING -> Click onto link for application running in the previous step # Click on the "Logs" link - ACTUAL RESULT - # Stdout is empty (as a rule) # Stderr contains stdout content (and doesn't contains errors) - EXPECTED RESULT - # Stderr is empty (as a rule) # Stdout contains stdout content > Ignite Yarn application stdout and stderr logs are misrecognized. > - > > Key: IGNITE-2927 > URL: https://issues.apache.org/jira/browse/IGNITE-2927 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.5.0.final >Reporter: Vasilisa Sidorova >Priority: Minor > > - > DESCRIPTION > - > Ignite Yarn application stdout and stderr logs are misrecognized. > - > STEPS FOR REPRODUCE > - > # Configure and run YARN and Hadoop cluster > # Run Ignite Yarn application > # Go to web interface for the ResourceManager (http://localhost:8088/) -> > Applications -> RUNNING -> Click onto link for application running in the > previous step > # Click on the "Logs" link > - > ACTUAL RESULT > - > ## Stdout is empty (as a rule) > ## Stderr contains stdout content (and doesn't contains errors) > - > EXPECTED RESULT > - > ## Stderr is empty (as a rule) > ## Stdout contains stdout content -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2927) Ignite Yarn application stdout and stderr logs are misrecognized.
Vasilisa Sidorova created IGNITE-2927: -- Summary: Ignite Yarn application stdout and stderr logs are misrecognized. Key: IGNITE-2927 URL: https://issues.apache.org/jira/browse/IGNITE-2927 Project: Ignite Issue Type: Bug Components: general Affects Versions: 1.5.0.final Reporter: Vasilisa Sidorova Priority: Minor - DESCRIPTION - Ignite Yarn application stdout and stderr logs are misrecognized. - STEPS FOR REPRODUCE - # Configure and run YARN and Hadoop cluster # Run Ignite Yarn application # Go to web interface for the ResourceManager (http://localhost:8088/) -> Applications -> RUNNING -> Click onto link for application running in the previous step # Click on the "Logs" link - ACTUAL RESULT - # Stdout is empty (as a rule) # Stderr contains stdout content (and doesn't contains errors) - EXPECTED RESULT - # Stderr is empty (as a rule) # Stdout contains stdout content -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2880) Starting ignite.sh from command line gets ClassNotFoundException after messaging examples running
[
https://issues.apache.org/jira/browse/IGNITE-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-2880:
---
Description:
-
DESCRIPTION
-
If you run any messaging example (java or scala) in the cluster and then try to
run new node from command line the node will be started but gets
ClassNotFoundException
-
STEPS FOR REPRODUCE
-
# Build examples in IDE
# Run ExampleNodeStartup or ./bin/ignite.sh
./examples/config/example-ignite.xml (it doesn't matter)
# Run any messaging example and wait while it will be finished
# Run one more node from command line:
{noformat}
./bin/ignite.sh ./examples/config/example-ignite.xml
{noformat}
-
ACTUAL RESULT
-
Node is started but gets ClassNotFoundException:
{noformat}
[18:34:59,563][SEVERE][tcp-disco-msg-worker-#2%null%][TcpDiscoverySpi] Failed
to unmarshal discovery data for component: 0
class org.apache.ignite.IgniteCheckedException: Failed to find class with given
class loader for unmarshalling (make sure same versions of all classes are
available on all nodes or enable peer-class-loading):
sun.misc.Launcher$AppClassLoader@1447034b
at
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:108)
at
org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMarshaller.java:78)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1717)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeAddedMessage(ServerImpl.java:3685)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2252)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:5789)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2161)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
Caused by: java.lang.ClassNotFoundException:
org.apache.ignite.scalar.examples.ScalarPingPongExample$$anon$1
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:278)
at
org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8213)
at
org.apache.ignite.marshaller.jdk.JdkMarshallerObjectInputStream.resolveClass(JdkMarshallerObjectInputStream.java:54)
at
java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1612)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1517)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1771)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at
org.apache.ignite.internal.GridMessageListenHandler.readExternal(GridMessageListenHandler.java:254)
at
java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1837)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$DiscoveryDataItem.readExternal(GridContinuousProcessor.java:1618)
at
java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1837)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at
org.apache.ignite.internal.util.IgniteUtils.readList(IgniteUtils.java:5176)
at
org.apache.ignite.internal.util.IgniteUtils.readCollection(IgniteUtils.java:1637)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$DiscoveryData.readExternal(GridContinuousProcessor.java:1533)
at
java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1837)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796)
[jira] [Updated] (IGNITE-2880) Starting ignite.sh from command line gets ClassNotFoundException after messaging examples running
[
https://issues.apache.org/jira/browse/IGNITE-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-2880:
---
Description:
-
DESCRIPTION
-
If you run any messaging example (java or scala) in the cluster and then try to
run new node from command line the node will be started but gets
ClassNotFoundException
-
STEPS FOR REPRODUCE
-
# Build examples in IDE
# Run ExampleNodeStartup or ./bin/ignite.sh
./examples/config/example-ignite.xml (it doesn't matter)
# Run any messaging example and wait while it will be finished
# Run one more node from command line:
{noformat}
./bin/ignite.sh ./examples/config/example-ignite.xml
{noformat}
-
ACTUAL RESULT
-
Node is started but gets ClassNotFoundException:
{noformat}
[18:34:59,563][SEVERE][tcp-disco-msg-worker-#2%null%][TcpDiscoverySpi] Failed
to unmarshal discovery data for component: 0
class org.apache.ignite.IgniteCheckedException: Failed to find class with given
class loader for unmarshalling (make sure same versions of all classes are
available on all nodes or enable peer-class-loading):
sun.misc.Launcher$AppClassLoader@1447034b
at
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:108)
at
org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMarshaller.java:78)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1717)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeAddedMessage(ServerImpl.java:3685)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2252)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:5789)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2161)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
Caused by: java.lang.ClassNotFoundException:
org.apache.ignite.scalar.examples.ScalarPingPongExample$$anon$1
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:278)
at
org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8213)
at
org.apache.ignite.marshaller.jdk.JdkMarshallerObjectInputStream.resolveClass(JdkMarshallerObjectInputStream.java:54)
at
java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1612)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1517)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1771)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at
org.apache.ignite.internal.GridMessageListenHandler.readExternal(GridMessageListenHandler.java:254)
at
java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1837)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$DiscoveryDataItem.readExternal(GridContinuousProcessor.java:1618)
at
java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1837)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at
org.apache.ignite.internal.util.IgniteUtils.readList(IgniteUtils.java:5176)
at
org.apache.ignite.internal.util.IgniteUtils.readCollection(IgniteUtils.java:1637)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$DiscoveryData.readExternal(GridContinuousProcessor.java:1533)
at
java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1837)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796)
[jira] [Updated] (IGNITE-2880) Starting ignite.sh from command line gets ClassNotFoundException after messaging examples running
[
https://issues.apache.org/jira/browse/IGNITE-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-2880:
---
Summary: Starting ignite.sh from command line gets ClassNotFoundException
after messaging examples running (was: Starting ignite.sh from command line
get ClassNotFoundException after messaging examples running)
> Starting ignite.sh from command line gets ClassNotFoundException after
> messaging examples running
> -
>
> Key: IGNITE-2880
> URL: https://issues.apache.org/jira/browse/IGNITE-2880
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.6
> Environment: Ubuntu 14.04, Ignite 1.6.0
>Reporter: Vasilisa Sidorova
>
> -
> DESCRIPTION
> -
> If you run any messaging example (java or scala) in the cluster and then try
> to run new node from command line the node will be started but gets
> ClassNotFoundException
> -
> STEPS FOR REPRODUCE
> -
> # Build examples in IDE
> # Run ExampleNodeStartup or ./bin/ignite.sh
> ./examples/config/example-ignite.xml (it doesn't matter)
> # Run any messaging example
> # Run one more node from command line:
> {noformat}
> ./bin/ignite.sh ./examples/config/example-ignite.xml
> {noformat}
> -
> ACTUAL RESULT
> -
> Node is started but gets ClassNotFoundException:
> {noformat}
> [18:34:59,563][SEVERE][tcp-disco-msg-worker-#2%null%][TcpDiscoverySpi] Failed
> to unmarshal discovery data for component: 0
> class org.apache.ignite.IgniteCheckedException: Failed to find class with
> given class loader for unmarshalling (make sure same versions of all classes
> are available on all nodes or enable peer-class-loading):
> sun.misc.Launcher$AppClassLoader@1447034b
> at
> org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:108)
> at
> org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMarshaller.java:78)
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1717)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeAddedMessage(ServerImpl.java:3685)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2252)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:5789)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2161)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> Caused by: java.lang.ClassNotFoundException:
> org.apache.ignite.scalar.examples.ScalarPingPongExample$$anon$1
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:278)
> at
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8213)
> at
> org.apache.ignite.marshaller.jdk.JdkMarshallerObjectInputStream.resolveClass(JdkMarshallerObjectInputStream.java:54)
> at
> java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1612)
> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1517)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1771)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
> at
> org.apache.ignite.internal.GridMessageListenHandler.readExternal(GridMessageListenHandler.java:254)
> at
> java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1837)
> at
> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
> at
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$DiscoveryDataItem.readExternal(GridContinuousProcessor.java:1618)
> at
>
[jira] [Created] (IGNITE-2880) Starting ignite.sh from command line get ClassNotFoundException after messaging examples running.
Vasilisa Sidorova created IGNITE-2880:
--
Summary: Starting ignite.sh from command line get
ClassNotFoundException after messaging examples running.
Key: IGNITE-2880
URL: https://issues.apache.org/jira/browse/IGNITE-2880
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 1.6
Environment: Ubuntu 14.04, Ignite 1.6.0
Reporter: Vasilisa Sidorova
-
DESCRIPTION
-
If you run any messaging example (java or scala) in the cluster and then try to
run new node from command line the node will be started but gets
ClassNotFoundException
-
STEPS FOR REPRODUCE
-
# Build examples in IDE
# Run ExampleNodeStartup or ./bin/ignite.sh
./examples/config/example-ignite.xml (it doesn't matter)
# Run any messaging example
# Run one more node from command line:
{noformat}
./bin/ignite.sh ./examples/config/example-ignite.xml
{noformat}
-
ACTUAL RESULT
-
Node is started but gets ClassNotFoundException:
{noformat}
[18:34:59,563][SEVERE][tcp-disco-msg-worker-#2%null%][TcpDiscoverySpi] Failed
to unmarshal discovery data for component: 0
class org.apache.ignite.IgniteCheckedException: Failed to find class with given
class loader for unmarshalling (make sure same versions of all classes are
available on all nodes or enable peer-class-loading):
sun.misc.Launcher$AppClassLoader@1447034b
at
org.apache.ignite.marshaller.jdk.JdkMarshaller.unmarshal(JdkMarshaller.java:108)
at
org.apache.ignite.marshaller.AbstractMarshaller.unmarshal(AbstractMarshaller.java:78)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.onExchange(TcpDiscoverySpi.java:1717)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeAddedMessage(ServerImpl.java:3685)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2252)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:5789)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2161)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
Caused by: java.lang.ClassNotFoundException:
org.apache.ignite.scalar.examples.ScalarPingPongExample$$anon$1
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:278)
at
org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8213)
at
org.apache.ignite.marshaller.jdk.JdkMarshallerObjectInputStream.resolveClass(JdkMarshallerObjectInputStream.java:54)
at
java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1612)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1517)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1771)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at
org.apache.ignite.internal.GridMessageListenHandler.readExternal(GridMessageListenHandler.java:254)
at
java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1837)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$DiscoveryDataItem.readExternal(GridContinuousProcessor.java:1618)
at
java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1837)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1350)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370)
at
org.apache.ignite.internal.util.IgniteUtils.readList(IgniteUtils.java:5176)
at
org.apache.ignite.internal.util.IgniteUtils.readCollection(IgniteUtils.java:1637)
at
[jira] [Assigned] (IGNITE-2694) .NET: AnyCPU build
[ https://issues.apache.org/jira/browse/IGNITE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasilisa Sidorova reassigned IGNITE-2694: -- Assignee: (was: Vasilisa Sidorova) > .NET: AnyCPU build > -- > > Key: IGNITE-2694 > URL: https://issues.apache.org/jira/browse/IGNITE-2694 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn > Fix For: 1.6 > > > Currently we provide separate x86 & x64 binaries. NuGet is x64-only. > This is inconvenient both for us and the user. > The only thing that prevents AnyCPU is unmanaged "common" project. > But we load it dynamically from resources, and we may as well detect current > process platform (x64 or not) and load a proper unmanaged resource. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2694) .NET: AnyCPU build
[
https://issues.apache.org/jira/browse/IGNITE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15206425#comment-15206425
]
Vasilisa Sidorova commented on IGNITE-2694:
Implementation is verified for Ignite 1.6.0 build #558: all is OK for both x86
and x64 platforms. Except little strange error for WinXP 32-bit, Microsoft
Visual C# 2010 - examples could be running only by "Run without debug". If user
try to Debug example (F5), the follow exception is a result:
{noformat}
An unhandled exception of type 'Apache.Ignite.Core.Common.IgniteException'
occurred in Apache.Ignite.Core.dll
Additional information: Failed to initialize JVM.
{noformat}
> .NET: AnyCPU build
> --
>
> Key: IGNITE-2694
> URL: https://issues.apache.org/jira/browse/IGNITE-2694
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Vasilisa Sidorova
> Fix For: 1.6
>
>
> Currently we provide separate x86 & x64 binaries. NuGet is x64-only.
> This is inconvenient both for us and the user.
> The only thing that prevents AnyCPU is unmanaged "common" project.
> But we load it dynamically from resources, and we may as well detect current
> process platform (x64 or not) and load a proper unmanaged resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-2694) .NET: AnyCPU build
[ https://issues.apache.org/jira/browse/IGNITE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasilisa Sidorova reassigned IGNITE-2694: -- Assignee: Vasilisa Sidorova (was: Pavel Tupitsyn) > .NET: AnyCPU build > -- > > Key: IGNITE-2694 > URL: https://issues.apache.org/jira/browse/IGNITE-2694 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Vasilisa Sidorova > Fix For: 1.6 > > > Currently we provide separate x86 & x64 binaries. NuGet is x64-only. > This is inconvenient both for us and the user. > The only thing that prevents AnyCPU is unmanaged "common" project. > But we load it dynamically from resources, and we may as well detect current > process platform (x64 or not) and load a proper unmanaged resource. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2837) Docker daemon doesn't start on the AWS instances
[
https://issues.apache.org/jira/browse/IGNITE-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15197247#comment-15197247
]
Vasilisa Sidorova commented on IGNITE-2837:
Please, fix the documentation also: update screenshot in the step 4 of the
"Amazon EC2 Deployment" instruction onto new attached version
> Docker daemon doesn't start on the AWS instances
>
>
> Key: IGNITE-2837
> URL: https://issues.apache.org/jira/browse/IGNITE-2837
> Project: Ignite
> Issue Type: Bug
> Components: aws
>Affects Versions: 1.5.0.final
>Reporter: Vasilisa Sidorova
> Attachments: ignite_aws_docker.png
>
>
> -
> DESCRIPTION
> -
> Deployment docker onto Amazon EC2 by this
> https://apacheignite.readme.io/docs/docker-deployment instruction is failed
> -
> STEPS FOR REPRODUCE
> -
> Do items 1-7 from "Amazon EC2 Deployement" instruction
> Do item 8
> -
> ACTUAL RESULT
> -
> The list of containers is empty. And command "sudo ./startup.sh" get result:
> {noformat}
> --2016-03-15 16:51:56-- http://169.254.169.254/latest/user-data
> Connecting to 169.254.169.254:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 41 [application/octet-stream]
> Saving to: ‘user-data’
> user-data
> 100%[===>]
> 41 --.-KB/s in 0s
> 2016-03-15 16:51:56 (10,1 MB/s) - ‘user-data’ saved [41/41]
> 1.5.0.final: Pulling from apacheignite/ignite
> 77e39ee82117: Already exists
> 5eb1402f0414: Already exists
> 9287fae7a16e: Already exists
> 0288ae931294: Already exists
> e5faec61f132: Already exists
> 9e9bea63cb40: Already exists
> dcb718404a8b: Already exists
> a8ce4138c3d9: Already exists
> 7c01b1c179c8: Already exists
> a41c2ba526d9: Already exists
> 5108e60af9fc: Already exists
> 171a6bf29457: Already exists
> 1e2a752083e5: Already exists
> 6dc3a9ded560: Already exists
> 5d9df50a72b0: Already exists
> e3dee37923c1: Already exists
> c7d92bcdbf90: Already exists
> 8de8b8b056fa: Already exists
> b298c64b2b41: Already exists
> 8185ba03f727: Already exists
> Digest:
> sha256:8826e49c8ea2c008ad6225df672916eb98979701b91948fb3587432e785cf40a
> Status: Image is up to date for apacheignite/ignite:1.5.0.final
> 84ca163452f47cc0ec3a62861b6ca88ccc242ee80d5cb8594b3e4820606f113c
> {noformat}
> -
> EXPECTED RESULT
> -
> Docker daemon and Ignite nodes should be started on all running amazon
> instances
> -
> ADDITIONAL INFO
> -
> Reproducible for all Amazon regions (west, east, central)
> For reproducing you can use instances with name ignite-docker-image in any
> region
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2862) Deployment Ignite in Mesos cluster is failed
Vasilisa Sidorova created IGNITE-2862:
--
Summary: Deployment Ignite in Mesos cluster is failed
Key: IGNITE-2862
URL: https://issues.apache.org/jira/browse/IGNITE-2862
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 1.5.0.final
Reporter: Vasilisa Sidorova
-
DESCRIPTION
-
Deployment Ignite in Mesos cluster by this instruction
https://apacheignite.readme.io/docs/mesos-deployment is failed
-
STEPS FOR REPRODUCE
-
# Do items 1-5 from "RUN THE FRAMEWORK VIA MARATHON" paragraph
-
ACTUAL RESULT
-
# Ignite nodes didn't start. Only ignition task is running. Look at the
attached picture "mesos_activetasks.png"
# Stderr log for ignition task get follow exception:
{noformat}
I0318 18:42:08.252142 17138 fetcher.cpp:409] Fetcher Info:
{"cache_directory":"\/tmp\/mesos\/fetch\/slaves\/20160318-180241-16777343-5050-16554-S0\/root","items":[{"action":"BYPASS_CACHE","uri":{"extract":false,"value":"https:\/\/s3.amazonaws.com\/vasilisk\/m\/ignite-mesos-1.5.0.final.jar"}}],"sandbox_directory":"\/tmp\/mesos\/slaves\/20160318-180241-16777343-5050-16554-S0\/frameworks\/20150603-121744-16842879-5050-6241-\/executors\/ignition.f8fa2435-ed1f-11e5-bea1-0242e00dbbdd\/runs\/776db62f-965f-4e9e-950a-4edb67c44667","user":"root"}
I0318 18:42:08.253284 17138 fetcher.cpp:364] Fetching URI
'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar'
I0318 18:42:08.253298 17138 fetcher.cpp:238] Fetching directly into the sandbox
directory
I0318 18:42:08.253312 17138 fetcher.cpp:176] Fetching URI
'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar'
I0318 18:42:08.253325 17138 fetcher.cpp:126] Downloading resource from
'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar' to
'/tmp/mesos/slaves/20160318-180241-16777343-5050-16554-S0/frameworks/20150603-121744-16842879-5050-6241-/executors/ignition.f8fa2435-ed1f-11e5-bea1-0242e00dbbdd/runs/776db62f-965f-4e9e-950a-4edb67c44667/ignite-mesos-1.5.0.final.jar'
I0318 18:42:12.091784 17138 fetcher.cpp:441] Fetched
'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar' to
'/tmp/mesos/slaves/20160318-180241-16777343-5050-16554-S0/frameworks/20150603-121744-16842879-5050-6241-/executors/ignition.f8fa2435-ed1f-11e5-bea1-0242e00dbbdd/runs/776db62f-965f-4e9e-950a-4edb67c44667/ignite-mesos-1.5.0.final.jar'
I0318 18:42:12.293658 17142 exec.cpp:132] Version: 0.23.0
I0318 18:42:12.296212 17145 exec.cpp:206] Executor registered on slave
20160318-180241-16777343-5050-16554-S0
Mar 18, 2016 6:42:12 PM org.apache.ignite.mesos.IgniteFramework main
INFO: Enabling checkpoint for the framework
2016-03-18 18:42:12.495:INFO::main: Logging initialized @151ms
2016-03-18 18:42:22.542:INFO:oejs.Server:main: jetty-9.2.z-SNAPSHOT
2016-03-18 18:42:22.579:INFO:oejs.ServerConnector:main: Started
ServerConnector@1268c278{HTTP/1.1}{172.17.0.1:48610}
2016-03-18 18:42:22.580:INFO:oejs.Server:main: Started @10235ms
Exception in thread "main" java.lang.RuntimeException: Got unexpected response
code. Response code: 404
at
org.apache.ignite.mesos.resource.IgniteProvider.downloadIgnite(IgniteProvider.java:202)
at
org.apache.ignite.mesos.resource.IgniteProvider.getIgnite(IgniteProvider.java:132)
at
org.apache.ignite.mesos.resource.ResourceProvider.init(ResourceProvider.java:57)
at org.apache.ignite.mesos.IgniteFramework.main(IgniteFramework.java:77)
{noformat}
-
EXPECTED RESULT
-
Tasks for all 3 nodes are running with ignition task.
-
ADDITIONAL INFO
-
# File "marathon.json" is attached
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2837) Docker daemon doesn't start on the AWS instances
[
https://issues.apache.org/jira/browse/IGNITE-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-2837:
---
Attachment: ignite_aws_docker.png
> Docker daemon doesn't start on the AWS instances
>
>
> Key: IGNITE-2837
> URL: https://issues.apache.org/jira/browse/IGNITE-2837
> Project: Ignite
> Issue Type: Bug
> Components: aws
>Affects Versions: 1.5.0.final
>Reporter: Vasilisa Sidorova
> Attachments: ignite_aws_docker.png
>
>
> -
> DESCRIPTION
> -
> Deployment docker onto Amazon EC2 by this
> https://apacheignite.readme.io/docs/docker-deployment instruction is failed
> -
> STEPS FOR REPRODUCE
> -
> Do items 1-7 from "Amazon EC2 Deployement" instruction
> Do item 8
> -
> ACTUAL RESULT
> -
> The list of containers is empty. And command "sudo ./startup.sh" get result:
> {noformat}
> --2016-03-15 16:51:56-- http://169.254.169.254/latest/user-data
> Connecting to 169.254.169.254:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 41 [application/octet-stream]
> Saving to: ‘user-data’
> user-data
> 100%[===>]
> 41 --.-KB/s in 0s
> 2016-03-15 16:51:56 (10,1 MB/s) - ‘user-data’ saved [41/41]
> 1.5.0.final: Pulling from apacheignite/ignite
> 77e39ee82117: Already exists
> 5eb1402f0414: Already exists
> 9287fae7a16e: Already exists
> 0288ae931294: Already exists
> e5faec61f132: Already exists
> 9e9bea63cb40: Already exists
> dcb718404a8b: Already exists
> a8ce4138c3d9: Already exists
> 7c01b1c179c8: Already exists
> a41c2ba526d9: Already exists
> 5108e60af9fc: Already exists
> 171a6bf29457: Already exists
> 1e2a752083e5: Already exists
> 6dc3a9ded560: Already exists
> 5d9df50a72b0: Already exists
> e3dee37923c1: Already exists
> c7d92bcdbf90: Already exists
> 8de8b8b056fa: Already exists
> b298c64b2b41: Already exists
> 8185ba03f727: Already exists
> Digest:
> sha256:8826e49c8ea2c008ad6225df672916eb98979701b91948fb3587432e785cf40a
> Status: Image is up to date for apacheignite/ignite:1.5.0.final
> 84ca163452f47cc0ec3a62861b6ca88ccc242ee80d5cb8594b3e4820606f113c
> {noformat}
> -
> EXPECTED RESULT
> -
> Docker daemon and Ignite nodes should be started on all running amazon
> instances
> -
> ADDITIONAL INFO
> -
> Reproducible for all Amazon regions (west, east, central)
> For reproducing you can use instances with name ignite-docker-image in any
> region
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2837) Docker daemon doesn't start on the AWS instances
[
https://issues.apache.org/jira/browse/IGNITE-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-2837:
---
Attachment: gcloud_ignitedocker_step6.png
> Docker daemon doesn't start on the AWS instances
>
>
> Key: IGNITE-2837
> URL: https://issues.apache.org/jira/browse/IGNITE-2837
> Project: Ignite
> Issue Type: Bug
> Components: aws
>Affects Versions: 1.5.0.final
>Reporter: Vasilisa Sidorova
> Attachments: gcloud_ignitedocker_step6.png, ignite_aws_docker.png
>
>
> -
> DESCRIPTION
> -
> Deployment docker onto Amazon EC2 by this
> https://apacheignite.readme.io/docs/docker-deployment instruction is failed
> -
> STEPS FOR REPRODUCE
> -
> Do items 1-7 from "Amazon EC2 Deployement" instruction
> Do item 8
> -
> ACTUAL RESULT
> -
> The list of containers is empty. And command "sudo ./startup.sh" get result:
> {noformat}
> --2016-03-15 16:51:56-- http://169.254.169.254/latest/user-data
> Connecting to 169.254.169.254:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 41 [application/octet-stream]
> Saving to: ‘user-data’
> user-data
> 100%[===>]
> 41 --.-KB/s in 0s
> 2016-03-15 16:51:56 (10,1 MB/s) - ‘user-data’ saved [41/41]
> 1.5.0.final: Pulling from apacheignite/ignite
> 77e39ee82117: Already exists
> 5eb1402f0414: Already exists
> 9287fae7a16e: Already exists
> 0288ae931294: Already exists
> e5faec61f132: Already exists
> 9e9bea63cb40: Already exists
> dcb718404a8b: Already exists
> a8ce4138c3d9: Already exists
> 7c01b1c179c8: Already exists
> a41c2ba526d9: Already exists
> 5108e60af9fc: Already exists
> 171a6bf29457: Already exists
> 1e2a752083e5: Already exists
> 6dc3a9ded560: Already exists
> 5d9df50a72b0: Already exists
> e3dee37923c1: Already exists
> c7d92bcdbf90: Already exists
> 8de8b8b056fa: Already exists
> b298c64b2b41: Already exists
> 8185ba03f727: Already exists
> Digest:
> sha256:8826e49c8ea2c008ad6225df672916eb98979701b91948fb3587432e785cf40a
> Status: Image is up to date for apacheignite/ignite:1.5.0.final
> 84ca163452f47cc0ec3a62861b6ca88ccc242ee80d5cb8594b3e4820606f113c
> {noformat}
> -
> EXPECTED RESULT
> -
> Docker daemon and Ignite nodes should be started on all running amazon
> instances
> -
> ADDITIONAL INFO
> -
> Reproducible for all Amazon regions (west, east, central)
> For reproducing you can use instances with name ignite-docker-image in any
> region
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-2837) Docker daemon doesn't start on the AWS instances
[
https://issues.apache.org/jira/browse/IGNITE-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15197247#comment-15197247
]
Vasilisa Sidorova edited comment on IGNITE-2837 at 3/16/16 2:07 PM:
-
Please, fix the documentation also:
1) Update screenshot in the step 4 of the "Amazon EC2 Deployment" instruction
onto new attached version
2) Update screenshot in the step 6 of the "Google Compute Deployment"
instruction onto new attached version
was (Author: vsidorova):
Please, fix the documentation also: update screenshot in the step 4 of the
"Amazon EC2 Deployment" instruction onto new attached version
> Docker daemon doesn't start on the AWS instances
>
>
> Key: IGNITE-2837
> URL: https://issues.apache.org/jira/browse/IGNITE-2837
> Project: Ignite
> Issue Type: Bug
> Components: aws
>Affects Versions: 1.5.0.final
>Reporter: Vasilisa Sidorova
> Attachments: gcloud_ignitedocker_step6.png, ignite_aws_docker.png
>
>
> -
> DESCRIPTION
> -
> Deployment docker onto Amazon EC2 by this
> https://apacheignite.readme.io/docs/docker-deployment instruction is failed
> -
> STEPS FOR REPRODUCE
> -
> Do items 1-7 from "Amazon EC2 Deployement" instruction
> Do item 8
> -
> ACTUAL RESULT
> -
> The list of containers is empty. And command "sudo ./startup.sh" get result:
> {noformat}
> --2016-03-15 16:51:56-- http://169.254.169.254/latest/user-data
> Connecting to 169.254.169.254:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 41 [application/octet-stream]
> Saving to: ‘user-data’
> user-data
> 100%[===>]
> 41 --.-KB/s in 0s
> 2016-03-15 16:51:56 (10,1 MB/s) - ‘user-data’ saved [41/41]
> 1.5.0.final: Pulling from apacheignite/ignite
> 77e39ee82117: Already exists
> 5eb1402f0414: Already exists
> 9287fae7a16e: Already exists
> 0288ae931294: Already exists
> e5faec61f132: Already exists
> 9e9bea63cb40: Already exists
> dcb718404a8b: Already exists
> a8ce4138c3d9: Already exists
> 7c01b1c179c8: Already exists
> a41c2ba526d9: Already exists
> 5108e60af9fc: Already exists
> 171a6bf29457: Already exists
> 1e2a752083e5: Already exists
> 6dc3a9ded560: Already exists
> 5d9df50a72b0: Already exists
> e3dee37923c1: Already exists
> c7d92bcdbf90: Already exists
> 8de8b8b056fa: Already exists
> b298c64b2b41: Already exists
> 8185ba03f727: Already exists
> Digest:
> sha256:8826e49c8ea2c008ad6225df672916eb98979701b91948fb3587432e785cf40a
> Status: Image is up to date for apacheignite/ignite:1.5.0.final
> 84ca163452f47cc0ec3a62861b6ca88ccc242ee80d5cb8594b3e4820606f113c
> {noformat}
> -
> EXPECTED RESULT
> -
> Docker daemon and Ignite nodes should be started on all running amazon
> instances
> -
> ADDITIONAL INFO
> -
> Reproducible for all Amazon regions (west, east, central)
> For reproducing you can use instances with name ignite-docker-image in any
> region
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2862) Deployment Ignite in Mesos cluster is failed
[
https://issues.apache.org/jira/browse/IGNITE-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova updated IGNITE-2862:
---
Description:
-
DESCRIPTION
-
Deployment Ignite in Mesos cluster by this instruction
https://apacheignite.readme.io/docs/mesos-deployment is failed
-
STEPS FOR REPRODUCE
-
# Do items 1-5 from "RUN THE FRAMEWORK VIA MARATHON" paragraph
-
ACTUAL RESULT
-
# Ignite nodes didn't start. Only ignition task is running. Look at the
attached picture "mesos_activetasks.png"
# Stderr log for ignition task get follow exception:
{noformat}
I0318 18:42:08.252142 17138 fetcher.cpp:409] Fetcher Info:
{"cache_directory":"\/tmp\/mesos\/fetch\/slaves\/20160318-180241-16777343-5050-16554-S0\/root","items":[{"action":"BYPASS_CACHE","uri":{"extract":false,"value":"https:\/\/s3.amazonaws.com\/vasilisk\/m\/ignite-mesos-1.5.0.final.jar"}}],"sandbox_directory":"\/tmp\/mesos\/slaves\/20160318-180241-16777343-5050-16554-S0\/frameworks\/20150603-121744-16842879-5050-6241-\/executors\/ignition.f8fa2435-ed1f-11e5-bea1-0242e00dbbdd\/runs\/776db62f-965f-4e9e-950a-4edb67c44667","user":"root"}
I0318 18:42:08.253284 17138 fetcher.cpp:364] Fetching URI
'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar'
I0318 18:42:08.253298 17138 fetcher.cpp:238] Fetching directly into the sandbox
directory
I0318 18:42:08.253312 17138 fetcher.cpp:176] Fetching URI
'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar'
I0318 18:42:08.253325 17138 fetcher.cpp:126] Downloading resource from
'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar' to
'/tmp/mesos/slaves/20160318-180241-16777343-5050-16554-S0/frameworks/20150603-121744-16842879-5050-6241-/executors/ignition.f8fa2435-ed1f-11e5-bea1-0242e00dbbdd/runs/776db62f-965f-4e9e-950a-4edb67c44667/ignite-mesos-1.5.0.final.jar'
I0318 18:42:12.091784 17138 fetcher.cpp:441] Fetched
'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar' to
'/tmp/mesos/slaves/20160318-180241-16777343-5050-16554-S0/frameworks/20150603-121744-16842879-5050-6241-/executors/ignition.f8fa2435-ed1f-11e5-bea1-0242e00dbbdd/runs/776db62f-965f-4e9e-950a-4edb67c44667/ignite-mesos-1.5.0.final.jar'
I0318 18:42:12.293658 17142 exec.cpp:132] Version: 0.23.0
I0318 18:42:12.296212 17145 exec.cpp:206] Executor registered on slave
20160318-180241-16777343-5050-16554-S0
Mar 18, 2016 6:42:12 PM org.apache.ignite.mesos.IgniteFramework main
INFO: Enabling checkpoint for the framework
2016-03-18 18:42:12.495:INFO::main: Logging initialized @151ms
2016-03-18 18:42:22.542:INFO:oejs.Server:main: jetty-9.2.z-SNAPSHOT
2016-03-18 18:42:22.579:INFO:oejs.ServerConnector:main: Started
ServerConnector@1268c278{HTTP/1.1}{172.17.0.1:48610}
2016-03-18 18:42:22.580:INFO:oejs.Server:main: Started @10235ms
Exception in thread "main" java.lang.RuntimeException: Got unexpected response
code. Response code: 404
at
org.apache.ignite.mesos.resource.IgniteProvider.downloadIgnite(IgniteProvider.java:202)
at
org.apache.ignite.mesos.resource.IgniteProvider.getIgnite(IgniteProvider.java:132)
at
org.apache.ignite.mesos.resource.ResourceProvider.init(ResourceProvider.java:57)
at org.apache.ignite.mesos.IgniteFramework.main(IgniteFramework.java:77)
{noformat}
-
EXPECTED RESULT
-
Tasks for all 3 nodes are running with ignition task.
-
ADDITIONAL INFO
-
# File "marathon.json" is attached
was:
-
DESCRIPTION
-
Deployment Ignite in Mesos cluster by this instruction
https://apacheignite.readme.io/docs/mesos-deployment is failed
-
STEPS FOR REPRODUCE
-
# Do items 1-5 from "RUN THE FRAMEWORK VIA MARATHON" paragraph
-
ACTUAL RESULT
-
# Ignite nodes didn't start. Only ignition task is running. Look at the
attached picture "mesos_activetasks.png"
# Stderr log for ignition task get follow exception:
{noformat}
I0318 18:42:08.252142 17138 fetcher.cpp:409] Fetcher Info:
[jira] [Commented] (IGNITE-2862) Deployment Ignite in Mesos cluster is failed
[
https://issues.apache.org/jira/browse/IGNITE-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15201765#comment-15201765
]
Vasilisa Sidorova commented on IGNITE-2862:
NB: the screenshot in the step 5 of paragraph "RUN THE FRAMEWORK VIA MARATHON"
is obsoleted. Please, update it. For example onto attached screenshot
"mesos_logs.png"
> Deployment Ignite in Mesos cluster is failed
>
>
> Key: IGNITE-2862
> URL: https://issues.apache.org/jira/browse/IGNITE-2862
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.5.0.final
>Reporter: Vasilisa Sidorova
> Attachments: marathon.json, mesos_activetasks.png, mesos_logs.png
>
>
> -
> DESCRIPTION
> -
> Deployment Ignite in Mesos cluster by this instruction
> https://apacheignite.readme.io/docs/mesos-deployment is failed
> -
> STEPS FOR REPRODUCE
> -
> # Do items 1-5 from "RUN THE FRAMEWORK VIA MARATHON" paragraph
> -
> ACTUAL RESULT
> -
> # Ignite nodes didn't start. Only ignition task is running. Look at the
> attached picture "mesos_activetasks.png"
> # Stderr log for ignition task get follow exception:
> {noformat}
> I0318 18:42:08.252142 17138 fetcher.cpp:409] Fetcher Info:
> {"cache_directory":"\/tmp\/mesos\/fetch\/slaves\/20160318-180241-16777343-5050-16554-S0\/root","items":[{"action":"BYPASS_CACHE","uri":{"extract":false,"value":"https:\/\/s3.amazonaws.com\/vasilisk\/m\/ignite-mesos-1.5.0.final.jar"}}],"sandbox_directory":"\/tmp\/mesos\/slaves\/20160318-180241-16777343-5050-16554-S0\/frameworks\/20150603-121744-16842879-5050-6241-\/executors\/ignition.f8fa2435-ed1f-11e5-bea1-0242e00dbbdd\/runs\/776db62f-965f-4e9e-950a-4edb67c44667","user":"root"}
> I0318 18:42:08.253284 17138 fetcher.cpp:364] Fetching URI
> 'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar'
> I0318 18:42:08.253298 17138 fetcher.cpp:238] Fetching directly into the
> sandbox directory
> I0318 18:42:08.253312 17138 fetcher.cpp:176] Fetching URI
> 'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar'
> I0318 18:42:08.253325 17138 fetcher.cpp:126] Downloading resource from
> 'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar' to
> '/tmp/mesos/slaves/20160318-180241-16777343-5050-16554-S0/frameworks/20150603-121744-16842879-5050-6241-/executors/ignition.f8fa2435-ed1f-11e5-bea1-0242e00dbbdd/runs/776db62f-965f-4e9e-950a-4edb67c44667/ignite-mesos-1.5.0.final.jar'
> I0318 18:42:12.091784 17138 fetcher.cpp:441] Fetched
> 'https://s3.amazonaws.com/vasilisk/m/ignite-mesos-1.5.0.final.jar' to
> '/tmp/mesos/slaves/20160318-180241-16777343-5050-16554-S0/frameworks/20150603-121744-16842879-5050-6241-/executors/ignition.f8fa2435-ed1f-11e5-bea1-0242e00dbbdd/runs/776db62f-965f-4e9e-950a-4edb67c44667/ignite-mesos-1.5.0.final.jar'
> I0318 18:42:12.293658 17142 exec.cpp:132] Version: 0.23.0
> I0318 18:42:12.296212 17145 exec.cpp:206] Executor registered on slave
> 20160318-180241-16777343-5050-16554-S0
> Mar 18, 2016 6:42:12 PM org.apache.ignite.mesos.IgniteFramework main
> INFO: Enabling checkpoint for the framework
> 2016-03-18 18:42:12.495:INFO::main: Logging initialized @151ms
> 2016-03-18 18:42:22.542:INFO:oejs.Server:main: jetty-9.2.z-SNAPSHOT
> 2016-03-18 18:42:22.579:INFO:oejs.ServerConnector:main: Started
> ServerConnector@1268c278{HTTP/1.1}{172.17.0.1:48610}
> 2016-03-18 18:42:22.580:INFO:oejs.Server:main: Started @10235ms
> Exception in thread "main" java.lang.RuntimeException: Got unexpected
> response code. Response code: 404
> at
> org.apache.ignite.mesos.resource.IgniteProvider.downloadIgnite(IgniteProvider.java:202)
> at
> org.apache.ignite.mesos.resource.IgniteProvider.getIgnite(IgniteProvider.java:132)
> at
> org.apache.ignite.mesos.resource.ResourceProvider.init(ResourceProvider.java:57)
> at org.apache.ignite.mesos.IgniteFramework.main(IgniteFramework.java:77)
> {noformat}
> -
> EXPECTED RESULT
> -
> Tasks for all 3 nodes are running with ignition task.
> -
> ADDITIONAL INFO
> -
> # File "marathon.json" is attached
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2837) Docker daemon doesn't start on the AWS instances
Vasilisa Sidorova created IGNITE-2837:
--
Summary: Docker daemon doesn't start on the AWS instances
Key: IGNITE-2837
URL: https://issues.apache.org/jira/browse/IGNITE-2837
Project: Ignite
Issue Type: Bug
Components: aws
Affects Versions: 1.5.0.final
Reporter: Vasilisa Sidorova
-
DESCRIPTION
-
Deployment docker onto Amazon EC2 by this
https://apacheignite.readme.io/docs/docker-deployment instruction is failed
-
STEPS FOR REPRODUCE
-
Do items 1-7 from "Amazon EC2 Deployement" instruction
Do item 8
-
ACTUAL RESULT
-
The list of containers is empty. And command "sudo ./startup.sh" get result:
{noformat}
--2016-03-15 16:51:56-- http://169.254.169.254/latest/user-data
Connecting to 169.254.169.254:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 41 [application/octet-stream]
Saving to: ‘user-data’
user-data
100%[===>]
41 --.-KB/s in 0s
2016-03-15 16:51:56 (10,1 MB/s) - ‘user-data’ saved [41/41]
1.5.0.final: Pulling from apacheignite/ignite
77e39ee82117: Already exists
5eb1402f0414: Already exists
9287fae7a16e: Already exists
0288ae931294: Already exists
e5faec61f132: Already exists
9e9bea63cb40: Already exists
dcb718404a8b: Already exists
a8ce4138c3d9: Already exists
7c01b1c179c8: Already exists
a41c2ba526d9: Already exists
5108e60af9fc: Already exists
171a6bf29457: Already exists
1e2a752083e5: Already exists
6dc3a9ded560: Already exists
5d9df50a72b0: Already exists
e3dee37923c1: Already exists
c7d92bcdbf90: Already exists
8de8b8b056fa: Already exists
b298c64b2b41: Already exists
8185ba03f727: Already exists
Digest: sha256:8826e49c8ea2c008ad6225df672916eb98979701b91948fb3587432e785cf40a
Status: Image is up to date for apacheignite/ignite:1.5.0.final
84ca163452f47cc0ec3a62861b6ca88ccc242ee80d5cb8594b3e4820606f113c
{noformat}
-
EXPECTED RESULT
-
Docker daemon and Ignite nodes should be started on all running amazon instances
-
ADDITIONAL INFO
-
Reproducible for all Amazon regions (west, east, central)
For reproducing you can use instances with name ignite-docker-image in any
region
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-2756) StreamVisitorExample returns empty result set
[
https://issues.apache.org/jira/browse/IGNITE-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova closed IGNITE-2756.
--
Assignee: (was: Vasilisa Sidorova)
> StreamVisitorExample returns empty result set
> -
>
> Key: IGNITE-2756
> URL: https://issues.apache.org/jira/browse/IGNITE-2756
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.6
>Reporter: Sergey Kozlov
>
> 1. Start {{ExampleNodeStartup}}
> 2. Start {{StreamVisitorExample}}
> {noformat}
> [15:31:22] Ignite node started OK (id=4395613e)
> [15:31:22] Topology snapshot [ver=2, servers=1, clients=1, CPUs=8, heap=7.1GB]
> Number of tuples streamed into Ignite: 50
> Number of tuples streamed into Ignite: 100
> ...
> Number of tuples streamed into Ignite: 950
> Number of tuples streamed into Ignite: 1000
> Top performing financial instruments:
> Query result set is empty.
> [15:31:47] Ignite node stopped OK [uptime=00:00:25:209]
> Process finished with exit code 0
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-2758) IGNITE_HOME/libs/ignite-aws/aws-java-sdk-1.10.29.jar doesn't contain any classes
[
https://issues.apache.org/jira/browse/IGNITE-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova closed IGNITE-2758.
--
Assignee: (was: Vasilisa Sidorova)
> IGNITE_HOME/libs/ignite-aws/aws-java-sdk-1.10.29.jar doesn't contain any
> classes
>
>
> Key: IGNITE-2758
> URL: https://issues.apache.org/jira/browse/IGNITE-2758
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Priority: Blocker
> Labels: community, customer, important
> Fix For: 1.6
>
>
> To observe the issue do this:
> * Build the fabric ZIP file.
> * Go to {{ignite-aws}} module folder.
> * Unzip {{aws-java-sdk-1.10.29.jar}}.
> * JAR file contains only pom.xml, no classes.
> We need to make sure that all required AWS SDK components are included. At
> least we need these ones:
> * aws-java-sdk-core
> * aws-java-sdk-s3
> * joda-time
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-2758) IGNITE_HOME/libs/ignite-aws/aws-java-sdk-1.10.29.jar doesn't contain any classes
[
https://issues.apache.org/jira/browse/IGNITE-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova resolved IGNITE-2758.
Resolution: Fixed
> IGNITE_HOME/libs/ignite-aws/aws-java-sdk-1.10.29.jar doesn't contain any
> classes
>
>
> Key: IGNITE-2758
> URL: https://issues.apache.org/jira/browse/IGNITE-2758
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Vasilisa Sidorova
>Priority: Blocker
> Labels: community, customer, important
> Fix For: 1.6
>
>
> To observe the issue do this:
> * Build the fabric ZIP file.
> * Go to {{ignite-aws}} module folder.
> * Unzip {{aws-java-sdk-1.10.29.jar}}.
> * JAR file contains only pom.xml, no classes.
> We need to make sure that all required AWS SDK components are included. At
> least we need these ones:
> * aws-java-sdk-core
> * aws-java-sdk-s3
> * joda-time
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-2756) StreamVisitorExample returns empty result set
[
https://issues.apache.org/jira/browse/IGNITE-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova resolved IGNITE-2756.
Resolution: Fixed
> StreamVisitorExample returns empty result set
> -
>
> Key: IGNITE-2756
> URL: https://issues.apache.org/jira/browse/IGNITE-2756
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.6
>Reporter: Sergey Kozlov
>Assignee: Vasilisa Sidorova
>
> 1. Start {{ExampleNodeStartup}}
> 2. Start {{StreamVisitorExample}}
> {noformat}
> [15:31:22] Ignite node started OK (id=4395613e)
> [15:31:22] Topology snapshot [ver=2, servers=1, clients=1, CPUs=8, heap=7.1GB]
> Number of tuples streamed into Ignite: 50
> Number of tuples streamed into Ignite: 100
> ...
> Number of tuples streamed into Ignite: 950
> Number of tuples streamed into Ignite: 1000
> Top performing financial instruments:
> Query result set is empty.
> [15:31:47] Ignite node stopped OK [uptime=00:00:25:209]
> Process finished with exit code 0
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2756) StreamVisitorExample returns empty result set
[
https://issues.apache.org/jira/browse/IGNITE-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189429#comment-15189429
]
Vasilisa Sidorova commented on IGNITE-2756:
Fix verified. Thank you, Valentin
> StreamVisitorExample returns empty result set
> -
>
> Key: IGNITE-2756
> URL: https://issues.apache.org/jira/browse/IGNITE-2756
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.6
>Reporter: Sergey Kozlov
>Assignee: Vasilisa Sidorova
>
> 1. Start {{ExampleNodeStartup}}
> 2. Start {{StreamVisitorExample}}
> {noformat}
> [15:31:22] Ignite node started OK (id=4395613e)
> [15:31:22] Topology snapshot [ver=2, servers=1, clients=1, CPUs=8, heap=7.1GB]
> Number of tuples streamed into Ignite: 50
> Number of tuples streamed into Ignite: 100
> ...
> Number of tuples streamed into Ignite: 950
> Number of tuples streamed into Ignite: 1000
> Top performing financial instruments:
> Query result set is empty.
> [15:31:47] Ignite node stopped OK [uptime=00:00:25:209]
> Process finished with exit code 0
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2758) IGNITE_HOME/libs/ignite-aws/aws-java-sdk-1.10.29.jar doesn't contain any classes
[
https://issues.apache.org/jira/browse/IGNITE-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15189420#comment-15189420
]
Vasilisa Sidorova commented on IGNITE-2758:
Done. All looks good now for Apache Ignite build #542 and there is not artifact
aws-java-sdk in the binaries.
Artifacts aws-java-sdk-core, aws-java-sdk-s3, joda-time, aws-java-sdk-kms
contain some classes.
> IGNITE_HOME/libs/ignite-aws/aws-java-sdk-1.10.29.jar doesn't contain any
> classes
>
>
> Key: IGNITE-2758
> URL: https://issues.apache.org/jira/browse/IGNITE-2758
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Vasilisa Sidorova
>Priority: Blocker
> Labels: community, customer, important
> Fix For: 1.6
>
>
> To observe the issue do this:
> * Build the fabric ZIP file.
> * Go to {{ignite-aws}} module folder.
> * Unzip {{aws-java-sdk-1.10.29.jar}}.
> * JAR file contains only pom.xml, no classes.
> We need to make sure that all required AWS SDK components are included. At
> least we need these ones:
> * aws-java-sdk-core
> * aws-java-sdk-s3
> * joda-time
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-2758) IGNITE_HOME/libs/ignite-aws/aws-java-sdk-1.10.29.jar doesn't contain any classes
[
https://issues.apache.org/jira/browse/IGNITE-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasilisa Sidorova reassigned IGNITE-2758:
--
Assignee: Valentin Kulichenko (was: Vasilisa Sidorova)
> IGNITE_HOME/libs/ignite-aws/aws-java-sdk-1.10.29.jar doesn't contain any
> classes
>
>
> Key: IGNITE-2758
> URL: https://issues.apache.org/jira/browse/IGNITE-2758
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Blocker
> Labels: community, customer, important
> Fix For: 1.6
>
>
> To observe the issue do this:
> * Build the fabric ZIP file.
> * Go to {{ignite-aws}} module folder.
> * Unzip {{aws-java-sdk-1.10.29.jar}}.
> * JAR file contains only pom.xml, no classes.
> We need to make sure that all required AWS SDK components are included. At
> least we need these ones:
> * aws-java-sdk-core
> * aws-java-sdk-s3
> * joda-time
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
