Re: Unable to connect to Ignite Visor Console in Ignite 2.8.0

2020-03-10 Thread Ilya Kasnacheev
Hello!

Actually, this screen shot does actually contain relevant error message:
rebalance thread pool size should be < system thread pool size.

It is enforced and node will not start (even visor's Daemon node).

Please fix your cfg to enforce this constraint:
https://apacheignite.readme.io/docs/thread-pools

Regards,
-- 
Ilya Kasnacheev


пт, 6 мар. 2020 г. в 17:37, Николай Кулагин :

> Joshi,
>
> A ticket has been started for this issue. You can track his status here
> [1].
>
> [1] https://issues.apache.org/jira/browse/IGNITE-12757
>
> чт, 5 мар. 2020 г. в 14:48, Kamlesh Joshi :
>
>> Hi Team,
>>
>>
>>
>> I have updated Ignite cluster to latest version 2.8.0 and update was
>> successful. However, I am unable connect to IgniteVisor console. Below is
>> the command I used (the same command was used for earlier versions and it
>> worked fine). Not sure am I missing something or is there any defect around
>> it? Ignite 2.8.0 docs are not available on the site !
>>
>>
>>
>> *$IGNITE_HOME/bin/ignitevisorcmd.sh -cfg="/app/Ignite/visorconfig.xml"*
>>
>>
>>
>>
>>
>>
>>
>> *Thanks and Regards,*
>>
>> *Kamlesh Joshi*
>>
>>
>>
>>
>> "*Confidentiality Warning*: This message and any attachments are
>> intended only for the use of the intended recipient(s), are confidential
>> and may be privileged. If you are not the intended recipient, you are
>> hereby notified that any review, re-transmission, conversion to hard copy,
>> copying, circulation or other use of this message and any attachments is
>> strictly prohibited. If you are not the intended recipient, please notify
>> the sender immediately by return email and delete this message and any
>> attachments from your system.
>>
>> *Virus Warning:* Although the company has taken reasonable precautions
>> to ensure no viruses are present in this email. The company cannot accept
>> responsibility for any loss or damage arising from the use of this email or
>> attachment."
>>
>


Re: Unable to connect to Ignite Visor Console in Ignite 2.8.0

2020-03-06 Thread Николай Кулагин
Joshi,

A ticket has been started for this issue. You can track his status here [1].

[1] https://issues.apache.org/jira/browse/IGNITE-12757

чт, 5 мар. 2020 г. в 14:48, Kamlesh Joshi :

> Hi Team,
>
>
>
> I have updated Ignite cluster to latest version 2.8.0 and update was
> successful. However, I am unable connect to IgniteVisor console. Below is
> the command I used (the same command was used for earlier versions and it
> worked fine). Not sure am I missing something or is there any defect around
> it? Ignite 2.8.0 docs are not available on the site !
>
>
>
> *$IGNITE_HOME/bin/ignitevisorcmd.sh -cfg="/app/Ignite/visorconfig.xml"*
>
>
>
>
>
>
>
> *Thanks and Regards,*
>
> *Kamlesh Joshi*
>
>
>
>
> "*Confidentiality Warning*: This message and any attachments are intended
> only for the use of the intended recipient(s), are confidential and may be
> privileged. If you are not the intended recipient, you are hereby notified
> that any review, re-transmission, conversion to hard copy, copying,
> circulation or other use of this message and any attachments is strictly
> prohibited. If you are not the intended recipient, please notify the sender
> immediately by return email and delete this message and any attachments
> from your system.
>
> *Virus Warning:* Although the company has taken reasonable precautions to
> ensure no viruses are present in this email. The company cannot accept
> responsibility for any loss or damage arising from the use of this email or
> attachment."
>


Unable to connect to Ignite Visor Console in Ignite 2.8.0

2020-03-05 Thread Kamlesh Joshi
Hi Team,

I have updated Ignite cluster to latest version 2.8.0 and update was 
successful. However, I am unable connect to IgniteVisor console. Below is the 
command I used (the same command was used for earlier versions and it worked 
fine). Not sure am I missing something or is there any defect around it? Ignite 
2.8.0 docs are not available on the site !

$IGNITE_HOME/bin/ignitevisorcmd.sh -cfg="/app/Ignite/visorconfig.xml"

[cid:image001.jpg@01D5F312.05CC1780]


Thanks and Regards,
Kamlesh Joshi

"Confidentiality Warning: This message and any attachments are intended only 
for the use of the intended recipient(s). 
are confidential and may be privileged. If you are not the intended recipient. 
you are hereby notified that any 
review. re-transmission. conversion to hard copy. copying. circulation or other 
use of this message and any attachments is 
strictly prohibited. If you are not the intended recipient. please notify the 
sender immediately by return email. 
and delete this message and any attachments from your system.

Virus Warning: Although the company has taken reasonable precautions to ensure 
no viruses are present in this email. 
The company cannot accept responsibility for any loss or damage arising from 
the use of this email or attachment."


Re: Visor console

2018-04-06 Thread oggo
Hi Vasiliy, 
sure i woud have set IGNITE_HOME if i have used visor cmd, but as i said i
am trying the approach to start visor from java application with maven
dependency, similar to the suggestion done by Alexey. I have an springboot
application and inside this application i am starting ignite node. All the
configurations are done in java and inside the application. Apart from this
i want to give the possibility to the operation guys to connect to the
clustur just executing a java class / jar. I don't have full ignite
distribution. 

Thanx and cheers, 
Oggo



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/


Re: Visor console

2018-04-06 Thread Vasiliy Sisko
Hello @oggo

Null is possible when IGNITE_HOME variable is not configured. Visor CMD use
that variable  as a root folder to find configuration files and show they in
open command.

Please set IGNITE_HOME variable equal to your application home.

Ignite automatically detect the home folder when it contain "bin" and
"config" folder.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/


Re: Visor console

2018-04-06 Thread oggo
Hi Alexey, 
i am using the same approach, it starts the visor, but when i try to open a
configuration i get following exception (and 2 warnings): 
[17:26:30] (wrn) Failed to resolve IGNITE_HOME automatically for class
codebase [class=class o.a.i.i.util.IgniteUtils, e=URI is not hierarchical]
java.lang.NullPointerException
at java.io.File.(Unknown Source)
at
org.apache.ignite.internal.util.GridConfigurationFinder.getConfigFiles(GridConfigurationFinder.java:61)
at org.apache.ignite.visor.visor$.askConfigFile(visor.scala:1998)
at
org.apache.ignite.visor.commands.open.VisorOpenCommand.open(VisorOpenCommand.scala:205)
at
org.apache.ignite.visor.commands.open.VisorOpenCommand.open(VisorOpenCommand.scala:96)
at
org.apache.ignite.visor.commands.open.VisorOpenCommand$$anonfun$1.apply$mcV$sp(VisorOpenCommand.scala:305)
at
org.apache.ignite.visor.commands.VisorConsole.mainLoop(VisorConsole.scala:220)
at
org.apache.ignite.visor.commands.VisorConsole$.delayedEndpoint$org$apache$ignite$visor$commands$VisorConsole$1(VisorConsole.scala:337)
at
org.apache.ignite.visor.commands.VisorConsole$delayedInit$body.apply(VisorConsole.scala:326)
at scala.Function0$class.apply$mcV$sp(Function0.scala:34)
at
scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12)
at scala.App$$anonfun$main$1.apply(App.scala:76)
at scala.App$$anonfun$main$1.apply(App.scala:76)
at scala.collection.immutable.List.foreach(List.scala:381)
at
scala.collection.generic.TraversableForwarder$class.foreach(TraversableForwarder.scala:35)
at scala.App$class.main(App.scala:76)
at
org.apache.ignite.visor.commands.VisorConsole$.main(VisorConsole.scala:326)
at
org.apache.ignite.visor.commands.VisorConsole.main(VisorConsole.scala)
at
de.db.istp.oggo.demo.DemoVisorConsole.main(DemoVisorConsole.java:33)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader.main(JarRsrcLoader.java:58)
(wrn) : Invalid command name: 'open'
(wrn) : Type 'help' to print commands list.

... i guess the visor needs some of the jars in libs and bin/include
directories to work, but in my application i don't have full ignite
instance, just maven dependencies. Is there a way to get it working?

Thanx and cheers, 
Oggo




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/


Re: Unable to query system cache through Visor console

2017-11-22 Thread Denis Magda
Krzystof,

It will be more correct to add missing metrics that will provide this 
information. Feel free to propose the new metrics in this discussion:
http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Enhancement-Proposal-6-Metrics-td24192.html
 


The community has putting efforts on making the metrics more mature and 
advanced.

P.S. don’t forget to sign up for the dev list before sending a message there.

--
Denis

> On Nov 22, 2017, at 1:12 PM, Krzysztof Chmielewski 
>  wrote:
> 
> Thanks for your response Denis. 
> My uses case would be to list all Ignite semaphores and Ignite atomic
> references used in my Ignite grid.
> As fare as I know, those are stored in system caches.
> 
> Thanks
> Krzysztof 
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/



Re: Unable to query system cache through Visor console

2017-11-22 Thread Krzysztof Chmielewski
Thanks for your response Denis. 
My uses case would be to list all Ignite semaphores and Ignite atomic
references used in my Ignite grid.
As fare as I know, those are stored in system caches.

Thanks
Krzysztof 



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/


Re: Unable to query system cache through Visor console

2017-11-22 Thread Denis Mekhanikov
Hi Krzysztof!

It's even problematic to get an instance of system cache over Java API, not
even from Visor CLI.
Internal system information is stored there, so it's hidden from users. And
Visor cannot access it as well, because it uses public API.

Why would you want to do something like that? Could you describe your
use-case?

Denis

ср, 22 нояб. 2017 г. в 16:26, Krzysztof Chmielewski <
krzysiek.chmielew...@gmail.com>:

> Hi,
> is there a way to query system caches like *ignite-sys-atomic-cache* via
> Visor console?
> If I'm trying to execute Visor command "cache -scan -c=@c2" where @2 is a
> cache's id, I'm receiving this error:
> *(wrn) : Failed to get cache because it is a system cache:
> ignite-sys-atomic-cache@default-ds-group*
>
>
> Im using Ignite 2.3.0
>
> Thanks
> Krzysztof
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


Unable to query system cache through Visor console

2017-11-22 Thread Krzysztof Chmielewski
Hi, 
is there a way to query system caches like *ignite-sys-atomic-cache* via
Visor console?
If I'm trying to execute Visor command "cache -scan -c=@c2" where @2 is a
cache's id, I'm receiving this error:
*(wrn) : Failed to get cache because it is a system cache:
ignite-sys-atomic-cache@default-ds-group*


Im using Ignite 2.3.0

Thanks
Krzysztof



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/


Re: 2.1.4 visor console - activate/deactivate command?

2017-09-07 Thread Denis Magda
Hello,

You need to use {ignite}/bin/control.sh script to activate/deactivate the 
cluster. Hope this feature will be migrated to the Visor CMD soon.

—
Denis

> On Sep 7, 2017, at 9:30 AM, Michael Cherkasov  
> wrote:
> 
> Hi, 
> there's no such version like 2.1.4, the latest one is 2.1.
> 
> Thanks,
> Mike.
> 
> 2017-09-07 19:00 GMT+03:00 mzingman  >:
> I've downloaded latest ignite-fabric (2.1.4), and running ignitevisorcmd, but
> having trouble finding activate/deactivate grid command (promised in Release
> Notes). Please help, thank you.
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ 
> 
> 



Re: 2.1.4 visor console - activate/deactivate command?

2017-09-07 Thread Michael Cherkasov
Hi,
there's no such version like 2.1.4, the latest one is 2.1.

Thanks,
Mike.

2017-09-07 19:00 GMT+03:00 mzingman :

> I've downloaded latest ignite-fabric (2.1.4), and running ignitevisorcmd,
> but
> having trouble finding activate/deactivate grid command (promised in
> Release
> Notes). Please help, thank you.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


2.1.4 visor console - activate/deactivate command?

2017-09-07 Thread mzingman
I've downloaded latest ignite-fabric (2.1.4), and running ignitevisorcmd, but
having trouble finding activate/deactivate grid command (promised in Release
Notes). Please help, thank you.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/


Re: Visor console

2016-11-11 Thread Paolo Di Tommaso
Wow, easy! I will give it a try soon.


Thanks,
Paolo


On Fri, Nov 11, 2016 at 10:19 AM, Alexey Kuznetsov <akuznet...@apache.org>
wrote:

> Hi Paolo!
>
> Yes, it is possible.
>
> See attached pom.xml and VisorStartup.java example.
>
>
> On Fri, Nov 11, 2016 at 4:59 AM, Paolo Di Tommaso <
> paolo.ditomm...@gmail.com> wrote:
>
>> Hi,
>>
>> Is it possible to deploy the visor console in a embedded manner? I mean
>> just including the visor dependencies into an application classpath and
>> launch it?
>>
>>
>> Is there any example of that?
>>
>>
>> Cheers,
>> Paolo
>>
>>
>
>
>
> --
> Alexey Kuznetsov
>


Re: Visor console

2016-11-11 Thread Alexey Kuznetsov
Hi Paolo!

Yes, it is possible.

See attached pom.xml and VisorStartup.java example.


On Fri, Nov 11, 2016 at 4:59 AM, Paolo Di Tommaso <paolo.ditomm...@gmail.com
> wrote:

> Hi,
>
> Is it possible to deploy the visor console in a embedded manner? I mean
> just including the visor dependencies into an application classpath and
> launch it?
>
>
> Is there any example of that?
>
>
> Cheers,
> Paolo
>
>



-- 
Alexey Kuznetsov




http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
 xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0

org.apache.ignite
My_cluster-project
1.6.9



GridGain External Repository
http://www.gridgainsystems.com/nexus/content/repositories/external





org.apache.ignite
ignite-core
1.6.9



org.apache.ignite
ignite-core
1.6.9



org.apache.ignite
ignite-ssh
1.6.9



org.apache.ignite
ignite-spring
1.6.9
    

    
    org.apache.ignite
ignite-visor-console
1.6.9



org.springframework
spring-core
4.1.0.RELEASE



org.springframework
spring-beans
4.1.0.RELEASE



org.springframework
spring-context
4.1.0.RELEASE



org.springframework
spring-expression
4.1.0.RELEASE



org.scala-lang
scala-library
2.11.7



jline
jline
2.12.1






src/main/java

**/*.java



src/main/resources




maven-dependency-plugin


copy-libs
test-compile

copy-dependencies


org.apache.ignite,org.gridgain
target/libs
compile
true





maven-compiler-plugin
3.1

1.7
1.7







VisorStartup.java
Description: Binary data


Visor console

2016-11-10 Thread Paolo Di Tommaso
Hi,

Is it possible to deploy the visor console in a embedded manner? I mean
just including the visor dependencies into an application classpath and
launch it?


Is there any example of that?


Cheers,
Paolo


Re: "OFFHEAP_VALUES" MODE (VISOR CONSOLE)

2016-09-09 Thread Ignitebie
Thanks Val.



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/OFFHEAP-VALUES-MODE-VISOR-CONSOLE-tp7601p7631.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


Re: "OFFHEAP_VALUES" MODE (VISOR CONSOLE)

2016-09-08 Thread vkulichenko
Hi,

This is correct behavior. In OFFHEAP_VALUES mode, entries are actually
stored on-heap, but in instead of values they have a pointers to off-heap
memory.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/OFFHEAP-VALUES-MODE-VISOR-CONSOLE-tp7601p7618.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.


"OFFHEAP_VALUES" MODE (VISOR CONSOLE)

2016-09-08 Thread Ignitebie
Hi,

We have configured few caches in "OFFHEAP_VALUES" mode and trying to see how
entries are being deployed (ON/OFF) using visor. Our observation it that for
"OFFHEAP_TIERED", visor show entries in off heap metrics on visor console.
However, for OFFHEAP_VALUES, visor show count 0 for off heap and all count
is reflected against on heap column Header (   Entries (Heap / Off heap)).

Is it because key is still on heap and it counts entries not (values). What
is the way to know whether values are really of heap now  in OFFHEAP_VALUES.





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/OFFHEAP-VALUES-MODE-VISOR-CONSOLE-tp7601.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.