[graylog2] Re: Widget Types in Dashboards
found a few more by looking at example content packs: QUICKVALUES STREAM_SEARCH_RESULT_COUNT One issue/concern is that by changing in JSON just the type of a widget It can have undesired knock on affects due my lack of graylog knowledge. cheers aidan On Tuesday, July 21, 2015 at 4:58:52 PM UTC+1, Aidan Venn wrote: Hi, Working on the various widget types (display options) in dashboards. When analysing JSON code of exported content pack I can see the following: type : SEARCH_RESULT_COUNT, type : SEARCH_RESULT_CHART, However docs and images suggest others (line, pie chart) but I can not find how to edit through webGUI so editing via export/import content pack. Through webGUI they may auto adjust to input and time range? Does any one know the others if they are any and whts the syntax? for example: pie chart, line chart? It may be that some rely on multiple values to create - pie charts. Kind Regards Aidan -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Widget Types in Dashboards
Hi, Working on the various widget types (display options) in dashboards. When analysing JSON code of exported content pack I can see the following: type : SEARCH_RESULT_COUNT, type : SEARCH_RESULT_CHART, However docs and images suggest others (line, pie chart) but I can not find how to edit through webGUI so editing via export/import content pack. Through webGUI they may auto adjust to input and time range? Does any one know the others if they are any and whts the syntax? for example: pie chart, line chart? It may be that some rely on multiple values to create - pie charts. Kind Regards Aidan -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Drools rule example in graylog documentation does not work
I'm attempting to DROP or filter out specific messages using a drools rule. I followed the example here http://docs.graylog.org/en/latest/pages/drools.html but I get errors saying the rule is invalid. Any ideas? Rules file import org.graylog2.plugin.Message import java.util.regex.Matcher import java.util.regex.Pattern rule Drop Netscaler SESSION_UPDATE when m : Message( getField(full_message) matches ^\s?\d+\/\d+\/\d+:\d+:\d+:\d+\s+[\w\-]+\s.*?:\s+\w+\s+SESSION_UPDATE ) then m.setFilterOut(true); System.out.println([Drop Netscaler SESSION_UPDATE] : + m.toString() ); end 2015-07-21 13:17:19,411 ERROR: org.drools.compiler.kie.builder.impl.AbstractKieModule - Unable to build KieBaseModel:defaultKieBase [11,63]: [ERR 101] Line 11:63 no viable alternative at input '' [16,0]: [ERR 102] Line 16:0 mismatched input '' [11,63]: [ERR 101] Line 11:63 no viable alternative at input '/' in rule Drop Netscaler SESSION_UPDATE [0,0]: Parser returned a null Package 2015-07-21 13:17:19,412 WARN : org.graylog2.rules.DroolsEngine - Unable to add rules due to compilation errors. org.graylog2.rules.RulesCompilationException: Message [id=1, level=ERROR, path=r1.drl, line=11, column=0 text=[ERR 101] Line 11:63 no viable alternative at input ''] Message [id=2, level=ERROR, path=r1.drl, line=16, column=0 text=[ERR 102] Line 16:0 mismatched input ''] Message [id=3, level=ERROR, path=r1.drl, line=11, column=0 text=[ERR 101] Line 11:63 no viable alternative at input '/' in rule Drop Netscaler SESSION_UPDATE] Message [id=4, level=ERROR, path=r1.drl, line=0, column=0 text=Parser returned a null Package] at org.graylog2.rules.DroolsEngine.createKJar(DroolsEngine.java:221) at org.graylog2.rules.DroolsEngine.createAndDeployJar(DroolsEngine.java:190) at org.graylog2.rules.DroolsEngine.deployRules(DroolsEngine.java:165) at org.graylog2.rules.DroolsEngine.commitRules(DroolsEngine.java:143) at org.graylog2.rules.DroolsEngine.addRule(DroolsEngine.java:85) at org.graylog2.rules.DroolsEngine.addRulesFromFile(DroolsEngine.java:98) at org.graylog2.bindings.providers.RulesEngineProvider.init(RulesEngineProvider.java:43) at org.graylog2.bindings.providers.RulesEngineProvider$$FastClassByGuice$$3947f391.newInstance(generated) at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61) at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105) at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85) at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:267) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103) at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.BoundProviderFactory.get(BoundProviderFactory.java:61) at com.google.inject.internal.SingleParameterInjector.inject(SingleParameterInjector.java:38) at com.google.inject.internal.SingleParameterInjector.getAll(SingleParameterInjector.java:62) at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:104) at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85) at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:267) at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:56) at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103) at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012) at com.google.inject.multibindings.Multibinder$RealMultibinder.get(Multibinder.java:375) at com.google.inject.multibindings.Multibinder$RealMultibinder.get(Multibinder.java:258) at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:81) at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:53) at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:61) at
[graylog2] Re: About shards
Hi Juan,
IHMO for production having 4 ES nodes 4 shards can be fine. The data will
be shared on the 4 nodes leaving you
with 4 shards. (one on each node) Turning replicas to 1 wil create 1
replicated shard for each one there is. This gives you a backup
and improves search speed.
This is only in count for the new index that will be created if our setup
is already running, but there are some commands
in es that can make that happen for the current index.
see:
https://www.elastic.co/guide/en/elasticsearch/reference/1.6/indices-update-settings.html
Choosing the number of replicas:
https://www.elastic.co/guide/en/elasticsearch/guide/current/replica-shards.html
So for backup take one replica, for speed improvement choose 3 when having
4 nodes.
Every node is than capable of serving a search request.
A.
Op dinsdag 21 juli 2015 15:19:21 UTC+2 schreef Juan Andres Ramirez:
The cluster health:
{
cluster_name : elasticsearch,
status : yellow,
timed_out : false,
number_of_nodes : 2,
number_of_data_nodes : 1,
active_primary_shards : 16,
active_shards : 16,
relocating_shards : 0,
initializing_shards : 0,
unassigned_shards : 1,
delayed_unassigned_shards : 0,
number_of_pending_tasks : 0,
number_of_in_flight_fetch : 0
}
On Tuesday, July 21, 2015 at 9:54:23 AM UTC-3, Juan Andres Ramirez wrote:
Hello guys,
I was searching the answer in this group and in the web, but I
can't found the answer.
1- Graylog create 1 shard per indice?, so in this moment I have 17 shards
and in my config I have :
elasticsearch_shards = 1
elasticsearch_replicas = 0
So I'm in development phase, I don't need replicas.
2- If I will change in config elasticsearch_shards = 2 , then I'm going
to have 34 shards 2 per index?.
My last question, If I'm going to create an Elasticsearch a cluster with
4 nodes and change the setup elasticsearch_replicas = 1 , I'm going to have
17 shard in every node automatically?
I have problem to know how to work the elasticsearch cluster and the
configuration to failover.
Thank you.
--
You received this message because you are subscribed to the Google Groups
graylog2 group.
To unsubscribe from this group and stop receiving emails from it, send an email
to graylog2+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[graylog2] graylog2-web crashes after update to 1.1.4
Hello, I've upgraded from 1.0.2-1 to 1.1.4-1 on my graylog-server. ES, MongoDB, Graylog2-Server are running fine. Graylog2-Web crashes instantly after trying to access the web-interface. 2015-07-21T09:45:46.087+02:00 - [INFO] - from play in main Application started (Prod) 2015-07-21T09:45:46.146+02:00 - [INFO] - from play in main Listening for HTTP on /0:0:0:0:0:0:0:0:9000 2015-07-21T09:45:54.503+02:00 - [ERROR] - from play.nettyException in New I/O worker #6 Exception caught in Netty java.lang.IllegalArgumentException: empty text at org.jboss.netty.handler.codec.http.HttpVersion.init(HttpVersion.java:97) ~[io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.handler.codec.http.HttpVersion.valueOf(HttpVersion.java:62) ~[io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.handler.codec.http.HttpRequestDecoder.createMessage(HttpRequestDecoder.java:75) ~[io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.handler.codec.http.HttpMessageDecoder.decode(HttpMessageDecoder.java:191) ~[io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.handler.codec.http.HttpMessageDecoder.decode(HttpMessageDecoder.java:102) ~[io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:500) ~[io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:435) ~[io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) ~[io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) [io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) [io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) [io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) [io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108) [io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337) [io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89) [io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) [io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) [io.netty.netty-3.9.8.Final.jar:na] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_79] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_79] at java.lang.Thread.run(Thread.java:745) [na:1.7.0_79] I'm running CentOS 6.6, JDK 1.7.0_79. Configuration is done via puppet. I've also tried running it with openjdk 1.8.0_51. Any suggestions on this issue? Thanks, Denny -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: Remove some fields from log model
Hi Jochen, Which functionality of Graylog will be broken? On Tuesday, July 21, 2015 at 12:02:37 PM UTC+3, Jochen Schalanda wrote: Hi Eugene, while you can remove those fields retroactively (i. e. after the original messages have been indexed into Elasticsearch) using the Update API ( https://www.elastic.co/guide/en/elasticsearch/reference/1.6/docs-update.html#_scripted_updates), I would strongly advise against it since this will break some functionality of Graylog. Cheers, Jochen On Tuesday, 21 July 2015 10:50:09 UTC+2, Eugene Prokopiev wrote: Hi, I need to remove some fields from index such as gl2_source_input or gl2_source_node to reduce index size. Is it possible? -- Eugene -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: graylog2-web crashes after update to 1.1.4
Hi Denny, is there a transparent proxy between your client and the Graylog web interface or are you using any unusual client? It looks like the HTTP request doesn't contain all required information (i. e. the HTTP version line is missing, which is mandatory for any valid HTTP request). Cheers, Jochen On Tuesday, 21 July 2015 09:52:57 UTC+2, Denny Gebel wrote: Hello, I've upgraded from 1.0.2-1 to 1.1.4-1 on my graylog-server. ES, MongoDB, Graylog2-Server are running fine. Graylog2-Web crashes instantly after trying to access the web-interface. 2015-07-21T09:45:46.087+02:00 - [INFO] - from play in main Application started (Prod) 2015-07-21T09:45:46.146+02:00 - [INFO] - from play in main Listening for HTTP on /0:0:0:0:0:0:0:0:9000 2015-07-21T09:45:54.503+02:00 - [ERROR] - from play.nettyException in New I/O worker #6 Exception caught in Netty java.lang.IllegalArgumentException: empty text at org.jboss.netty.handler.codec.http.HttpVersion.init(HttpVersion.java:97) ~[io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.handler.codec.http.HttpVersion.valueOf(HttpVersion.java:62) ~[io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.handler.codec.http.HttpRequestDecoder.createMessage(HttpRequestDecoder.java:75) ~[io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.handler.codec.http.HttpMessageDecoder.decode(HttpMessageDecoder.java:191) ~[io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.handler.codec.http.HttpMessageDecoder.decode(HttpMessageDecoder.java:102) ~[io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:500) ~[io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:435) ~[io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) ~[io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) [io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) [io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) [io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) [io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108) [io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:337) [io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89) [io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) [io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [io.netty.netty-3.9.8.Final.jar:na] at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) [io.netty.netty-3.9.8.Final.jar:na] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_79] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_79] at java.lang.Thread.run(Thread.java:745) [na:1.7.0_79] I'm running CentOS 6.6, JDK 1.7.0_79. Configuration is done via puppet. I've also tried running it with openjdk 1.8.0_51. Any suggestions on this issue? Thanks, Denny -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: Remove some fields from log model
Hi Eugene, while you can remove those fields retroactively (i. e. after the original messages have been indexed into Elasticsearch) using the Update API ( https://www.elastic.co/guide/en/elasticsearch/reference/1.6/docs-update.html#_scripted_updates), I would strongly advise against it since this will break some functionality of Graylog. Cheers, Jochen On Tuesday, 21 July 2015 10:50:09 UTC+2, Eugene Prokopiev wrote: Hi, I need to remove some fields from index such as gl2_source_input or gl2_source_node to reduce index size. Is it possible? -- Eugene -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: Graylog Message get the Index
With deflector.getCurrentActualTargetIndex() the current index could be retrieved. But there is the problem in case the index changes (between message store time and output writing). -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [graylog2] Re: Graylog Message get the Index
Yes, that is correct, it is currently not possible to find the index name before it is written to elasticsearch. Getting the current deflector target name is the best option for now. Alternatively you could perform a search with the message id, but that has other problems like the fact that there is a delay between message write and it being available (refresh time). Cheers, Kay On Tue, Jul 21, 2015, 8:21 AM Kasimir Blaser kasimir.bla...@zuehlke.com wrote: With deflector.getCurrentActualTargetIndex() the current index could be retrieved. But there is the problem in case the index changes (between message store time and output writing). -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] About shards
Hello guys, I was searching the answer in this group and in the web, but I can't found the answer. 1- Graylog create 1 shard per indice?, so in this moment I have 17 shards and in my config I have : elasticsearch_shards = 1 elasticsearch_replicas = 0 So I'm in development phase, I don't need replicas. 2- If I will change in config elasticsearch_shards = 2 , then I'm going to have 34 shards 2 per index?. My last question, If I'm going to create an Elasticsearch a cluster with 4 nodes and change the setup elasticsearch_replicas = 1 , I'm going to have 17 shard in every node automatically? I have problem to know how to work the elasticsearch cluster and the configuration to failover. Thank you. -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Dashboards problems
My dashboards widgets load very slowly, there is a warning icon on each widget : Error loading widget value: Gateway Timeout Nothing happens in graylog servers logs, but webinterface server logs get full with messages like this : 2015-07-21 14:36:21,125[ERROR][org.graylog2.restclient.lib.ApiClient][play-akka.actor.default-dispatcher-46] REST call failed java.util.concurrent.TimeoutException: No response received after 5000 at com.ning.http.client.providers.netty.NettyResponseFuture.get(NettyResponseFuture.java:260) ~[com.ning.async-http-client-1.8.14.jar:na] at org.graylog2.restclient.lib.ApiClientImpl$ApiRequestBuilder.execute(ApiClientImpl.java:435) ~[org.graylog2.graylog2-rest-client--1.1.4-1.1.4.jar:na] at org.graylog2.restclient.models.dashboards.widgets.DashboardWidget.getValue(DashboardWidget.java:112) [org.graylog2.graylog2-rest-client--1.1.4-1.1.4.jar:na] at controllers.api.DashboardsApiController.widgetValue(DashboardsApiController.java:226) [graylog-web-interface.graylog-web-interface-1.1.4.jar:1.1.4] at Routes$$anonfun$routes$1$$anonfun$applyOrElse$173$$anonfun$apply$957.apply(routes_routing.scala:2991) [graylog-web-interface.graylog-web-interface-1.1.4.jar:na] at Routes$$anonfun$routes$1$$anonfun$applyOrElse$173$$anonfun$apply$957.apply(routes_routing.scala:2991) [graylog-web-interface.graylog-web-interface-1.1.4.jar:na] at play.core.Router$HandlerInvokerFactory$$anon$4.resultCall(Router.scala:264) [com.typesafe.play.play_2.10-2.3.9.jar:2.3.9] at play.core.Router$HandlerInvokerFactory$JavaActionInvokerFactory$$anon$15$$anon$1.invocation(Router.scala:255) [com.typesafe.play.play_2.10-2.3.9.jar:2.3.9] at play.core.j.JavaAction$$anon$1.call(JavaAction.scala:55) [com.typesafe.play.play_2.10-2.3.9.jar:2.3.9] at play.GlobalSettings$1.call(GlobalSettings.java:67) [com.typesafe.play.play_2.10-2.3.9.jar:2.3.9] at play.mvc.Security$AuthenticatedAction.call(Security.java:44) [com.typesafe.play.play_2.10-2.3.9.jar:2.3.9] at play.core.j.JavaAction$$anonfun$11.apply(JavaAction.scala:82) [com.typesafe.play.play_2.10-2.3.9.jar:2.3.9] at play.core.j.JavaAction$$anonfun$11.apply(JavaAction.scala:82) [com.typesafe.play.play_2.10-2.3.9.jar:2.3.9] at scala.concurrent.impl.Future$PromiseCompletingRunnable.liftedTree1$1(Future.scala:24) [org.scala-lang.scala-library-2.10.4.jar:na] at scala.concurrent.impl.Future$PromiseCompletingRunnable.run(Future.scala:24) [org.scala-lang.scala-library-2.10.4.jar:na] at play.core.j.HttpExecutionContext$$anon$2.run(HttpExecutionContext.scala:40) [com.typesafe.play.play_2.10-2.3.9.jar:2.3.9] at play.api.libs.iteratee.Execution$trampoline$.execute(Execution.scala:46) [com.typesafe.play.play-iteratees_2.10-2.3.9.jar:2.3.9] at play.core.j.HttpExecutionContext.execute(HttpExecutionContext.scala:32) [com.typesafe.play.play_2.10-2.3.9.jar:2.3.9] at scala.concurrent.impl.Future$.apply(Future.scala:31) [org.scala-lang.scala-library-2.10.4.jar:na] at scala.concurrent.Future$.apply(Future.scala:485) [org.scala-lang.scala-library-2.10.4.jar:na] at play.core.j.JavaAction$class.apply(JavaAction.scala:82) [com.typesafe.play.play_2.10-2.3.9.jar:2.3.9] at play.core.Router$HandlerInvokerFactory$JavaActionInvokerFactory$$anon$15$$anon$1.apply(Router.scala:252) [com.typesafe.play.play_2.10-2.3.9.jar:2.3.9] at play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4$$anonfun$apply$5.apply(Action.scala:130) [com.typesafe.play.play_2.10-2.3.9.jar:2.3.9] at play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4$$anonfun$apply$5.apply(Action.scala:130) [com.typesafe.play.play_2.10-2.3.9.jar:2.3.9] at play.utils.Threads$.withContextClassLoader(Threads.scala:21) [com.typesafe.play.play_2.10-2.3.9.jar:2.3.9] at play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4.apply(Action.scala:129) [com.typesafe.play.play_2.10-2.3.9.jar:2.3.9] at play.api.mvc.Action$$anonfun$apply$1$$anonfun$apply$4.apply(Action.scala:128) [com.typesafe.play.play_2.10-2.3.9.jar:2.3.9] at scala.Option.map(Option.scala:145) [org.scala-lang.scala-library-2.10.4.jar:na] at play.api.mvc.Action$$anonfun$apply$1.apply(Action.scala:128) [com.typesafe.play.play_2.10-2.3.9.jar:2.3.9] at play.api.mvc.Action$$anonfun$apply$1.apply(Action.scala:121) [com.typesafe.play.play_2.10-2.3.9.jar:2.3.9] at play.api.libs.iteratee.Iteratee$$anonfun$mapM$1.apply(Iteratee.scala:483) [com.typesafe.play.play-iteratees_2.10-2.3.9.jar:2.3.9] at play.api.libs.iteratee.Iteratee$$anonfun$mapM$1.apply(Iteratee.scala:483) [com.typesafe.play.play-iteratees_2.10-2.3.9.jar:2.3.9] at play.api.libs.iteratee.Iteratee$$anonfun$flatMapM$1.apply(Iteratee.scala:519) [com.typesafe.play.play-iteratees_2.10-2.3.9.jar:2.3.9] at
[graylog2] Re: About shards
The cluster health:
{
cluster_name : elasticsearch,
status : yellow,
timed_out : false,
number_of_nodes : 2,
number_of_data_nodes : 1,
active_primary_shards : 16,
active_shards : 16,
relocating_shards : 0,
initializing_shards : 0,
unassigned_shards : 1,
delayed_unassigned_shards : 0,
number_of_pending_tasks : 0,
number_of_in_flight_fetch : 0
}
On Tuesday, July 21, 2015 at 9:54:23 AM UTC-3, Juan Andres Ramirez wrote:
Hello guys,
I was searching the answer in this group and in the web, but I
can't found the answer.
1- Graylog create 1 shard per indice?, so in this moment I have 17 shards
and in my config I have :
elasticsearch_shards = 1
elasticsearch_replicas = 0
So I'm in development phase, I don't need replicas.
2- If I will change in config elasticsearch_shards = 2 , then I'm going to
have 34 shards 2 per index?.
My last question, If I'm going to create an Elasticsearch a cluster with 4
nodes and change the setup elasticsearch_replicas = 1 , I'm going to have
17 shard in every node automatically?
I have problem to know how to work the elasticsearch cluster and the
configuration to failover.
Thank you.
--
You received this message because you are subscribed to the Google Groups
graylog2 group.
To unsubscribe from this group and stop receiving emails from it, send an email
to graylog2+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
