> I believe the issue is just jmx_host needing to be set to 'localhost'
Yes, that solved. Thanks!
giampaolo
2016-01-08 5:17 GMT+01:00 Nick Bailey :
> stomp_interface is the address to connect back to the central OpsCenter
> daemon with, so 127.0.0.1 should be correct. I believe the issue is jus
On 01/07/2016 10:17 PM, Nick Bailey wrote:
> stomp_interface is the address to connect back to the central OpsCenter
> daemon with, so 127.0.0.1 should be correct. I believe the issue is just
> jmx_host needing to be set to 'localhost'
This indeed looks promising, thanks Nick!
mshuler@hana:~$ ccm
stomp_interface is the address to connect back to the central OpsCenter
daemon with, so 127.0.0.1 should be correct. I believe the issue is just
jmx_host needing to be set to 'localhost'
On Thu, Jan 7, 2016 at 8:50 PM, Michael Shuler
wrote:
> On 01/07/2016 08:46 PM, Michael Shuler wrote:
> > I'm
On 01/07/2016 08:46 PM, Michael Shuler wrote:
> I'm not sure exactly what that service is, but if all 4 nodes (which are
> all really localhost aliases) are attempting to bind to the same IP:port
> for that stomp connection, they could be stepping on one another. Should
> those be 127.0.0.1 for nod
On 01/07/2016 02:09 AM, Giampaolo Trapasso wrote:
> I've configured all the four agents. For example /agent3/ configuration is
>
> |[Giampaolo]: ~/opscenter/> cat agent3/conf/address.yaml stomp_interface:
> "127.0.0.1" agent_rpc_interface: 127.0.0.3 jmx_host: 127.0.0.3 jmx_port:
> 7300 |
This loo
Cassandra switched jmx to only bind to localhost, so I believe you just
need to change jmx_host to localhost for all conf files.
On Thu, Jan 7, 2016 at 4:48 PM, Giampaolo Trapasso <
giampaolo.trapa...@radicalbit.io> wrote:
> Thanks Michael for the reply. I'm quite new to Cassandra, so it make sen
Thanks Michael for the reply. I'm quite new to Cassandra, so it make sense
to explain the use case. I just want to try different choices of data
modelling and compare number of reads and writes. At the moment I'm not
interested in a real stress test, I just want to understand implications of
my cho
