Github user uce commented on a diff in the pull request:
https://github.com/apache/flink/pull/3460#discussion_r105928423
--- Diff:
flink-core/src/main/java/org/apache/flink/configuration/HistoryServerOptions.java
---
@@ -0,0 +1,82 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.flink.configuration;
+
+import org.apache.flink.annotation.PublicEvolving;
+
+import static org.apache.flink.configuration.ConfigOptions.key;
+
+/**
+ * The set of configuration options relating to the HistoryServer.
+ */
+@PublicEvolving
+public class HistoryServerOptions {
+
+ /**
+ * The interval at which the HistoryServer polls {@link
HistoryServerOptions#HISTORY_SERVER_DIRS} for new archives.
+ */
+ public static final ConfigOption<Long> HISTORY_SERVER_REFRESH_INTERVAL =
+ key("historyserver.refresh-interval")
+ .defaultValue(3000L);
--- End diff --
I was under the impression that the `historyserver.web.refresh-interval`
does not affect the actual web refresh interval specified in index.coffee,
right?
What I thought originally was that the fs refresh interval being smaller
than the web refresh interval does not make sense if we only update the
frontend every 10s. But I forgot that people also manually browse the pages ;-)
I'm still in favour to increase as you say.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
